STIGhubSTIGhub
STIGhub— A free STIG search and compliance tool·STIGs updated 12 hours ago
Powered by Pylon·Privacy·Terms·Feedback·© 2026 Beacon Cloud Solutions, Inc.
← Back to Infoblox NIOS 9.x Security Technical Implementation Guide

V-285239

CAT II (Medium)

The Infoblox DNS service member must authenticate another DNS service member before establishing a remote and/or network connection using bidirectional authentication that is cryptographically based.

Rule ID

SV-285239r1258915_rule

STIG

Infoblox NIOS 9.x Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000186CCI-000778CCI-001184CCI-001904CCI-001958CCI-001967

Discussion

To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every pair of name servers. The key also can be used for securing other transactions, such as dynamic updates, DNS queries, and responses. The binary key string that is generated by most key generation utilities used with DNSSEC is Base64-encoded. TSIG is a string used to generate the message authentication hash stored in a TSIG RR and used to authenticate an entire DNS message. The process of authenticating the source of a message and its integrity through hash-based message authentication codes (HMAC) is specified through a set of DNS specifications known collectively as TSIG. The sender of the message uses the HMAC function to generate a MAC and sends this MAC along with the message to the receiver. The receiver, who shares the same secret key, uses the key and HMAC function used by the sender to compute the MAC on the received message. The receiver then compares the computed MAC with the received MAC; if the two values match, it provides assurance that the message has been received correctly and that the sender belongs to the community of users sharing the same secret key. Thus, message source authentication and integrity verification are performed in a single process. To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every pair of name servers. The key also can be used for securing other transactions, such as dynamic updates, DNS queries, and responses. The binary key string that is generated by most key generation utilities used with DNSSEC is Base64-encoded. TSIG is a string used to generate the message authentication hash stored in a TSIG RR and used to authenticate an entire DNS message. Satisfies: SRG-APP-000158-DNS-000076, SRG-APP-000158-DNS-000015, SRG-APP-000219-DNS-000028, SRG-APP-000349-DNS-000043, SRG-APP-000394-DNS-000049, SRG-APP-000395-DNS-000050

Check Content

Verify that Infoblox external logging is configured to use TSIG keys to validate zone transfers to non-Grid systems.

1. Navigate to Data Management >> DNS >> Zones tab. 
2. Review each zone by clicking "Edit" and inspecting the "DNS service members" tab. If using Name Server Groups, select the "Name Servers" tab. 
Note: If all entries in the "Type" column are configured as "Grid", this check is Not Applicable. 
3. Navigate to Data Management >> DNS >> Members tab. 
4. Select each non-Grid DNS service member, and click the "Edit".
5. Click the "Zone Transfers" tab and verify configuration of TSIG Access Control Entry (ACE). 
6. When complete, click "Cancel" to exit the "Properties" screen. 

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: 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.

And/or 

1. Navigate to Data Management >> DNS >> Zones tab. 
2. Select a zone and click "Edit".
3. Click on the "Name Servers" tab and if there are external secondaries, check the box next to the name server and click the edit icon.
4. Check the box for "Use TSIG" and configure key information.
5. When complete, click "Save & Close" to save the changes and exit the "Properties" screen.
6. Perform a service restart if necessary.
7. Verify zone transfers are operational after configuration of TSIG.