OpenControls Logo

STIG Viewer

STIGViewer Support

The Infoblox DNS service member implementation must enforce approved authorizations for controlling the flow of information between DNS service members and between DNS service members and DNS clients based on TSIG policies.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-233911IDNS-8X-700006SV-233911r1082711_ruleCCI-001663medium
Description
A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design. If information flow is not enforced based on approved authorizations, the system may become compromised. Information flow control regulates where information is allowed to travel within a system and between interconnected systems. The flow of all application information must be monitored and controlled so it does not introduce any unacceptable risk to the systems or data. Application-specific examples of enforcement occurs in systems that employ rule sets or establish configuration settings that restrict information system services or provide a message-filtering capability based on message content (e.g., implementing keyword searches or using document characteristics). Applications providing information flow control must be able to enforce approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy. Within the context of DNS, this is applicable in terms of controlling the flow of DNS information between systems, such as DNS zone transfers.
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-001663
1.00

Details

Check Text (C-233911r1082711_chk)

Review the configuration of Infoblox DNS systems and verify that communication flow is validated. 1. Review the Infoblox DNS configuration to verify that only approved communications are allowed. 2. Use of Access Control Lists to control clients, DNS zone transfer configuration to systems external to the Infoblox Grid, and Grid member configuration can be used to control communications as desired. Infoblox DNS service members within the same Grid use internal database updates and do not perform zone transfers. If all DNS service members are within the same Infoblox Grid, this is not a finding. If the Infoblox system is configured to perform zone transfers to non-Grid systems, access control must be used; otherwise, this is a finding.

Fix Text (F-37061r1082710_fix)

Zone transfers can be restricted at the Grid, Member, and Zone level. Configuration is inherited and can be overridden if necessary to construct the appropriate access control. Refer to the Infoblox Administrator Guide if necessary. Grid-level configuration: 1. Navigate to Data Management >> DNS >> Zones tab. 2. Click "Grid DNS Properties" and toggle Advanced Mode. Member-level configuration: 1. Navigate to Data Management >> DNS >> Members tab. 2. Click "Edit" to review each member with the DNS service status of "Running". 3. Zone-level configuration: Navigate to Data Management >> DNS >> Zones tab. 4. Select the "Zone Transfers" tab. 5. Click "Override" to set permissions for "Allow zone transfers to". 6. Configure IPv4 and IPv6 networks, addresses, and TSIG keys to restrict zone transfers.