Infoblox 7.x DNS Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
A DNS server implementation must perform data integrity verification on the name/address resolution responses the system receives from authoritative sources.
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 intercep...Rule Medium Severity -
A DNS server implementation must perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.
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 intercep...Rule Medium Severity -
The DNS server implementation must maintain the integrity of information during reception.
Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/un...Rule Medium Severity -
The DNS server implementation must follow procedures to re-role a secondary name server as the master name server should the master name server permanently lose functionality.
Failing to an unsecure condition negatively impacts application security and can lead to system compromise. Failure conditions include, for example, loss of communications among critical system com...Rule Medium Severity -
NSEC3 must be used for all internal DNS zones.
To ensure that RRs associated with a query are really missing in a zone file and have not been removed in transit, the DNSSEC mechanism provides a means for authenticating the nonexistence of an RR...Rule Medium Severity -
Digital signature algorithm used for DNSSEC-enabled zones must be FIPS-compatible.
The choice of digital signature algorithm will be based on recommended algorithms in well-known standards. NIST's Digital Signature Standard (DSS) [FIPS186] provides three algorithm choices: * Digi...Rule High Severity -
In a split DNS configuration, where separate name servers are used between the external and internal networks, the external name server must be configured to not be reachable from inside resolvers.
Instead of having the same set of authoritative name servers serve different types of clients, an enterprise could have two different sets of authoritative name servers. One set, called external ...Rule Medium Severity -
The DNS implementation must implement internal/external role separation.
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 re...Rule Medium Severity -
The Infoblox system must utilize valid root name servers in the local root zone file.
All caching name servers must be authoritative for the root zone because, without this starting point, they would have no knowledge of the DNS infrastructure and thus would be unable to respond to ...Rule Medium Severity -
The platform on which the name server software is hosted must be configured to respond to DNS traffic only.
OS configuration practices as issued by the US Computer Emergency Response Team (US CERT) and the National Institute of Standards and Technology's (NIST's) National Vulnerability Database (NVD), ba...Rule Medium Severity -
The private keys corresponding to both the ZSK and the KSK must not be kept on the DNSSEC-aware primary authoritative name server when the name server does not support dynamic updates.
The private keys in the KSK and ZSK key pairs must be protected from unauthorized access. If possible, the private keys should be stored off-line (with respect to the Internet-facing, DNSSEC-aware ...Rule Medium Severity -
Infoblox systems must be configured with current DoD password restrictions.
The Infoblox systems must be configured to meet current DoD password policy when using the Infoblox Local User Database as the authentication source.Rule High Severity -
All authoritative name servers for a zone must be geographically disbursed.
In addition to network-based dispersion, authoritative name servers should be dispersed geographically as well. In other words, in addition to being located on different network segments, the autho...Rule Medium Severity -
SRG-APP-000516-DNS-000095
Group -
SRG-APP-000001-DNS-000115
Group -
The Infoblox system must limit the number of concurrent client connections to the number of allowed dynamic update clients.
Limiting the number of concurrent sessions reduces the risk of Denial of Service (DoS) to the DNS implementation. Name servers do not have direct user connections but accept client connections for...Rule Medium Severity -
SRG-APP-000125-DNS-000012
Group -
The Infoblox system audit records must be backed up at least every seven days onto a different system or system component than the system or component being audited.
Protection of log data includes assuring log data is not accidentally lost or deleted. Backing up audit records to a different system or onto separate media than the system being audited on a defin...Rule Medium Severity -
SRG-APP-000142-DNS-000014
Group -
SRG-APP-000158-DNS-000015
Group
Node 2
The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.