The IBM z/VM DOMAINSEARCH statement in the TCPIP DATA file must be configured with proper domain names for name resolution.

From IBM z/VM Using CA VM:Secure Security Technical Implementation Guide

Part of SRG-OS-000402-GPOS-00181

Associated with: CCI-002468

SV-93659r1_rule The IBM z/VM DOMAINSEARCH statement in the TCPIP DATA file must be configured with proper domain names for name resolution.

Vulnerability discussion

If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it may have come from a poisoned cache, the packets could have been intercepted without the resolver's knowledge, or resource records could have been removed which would result in query failure or denial of service. Data origin authentication verification must be performed to thwart these types of attacks.Each client of name resolution services either performs this validation on its own or has authenticated channels to trusted validation providers. Information systems that provide name and address resolution services for local clients include, for example, recursive resolving or caching Domain Name System (DNS) servers. DNS client resolvers either perform validation of DNSSEC signatures, or clients use authenticated channels to recursive resolvers that perform such validations.This is not applicable if DNSSEC is not implemented on the local network.

Check content

Examine the “TCPIP DATA” file. The domain specified for the “DOMAINORIGIN” statement is also used for host name resolution, as if it appeared in a “DOMAINSEARCH” statement. If there is no "DOMAINORIGIN" or “DOMAINSEARCH” statement, this is a finding. If the “DOMAINSEARCH” statement does not specify a proper domain, this is a finding. If the “DOMAINORIGIN” statement does not specify a proper domain, this is a finding.

Fix text

Configure any statement in the “TCPIP DATA” file used during host name resolution such as “DOMAINSEARCH” statement or the "DOMAINORIGIN" statement with a proper domain name.

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.

Powered by sagemincer