V-285244

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 IETF's 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

Verify Infoblox is configured to use DNSSEC.

1. Navigate to Data Management >> DNS tab.
2. Click on "Grid DNS Properties" (Toolbar menu). 
3. Click on "DNSSEC" tab. 
4. Verify "Enable DNSSEC" checkbox is selected.
5. When complete, click "Cancel" to exit the "Properties" screen. 
6. Navigate to Data Management >> DNS >> Zones tab. 
7. If screen lists options for "Internal" and "External" (NSG) zone views, click the "External" hyperlink.
8. Verify the "Signed" column is displayed.
9. Validate that all external authoritative zones are signed by displaying "Yes".
10. 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.