STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Infoblox 8.x DNS Security Technical Implementation Guide

V-233899

CAT II (Medium)

When using third-party DNS servers for zone transfers, each DNS server must use TSIG to uniquely identify the other server.

Rule ID

SV-233899r1082685_rule

STIG

Infoblox 8.x DNS Security Technical Implementation Guide

Version

V1R2

CCIs

CCI-000778

Discussion

Without identifying devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. This applies to server-to-server (zone transfer) transactions only and is provided by TSIG, which enforces mutual server authentication using a key that is unique to each server pair (TSIG), thus uniquely identifying the other server.

Check Content

1. Navigate to Data Management >> DNS >> Zones tab. 
2. Review each zone by clicking "Edit" and inspecting the "DNS service members" tab. 
3. Verify that each zone that contains non-Grid DNS service members is further verified by inspection of the "Zone Transfers" tab and configuration of TSIG Access Control Entry (ACE). 
4. When complete, click "Cancel" to exit the "Properties" screen.  

If all entries in the "Type" column are configured as "Grid", this check is Not Applicable.

If there is a non-Grid system that uses zone transfers but does not have a TSIG key, this is a finding.

Fix Text

1. Navigate to Data Management >> DNS >> Zones tab.  
2. Select a zone and click "Edit".
3. Click on the "Zone Transfers" tab and click "Override" for the "Allow Zone Transfers to" section.
4. Use the radio button to select "Set of ACEs" and the "Add" drop-down to configure a TSIG key. 
5. Verify that both the Infoblox and other DNS service member have the identical TSIG configuration. 
6. Verify that both the Infoblox DNS service member and other non-Infoblox DNS service member have time synchronized properly. Note that TSIG relies on both key and time synchronization. TSIG will fail if the local clocks on both DNS service appliances are not synchronized.
7. When complete, click "Save & Close" to save the changes and exit the "Properties" screen.
8. Perform a service restart if necessary.
9. Verify zone transfers are operational after configuration of TSIG.