OpenControls Logo

STIG Viewer

STIGViewer Support

The F5 BIG-IP DNS must use valid root name servers in the local root zone file.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-265984F5BI-DN-300015SV-265984r1024858_ruleCCI-000366medium
Description
All caching name servers must be authoritative for the root zone because, without this starting point, they would have no knowledge of the DNS infrastructure and thus would be unable to respond to any queries. The security risk is that an adversary could change the root hints and direct the caching name server to a bogus root server. At that point, every query response from that name server is suspect, which would give the adversary substantial control over the network communication of the name servers' clients. When authoritative servers are sent queries for zones that they are not authoritative for, and they are configured as a noncaching server (as recommended), they can either be configured to return a referral to the root servers or they can be configured to refuse to answer the query. The recommendation is to configure authoritative servers to refuse to answer queries for any zones for which they are not authoritative. This is more efficient for the server and allows it to spend more of its resources doing what its intended purpose is, answering authoritatively for its zone.
STIGDate
F5 BIG-IP TMOS DNS Security Technical Implementation Guide2024-09-09

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (8) 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.

CFG-01Configuration Management Program
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
MON-01Continuous Monitoring
1.00
MON-01.7File Integrity Monitoring (FIM)
1.00
CFG-02Secure Baseline Configurations
0.50
CFG-02.7Approved Configuration Deviations
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) 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.

AC-12Session Termination
1.00
AC-16(1)Dynamic Attribute Association
1.00
AC-17(1)Monitoring and Control
1.00
AC-2Account Management
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-24(1)Transmit Access Authorization Information
1.00
AC-25Reference Monitor
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) 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.

3.4.1
1.00
3.4.2
1.00
CCI1 mapping
CCI-000366
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) 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.

DE.CM-09
1.00
PR.PS-01
1.00
PR.DS-10
0.50
PR.PSPlatform Security
0.50
PR.PS-05
0.50

Who does this work

10 NICE work roles and 9 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-265984r1024858_chk)

This is only applicable if DNS recursion is being performed by the BIG-IP AND a custom root hint list must be defined. From the BIG-IP GUI: 1. DNS. 2. Zones. 3. ZoneRunner. 4. Zone List. 5. Verify there is no Zone Name called ".". 6. If a "." Zone Name exists, log in to the BIG-IP CLI and run the following commands: cat /var/named/config/namedb/db.external.named.root. 7. Verify valid root name servers are configured. If the BIG-IP appliance is not configured to use valid root name servers in the local root zone file, this is a finding.

Fix Text (F-69810r1024857_fix)

This is only applicable if DNS recursion is being performed by the BIG-IP AND a custom root hint list must be defined. Enable recursion for named: From the BIG-IP GUI: 1. DNS. 2. Zones. 3. ZoneRunner. 4. Named Configuration. 5. Change the recursion option to "recursion yes;". 6. Click "Update". Create a hint zone using ZoneRunner: From the BIG-IP GUI: 1. DNS. 2. Zones. 3. ZoneRunner. 4. Zone List. 5. Create. 6. For the View Name option, select the view for which the hint zone will apply. 7. For the Zone Name, enter a period character "." (without quotes). 8. For the Zone Type, select "Hint". 9. Change the Zone File Name to "db.external.named.root." (without quotes). 10. Click "Finished". Edit the hint zone file: From the BIG-IP CLI: 1. Edit the root hint file: vi /var/named/config/namedb/db.external.named.root. 2. Paste the list of valid root name servers. Note: A copy of the latest root server list can be found at the following location: http://www.internic.net/zones/named.cache. 3. Save the file. 4. Update the time stamp on: /var/named/config/named.conf touch /var/named/config/named.conf 5. Restart named: tmsh restart /sys service named 6. Restart zrd: tmsh restart /sys service zrd Note: The hint zone does not display any information when viewed in the ZoneRunner Configuration utility. The information is used by named for the purpose of querying and receiving the most up-to-date list of root servers. It cannot be updated or modified using the ZoneRunner utility.