800-53|SC-20

Title

SECURE NAME / ADDRESS RESOLUTION SERVICE (AUTHORITATIVE SOURCE)

Description

The information system:

Supplemental

This control enables external clients including, for example, remote Internet clients, to obtain origin authentication and integrity verification assurances for the host/service name to network address resolution information obtained through the service. Information systems that provide name and address resolution services include, for example, domain name system (DNS) servers. Additional artifacts include, for example, DNS Security (DNSSEC) digital signatures and cryptographic keys. DNS resource records are examples of authoritative data. The means to indicate the security status of child zones includes, for example, the use of delegation signer resource records in the DNS. The DNS security controls reflect (and are referenced from) OMB Memorandum 08-23. Information systems that use technologies other than the DNS to map between host/service names and network addresses provide other means to assure the authenticity and integrity of response data.

Reference Item Details

Related: AU-10,SC-12,SC-13,SC-21,SC-22,SC-8

Category: SYSTEM AND COMMUNICATIONS PROTECTION

Family: SYSTEM AND COMMUNICATIONS PROTECTION

Priority: P1

Baseline Impact: LOW,MODERATE,HIGH

Audit Items

View all Reference Audit Items

NamePluginAudit Name
1.1 Ensure DNS server is configuredFortiGateCIS FortiGate 7.4.x v1.0.1 L1
1.1 Ensure DNS server is configuredFortiGateCIS Fortigate 7.0.x v1.4.0 L1
1.1.6 DNS ConfigurationAristaCIS Arista EOS benchmark v1.0.0 L1
1.17 EX19-ED-000095WindowsCIS Microsoft Exchange 2019 Edge Server STIG v1.0.0 CAT II
1.26 EX19-MB-000106WindowsCIS Microsoft Exchange 2019 Mailbox Server STIG v1.0.0 CAT II
2.1.5 Ensure hostname is setFortiGateCIS FortiGate 7.4.x v1.0.1 L1
2.1.5 Ensure hostname is setFortiGateCIS Fortigate 7.0.x v1.4.0 L1
2.1.6 Ensure DNS server is configured - primaryCheckPointCIS Check Point Firewall L1 v1.1.0
3.1 Ensure DNS services are configured correctly - name-serverCiscoCIS Cisco Firewall v8.x L1 v4.2.0
3.2 Restrict Recursive Queries - Authoritative Name ServerUnixCIS BIND DNS v3.0.1 Authoritative Name Server
3.4 Restrict Queries of the Cache - Authoritative OnlyUnixCIS BIND DNS v3.0.1 Authoritative Name Server
5.4 CIFS - 'dns.domainname has been configured'NetAppTNS NetApp Data ONTAP 7G
5.4 CIFS - 'dns.enable = on'NetAppTNS NetApp Data ONTAP 7G
5.4 CIFS - 'dns.update.enable = on or secure'NetAppTNS NetApp Data ONTAP 7G
5.7.4 The default namespace should not be usedOpenShiftCIS Red Hat OpenShift Container Platform v1.9.0 L2 OpenShift
6.1 Ensure Root Domain Alias Record Points to ELBamazon_awsCIS Amazon Web Services Three-tier Web Architecture L2 1.0.0
6.2 Ensure a DNS alias record for the root domainamazon_awsCIS Amazon Web Services Three-tier Web Architecture L2 1.0.0
7.4 Ensure Either SPF or DKIM DNS Records are ConfiguredUnixCIS BIND DNS v1.0.0 L2 Authoritative Name Server
8.3 Ensure Any Signing Keys using RSA Have a Length of 2048 or GreaterUnixCIS BIND DNS v1.0.0 L2 Authoritative Name Server
Adtran : Ensure a trusted, primary DNS server is setAdtranTNS Adtran AOS Best Practice Audit
Adtran : Ensure a trusted, secondary DNS server is setAdtranTNS Adtran AOS Best Practice Audit
BIND-9X-001650 - A BIND 9.x server implementation must maintain the integrity and confidentiality of DNS information while it is being prepared for transmission, in transmission, and in use and must perform integrity verification and data origin verification for all DNS information.UnixDISA BIND 9.x STIG v3r3
DNS Profile - Address - DNS Server 1Cisco_ACITenable Cisco ACI
DNS Profile - Address - DNS Server 2Cisco_ACITenable Cisco ACI
DNS: A trusted primary DNS server is configuredAlcatelTNS Alcatel-Lucent TiMOS/Nokia SR-OS Best Practice Audit
DNS: A trusted secondary DNS server is configuredAlcatelTNS Alcatel-Lucent TiMOS/Nokia SR-OS Best Practice Audit
Ensure DNS services are configured correctly - name-serverCiscoTenable Cisco Firepower Best Practices Audit
Ensure DNS services are configured correctly - name-serverCisco_FirepowerTenable Cisco Firepower Threat Defense Best Practices Audit
F5BI-DN-300013 - An authoritative name server must be configured to enable DNSSEC Resource Records.F5DISA F5 BIG-IP TMOS DNS STIG v1r1
FireEye - The appliance uses a trusted DNS serverFireEyeTNS FireEye
Fortigate - DNS - primary serverFortiGateTNS Fortigate FortiOS Best Practices v2.0.0
Fortigate - DNS - secondary serverFortiGateTNS Fortigate FortiOS Best Practices v2.0.0
GEN001375-ESXI5-000086 - For systems using DNS resolution, at least two name servers must be configured.VMwareDISA VMWare ESXi 5.0 Server STIG v2r1
SonicWALL - Review the DNS Server SettingsSonicWALLTNS SonicWALL v5.9
WatchGuard : DNS ServersWatchGuardTNS Best Practice WatchGuard Audit 1.0.0
WDNS-SC-000003 - The Windows 2012 DNS Servers IP address must be statically defined and configured locally on the server.WindowsDISA Microsoft Windows 2012 Server Domain Name System STIG v2r7
WDNS-SC-000004 - The Windows 2012 DNS Server must return data information in responses to internal name/address resolution queries.WindowsDISA Microsoft Windows 2012 Server Domain Name System STIG v2r7
WDNS-SC-000005 - The Windows 2012 DNS Server must use DNSSEC data within queries to confirm data origin to DNS resolvers.WindowsDISA Microsoft Windows 2012 Server Domain Name System STIG v2r7