OpenControls Logo

STIG Viewer

STIGViewer Support

An authoritative name server must be configured to enable DNSSEC Resource Records.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-265982F5BI-DN-300013SV-265982r1024488_ruleCCI-000366medium
Description
The specification for a digital signature mechanism in the context of the DNS infrastructure is in IETF's DNSSEC standard. In DNSSEC, trust in the public key (for signature verification) of the source is established not by going to a third party or a chain of third parties (as in public key infrastructure [PKI] chaining), but by starting from a trusted zone (such as the root zone) and establishing the chain of trust down to the current source of response through successive verifications of signature of the public key of a child by its parent. The public key of the trusted zone is called the trust anchor. After authenticating the source, the next process DNSSEC calls for is to authenticate the response. DNSSEC mechanisms involve two main processes: sign and serve, and verify signature. Before a DNSSEC-signed zone can be deployed, a name server must be configured to enable DNSSEC processing. Satisfies: SRG-APP-000516-DNS-000089, SRG-APP-000347-DNS-000041, SRG-APP-000348-DNS-000042, SRG-APP-000420-DNS-000053, SRG-APP-000421-DNS-000054, SRG-APP-000158-DNS-000015, SRG-APP-000422-DNS-000055, SRG-APP-000215-DNS-000003, SRG-APP-000423-DNS-000056, SRG-APP-000424-DNS-000057, SRG-APP-000425-DNS-000058, SRG-APP-000426-DNS-000059, SRG-APP-000219-DNS-000030
STIGDate
F5 BIG-IP TMOS DNS Security Technical Implementation Guide2024-09-09

Related Frameworks

13 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (17) 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
IAC-01.2Authenticate, Authorize and Audit (AAA)
1.00
IAC-02Identification & Authentication for Organizational Users
1.00
IAC-03Identification & Authentication for Non-Organizational Users
1.00
IAC-04Identification & Authentication for Devices
1.00
IAC-05Identification & Authentication for Third-Party Technology Assets, Applications and/or Services (TAAS)
1.00
MON-01Continuous Monitoring
1.00

+7 more (top 10 by confidence shown)

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

3.13.15
1.00
3.4.1
1.00
3.4.2
1.00
3.5.1
1.00
3.5.2
1.00
CCI13 mappings
CCI-000366
1.00
CCI-000778
1.00
CCI-001184
1.00
CCI-001663
1.00
CCI-001901
1.00
CCI-001902
1.00
CCI-002462
1.00
CCI-002463
1.00
CCI-002464
1.00
CCI-002465
1.00

+3 more (top 10 by weight shown)

NIST CSF 2.00 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.

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

Who does this work

13 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-265982r1024488_chk)

DNSSEC Keys: From the BIG-IP GUI: 1. DNS. 2. Zones. 3. DNSSEC Zones. 4. DNSSEC Zone List. 5. Click the name of the zone. 6. Verify a key is selected for both "Zone Signing Key" and "Key Signing Key". TSIG Key: 1. DNS. 2. Delivery. 3. Nameservers. 4. Nameserver List. 5. Click the name of the Nameserver. 6. Verify a value is selected for "TSIG Key". If the BIG-IP DNS implementation is not configured to enable DNSSEC Resource Records, this is a finding.

Fix Text (F-69808r1023202_fix)

DNSSEC Keys: From the BIG-IP GUI: 1. DNS. 2. Zones. 3. DNSSEC Zones. 4. DNSSEC Zone List. 5. Click the name of the zone. 6. Move a key for both "Zone Signing Key" and "Key Signing Key" into the "Active" column. 7. Click "Update". Note: To create a Zone Signing Key and/or Key Signing Key, go to DNS >> Delivery >> Keys >> DNSSEC Key List. TSIG Key: 1. DNS. 2. Delivery. 3. Nameservers. 4. Nameserver List. 5. Click on the name of the Nameserver. 6. Select a value from the drop-down for "TSIG Key". 7. Click "Update". Note: To create a TSIG Key, go to DNS >> Delivery >> Keys >> TSIG Key List.