OpenControls Logo

STIG Viewer

STIGViewer Support

The Infoblox DNS service member must provide additional integrity artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-233908IDNS-8X-700003SV-233908r1082705_ruleCCI-002462medium
Description
The major threat associated with DNS forged responses or failures is the integrity of the DNS data returned in the response. The principle of DNSSEC is to mitigate this threat by providing data origin authentication, establishing trust in the source. This requirement enables remote clients to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. A DNS server is an example of an information system providing name/address resolution service. Digital signatures and cryptographic keys are examples of additional artifacts. DNS resource records are examples of authoritative data. Applications other than the DNS to map between host/service names and network addresses must provide other means to ensure the authenticity and integrity of response data. In the case of DNS, employ DNSSEC to provide an additional data origin and integrity artifacts along with the authoritative data the system returns in response to DNS name/address resolution queries.
STIGDate
Infoblox 8.x DNS Security Technical Implementation Guide2026-06-03

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

NET-10Domain Name Service (DNS) Resolution
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (10) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AU-10(1)Association of Identities
1.00
AU-10(2)Validate Binding of Information Producer Identity
1.00
CM-6Configuration Settings
1.00
IA-3Device Identification and Authentication
1.00
SC-20Secure Name/Address Resolution Service (Authoritative Source)
1.00
SC-20(2)Data Origin and Integrity
1.00
SC-21Secure Name/Address Resolution Service (Recursive or Caching Resolver)
1.00
SC-23Session Authenticity
1.00
SC-8(2)Pre- and Post-transmission Handling
1.00
SI-10Information Input Validation
1.00
CCI1 mapping
CCI-002462
1.00

Details

Check Text (C-233908r1082705_chk)

Note: For Infoblox DNS systems on a classified network, this requirement is Not Applicable. 1. Verify that DNSSEC validation is enabled by navigating to Data Management >> DNS >> Grid DNS properties. 2. Toggle Advanced Mode and click on the "DNSSEC" tab. 3. Verify that both "Enable DNSSEC" and "Enable DNSSEC validation" are enabled. 4. When complete, click "Cancel" to exit the "Properties" screen. If both "Enable DNSSEC" and "Enable DNSSEC validation" are not enabled, this is a finding.

Fix Text (F-37058r611245_fix)

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