Title

The Infoblox system must provide additional data origin artifacts along with the authoritative data the system returns in response to external name/address resolution queries. (Cat II impact)

Discussion

The underlying feature in the major threat associated with DNS query/response (i.e., forged response or response failure) is the integrity of DNS data returned in the response. The security objective is to verify the integrity of each response received. An integral part of integrity verification is to ensure that valid data has originated from the right source. Establishing trust in the source is called data origin authentication. The security objectives, and consequently the security services, that are required for securing the DNS query/response transaction are data origin authentication and data integrity verification. The specification for a digital signature mechanism in the context of the DNS infrastructure is in the Internet Engineering Task Force's (IETF's) Domain Name System Security Extension (DNSSEC) standard. In DNSSEC, trust in the public key (for signature verification) of the source is established not by going to a third party or a chain of third parties (as in public key infrastructure [PKI] chaining), but by starting from a trusted zone (such as the root zone) and establishing the chain of trust down to the current source of response through successive verifications of signature of the public key of a child by its parent. The public key of the trusted zone is called the trust anchor.

Check Content

Note: For Infoblox DNS systems on a classified network, this requirement is Not Applicable. 1. Navigate to Data Management >> DNS >> Grid DNS properties. 2. Toggle Advanced Mode, click on "DNSSEC" tab, and verify that "Enable DNSSEC" is enabled. 3. Navigate to Data Management >> DNS >> Zones. Verify that the "Signed" column is displayed. 4. Validate that all external authoritative zones are signed by displaying "Yes". 5. When complete, click "Cancel" to exit the "Properties" screen. If DNSSEC is not enabled and external authoritative zones are not signed, this is a finding.

Fix Text

Note: Ensure DNSSEC is configured to meet all other STIG requirements prior to signing a zone to avoid signing with an unapproved configuration. 1. Navigate to Data Management >> DNS >> Zones tab. 2. Place a check mark in the box next to the desired external authoritative zone. Using the "DNSSEC" drop-down menu in the toolbar, select "Sign zones". 3. Acknowledge the informational banner and the service restart banner if prompted.

Additional Identifiers

Rule ID: SV-233907r621666_rule

Vulnerability ID: V-233907

Group Title: SRG-APP-000213-DNS-000024

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.