Detections
Analytics

BIND-9X-001430 - The BIND 9.x server implementation must implement internal/external role separation.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

DNS servers with an internal role only process name/address resolution requests from within the organization (i.e., internal clients). DNS servers with an external role only process name/address resolution information requests from clients external to the organization (i.e., on the external networks, including the internet). The set of clients that can access an authoritative DNS server in a particular role is specified by the organization using address ranges, explicit access control lists, etc. To protect internal DNS resource information, it is important to isolate the requests to internal DNS servers.

Failure to separate internal and external roles in DNS may lead to address space that is private (e.g., 10.0.0.0/24) or is otherwise concealed by some form of Network Address Translation from leaking into the public DNS system. Allowing private IP space to leak into the public DNS system may provide a person with malicious intent the ability to footprint the network and identify potential attack targets residing on the private network.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

Edit the 'named.conf' file.

Configure the internal and external view statements to use separate network segments.

Configure all internal view statements to be listed before any external view statement.

Restart the BIND 9.x process.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_BIND_9-x_V3R1_STIG.zip

Item Details

References: CAT|II, CCI|CCI-000366, Rule-ID|SV-272399r1124058_rule, STIG-ID|BIND-9X-001430, Vuln-ID|V-272399

Plugin: Unix

Control ID: c66535ad162f794cf76c38b8db0147d1ce26a48524bae71429fc8424acfb15c9