UCF STIG Viewer Logo

Domain Name System (DNS) Security Requirements Guide


Overview

Date Finding Count (97)
2023-06-12 CAT I (High): 1 CAT II (Med): 96 CAT III (Low): 0
STIG Description
This Security Requirements Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Available Profiles



Findings (MAC III - Administrative Sensitive)

Finding ID Severity Title
V-205216 High The DNS server implementation must protect the integrity of transmitted information.
V-205235 Medium Digital signature algorithm used for DNSSEC-enabled zones must be FIPS-compatible.
V-205234 Medium An authoritative name server must be configured to enable DNSSEC Resource Records.
V-205237 Medium In a split DNS configuration, where separate name servers are used between the external and internal networks, the external name server must be configured to not be reachable from inside resolvers.
V-205236 Medium For zones split between the external and internal sides of a network, the RRs for the external hosts must be separate from the RRs for the internal hosts.
V-205231 Medium The two files generated by the dnssec-keygen program must be made accessible only to the server administrator account, or deleted, after they have been copied to the key file in the name server.
V-205230 Medium The DNS implementation must ensure each NS record in a zone file points to an active name server authoritative for the domain specified in that record.
V-205233 Medium All authoritative name servers for a zone must have the same version of zone information.
V-205232 Medium All authoritative name servers for a zone must be located on different network segments.
V-205239 Medium Primary authoritative name servers must be configured to only receive zone transfer requests from specified secondary name servers.
V-205238 Medium In a split DNS configuration, where separate name servers are used between the external and internal networks, the internal name server must be configured to not be reachable from outside resolvers.
V-205158 Medium The DNS implementation must limit the number of concurrent sessions client connections to the number of allowed dynamic update clients.
V-205159 Medium The DNS server implementation must be configured to provide audit record generation capability for DoD-defined auditable events within all DNS server components.
V-205242 Medium The DNS implementation must implement internal/external role separation.
V-205243 Medium The DNS must utilize valid root name servers in the local root zone file.
V-205244 Medium The DNS name server software must be at the latest version.
V-205245 Medium The DNS Name Server software must run with restricted privileges.
V-205246 Medium The IP address for hidden master authoritative name servers must not appear in the name servers set in the zone database.
V-205247 Medium The platform on which the name server software is hosted must be configured to respond to DNS traffic only.
V-205248 Medium The platform on which the name server software is hosted must be configured to send outgoing DNS messages from a random port.
V-205249 Medium The private key corresponding to the ZSK, stored on name servers accepting dynamic updates, must have appropriate directory/file-level access control list-based or cryptography-based protections.
V-205157 Medium The DNS implementation must limit the number of concurrent sessions for zone transfers to the number of secondary name servers.
V-205253 Medium The DNS server implementation must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs.
V-205252 Medium CNAME records must not point to a zone with lesser security for more than six months.
V-205251 Medium A zone file must not include resource records that resolve to a fully qualified domain name residing in another zone.
V-205250 Medium The private keys corresponding to both the ZSK and the KSK must not be kept on the DNSSEC-aware primary authoritative name server when the name server does not support dynamic updates.
V-220317 Medium All authoritative name servers for a zone must be geographically disbursed.
V-220316 Medium A unique TSIG key must be generated for each pair of communicating hosts.
V-205178 Medium The validity period for the RRSIGs covering the DS RR for a zones delegated children must be no less than two days and no more than one week.
V-205179 Medium The DNS server implementation must enforce approved authorizations for controlling the flow of information between DNS servers and between DNS servers and DNS clients based on DNSSEC policies.
V-205176 Medium A DNS server implementation must provide additional data origin artifacts along with the authoritative data the system returns in response to external name/address resolution queries.
V-205177 Medium A DNS server implementation must provide the means to indicate the security status of child zones.
V-205174 Medium Signature generation using the KSK must be done off-line, using the KSK-private stored off-line.
V-205175 Medium The DNS server implementation must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions.
V-205172 Medium Read/Write access to the key file must be restricted to the account that runs the name server software only.
V-205173 Medium Only the private key corresponding to the ZSK alone must be kept on the name server that does support dynamic updates.
V-205170 Medium The DNS server implementation, when using PKI-based authentication, must enforce authorized access to the corresponding private key.
V-205171 Medium The key file must be owned by the account under which the name server software is run.
V-205161 Medium The DNS server implementation must produce audit records containing information to establish what type of events occurred.
V-205160 Medium The DNS server implementation must be configured to provide audit record generation capability for DoD-defined auditable events within all DNS server components.
V-205163 Medium The DNS server implementation must produce audit records containing information to establish where the events occurred.
V-205162 Medium The DNS server implementation must produce audit records containing information to establish when (date and time) the events occurred.
V-205165 Medium The DNS server implementation must produce audit records that contain information to establish the outcome of the events.
V-205164 Medium The DNS server implementation must produce audit records containing information to establish the source of the events.
V-205167 Medium The DNS server implementations audit records must be backed up at least every seven days onto a different system or system component than the system or component being audited.
V-205166 Medium The DNS server implementation must generate audit records containing information that establishes the identity of any individual or process associated with the event.
V-205169 Medium The DNS server implementation must uniquely identify the other DNS server before responding to a server-to-server transaction.
V-205168 Medium The DNS server implementation must be configured to prohibit or restrict unapproved ports and protocols.
V-205208 Medium A DNS server implementation must provide additional integrity artifacts along with the authoritative name resolution data the system returns in response to external name/address resolution queries.
V-205209 Medium A DNS server implementation must request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources.
V-205204 Medium The DNS server implementation must authenticate another DNS server before establishing a remote and/or network connection using bidirectional authentication that is cryptographically based.
V-205205 Medium The DNS server implementation, for PKI-based authentication, must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network.
V-205206 Medium A DNS server implementation must provide data origin artifacts for internal name/address resolution queries.
V-205207 Medium A DNS server implementation must provide data integrity protection artifacts for internal name/address resolution queries.
V-205201 Medium The DNS implementation must prohibit recursion on authoritative name servers.
V-205202 Medium The DNS server implementation must require devices to re-authenticate for each zone transfer and dynamic update request connection attempt.
V-205203 Medium The DNS server implementation must authenticate the other DNS server before responding to a server-to-server transaction.
V-205219 Medium The DNS server implementation must maintain the integrity of information during reception.
V-205218 Medium The DNS server implementation must maintain the integrity of information during preparation for transmission.
V-205217 Medium The DNS server implementation must implement cryptographic mechanisms to detect changes to information during transmission unless otherwise protected by alternative physical safeguards, such as, at a minimum, a Protected Distribution System (PDS).
V-205215 Medium The DNS server implementation must utilize cryptographic mechanisms to prevent unauthorized disclosure of non-DNS data stored on the DNS server.
V-205214 Medium The DNS server implementation must utilize cryptographic mechanisms to prevent unauthorized modification of DNS zone data.
V-205213 Medium If the DNS server is using SIG(0), the DNS server implementation must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected transactions.
V-205212 Medium A DNS server implementation must perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.
V-205211 Medium A DNS server implementation must perform data integrity verification on the name/address resolution responses the system receives from authoritative sources.
V-205210 Medium A DNS server implementation must request data integrity verification on the name/address resolution responses the system receives from authoritative sources.
V-205198 Medium The DNS server implementation must validate the binding of the other DNS servers identity to the DNS information for a server-to-server transaction (e.g., zone transfer).
V-205199 Medium In the event of an error when validating the binding of another DNS servers identity to the DNS information, the DNS server implementation must log the event and send notification to the DNS administrator.
V-205194 Medium The DNS Name Server software must be configured to refuse queries for its version information.
V-205195 Medium The HINFO, RP, TXT and LOC RR types must not be used in the zone SOA.
V-205196 Medium The DNS server implementation must strongly bind the identity of the DNS server with the DNS information.
V-205197 Medium The DNS server implementation must provide the means for authorized individuals to determine the identity of the source of the DNS server-provided information.
V-205190 Medium The DNS server implementation must manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of Denial of Service (DoS) attacks.
V-205191 Medium The DNS server implementation must check the validity of all data inputs except those specifically identified by the organization.
V-205192 Medium The DNS server implementation must, when a component failure is detected, activate a notification to the system administrator.
V-205193 Medium The DNS server implementation must be configured to generate audit records for failed security verification tests so that the ISSO and ISSM can be notified of the failures.
V-205222 Medium The DNS server implementation must perform verification of the correct operation of security functions: upon system start-up and/or restart; upon command by a user with privileged access; and/or every 30 days.
V-205223 Medium The DNS server implementation must log the event and notify the system administrator when anomalies in the operation of the signed zone transfers are discovered.
V-205220 Medium The DNS server implementation must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.
V-205221 Medium The DNS server implementation must follow procedures to re-role a secondary name server as the master name server should the master name server permanently lose functionality.
V-205226 Medium The DNS server must implement NIST FIPS-validated cryptography for provisioning digital signatures, generating cryptographic hashes, and protecting unclassified information requiring confidentiality.
V-205227 Medium The salt value for zones signed using NSEC3 RRs must be changed every time the zone is completely re-signed.
V-205224 Medium The DNS implementation must generate audit records for the success and failure of start and stop of the name server service or daemon.
V-205225 Medium The DNS implementation must generate audit records for the success and failure of all name server events.
V-205228 Medium The validity period for the RRSIGs covering a zones DNSKEY RRSet must be no less than two days and no more than one week.
V-205229 Medium NSEC3 must be used for all internal DNS zones.
V-205240 Medium The DNS implementation must be conformant to the IETF DNS specification.
V-205241 Medium The DNS implementation must enforce a Discretionary Access Control (DAC) policy that limits propagation of access rights.
V-205189 Medium The DNS server implementation must restrict the ability of individuals to use the DNS server to launch Denial of Service (DoS) attacks against other information systems.
V-205188 Medium The DNS server implementation must prevent unauthorized and unintended information transfer via shared system resources.
V-205187 Medium The DNS server implementation must protect the confidentiality and integrity of secret/private cryptographic keys at rest and the integrity of DNS information at rest.
V-205186 Medium In the event of a system failure, the DNS server implementation must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.
V-205185 Medium The DNS server implementation must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.
V-205184 Medium The DNS implementation must protect the authenticity of communications sessions for queries.
V-205183 Medium The DNS implementation must protect the authenticity of communications sessions for dynamic updates.
V-205182 Medium The DNS implementation must protect the authenticity of communications sessions for zone transfers.
V-205180 Medium A DNS server implementation must provide the means to enable verification of a chain of trust among parent and child domains (if the child supports secure resolution services).