← Back to Infoblox 8.x DNS Security Technical Implementation Guide

V-233924

CAT II (Medium)

The Infoblox DNS service member must implement cryptographic mechanisms to detect changes to information during transmission unless otherwise protected by alternative physical safeguards, such as, at a minimum, a Protected Distribution System (PDS).

Rule ID

SV-233924r1082738_rule

STIG

Infoblox 8.x DNS Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-002421

Discussion

Encrypting information for transmission protects it from unauthorized disclosure and modification. Cryptographic mechanisms implemented to protect information integrity include, for example, cryptographic hash functions that have common application in digital signatures, checksums, and message authentication codes. Confidentiality is not an objective of DNS, but integrity is. DNSSEC digitally signs DNS information to authenticate its source and ensure its integrity. DNSSEC is intended for third-party authenticity determination. Attempting to utilize DNSSEC internally was never an intended use case as it would require every consumer to have a third-party validating resolver installed along with a mechanism for periodic trust anchor distribution/update. It is recommended for external zones only.

Check Content

Note: For Infoblox DNS systems on a classified network, this requirement is Not Applicable.  

1. Verify that DNSSEC is enabled by navigating to Data Management >> DNS >> Grid DNS properties tab. 
2. Toggle Advanced Mode and review the "DNSSEC" tab to verify that DNSSEC is enabled. 
3. When complete, click "Cancel" to exit the "Properties" screen. 

If DNSSEC validation is not enabled, this is a finding.

Fix Text

1. Navigate to Data Management >> DNS >> Grid DNS properties tab. 
2. Toggle Advanced Mode and select the "DNSSEC" tab.  
3. Enable DNSSEC by selecting the check box.  
4. When complete, click "Save & Close" to save the changes and exit the "Properties" screen.  
5. Perform a service restart if necessary.