| Checked | Name | Title |
|---|
| ☐ | SV-69023r1_rule | The DNS implementation must limit the number of concurrent sessions client connections to the number of allowed dynamic update clients. |
| ☐ | SV-69027r1_rule | The DNS server implementation must be configured to provide audit record generation capability for DoD-defined auditable events within all DNS server components. |
| ☐ | SV-69029r1_rule | The DNS server implementation must be configured to provide audit record generation capability for DoD-defined auditable events within all DNS server components. |
| ☐ | SV-69031r1_rule | The DNS server implementation must produce audit records containing information to establish what type of events occurred. |
| ☐ | SV-69033r1_rule | The DNS server implementation must produce audit records containing information to establish where the events occurred. |
| ☐ | SV-69035r1_rule | The DNS server implementation must produce audit records containing information to establish the source of the events. |
| ☐ | SV-69037r1_rule | The DNS server implementation must produce audit records that contain information to establish the outcome of the events. |
| ☐ | SV-69039r1_rule | The DNS server implementation must generate audit records containing information that establishes the identity of any individual or process associated with the event. |
| ☐ | SV-69041r1_rule | 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. |
| ☐ | SV-69043r1_rule | The DNS server implementation must be configured to prohibit or restrict unapproved ports and protocols. |
| ☐ | SV-69045r1_rule | The DNS server implementation must uniquely identify the other DNS server before responding to a server-to-server transaction. |
| ☐ | SV-69047r1_rule | The DNS server implementation, when using PKI-based authentication, must enforce authorized access to the corresponding private key. |
| ☐ | SV-69049r1_rule | The key file must be owned by the account under which the name server software is run. |
| ☐ | SV-69051r1_rule | Read/Write access to the key file must be restricted to the account that runs the name server software only. |
| ☐ | SV-69053r1_rule | A unique TSIG key must be generated for each pair of communicating hosts. |
| ☐ | SV-69055r1_rule | Only the private key corresponding to the ZSK alone must be kept on the name server that does support dynamic updates. |
| ☐ | SV-69057r1_rule | Signature generation using the KSK must be done off-line, using the KSK-private stored off-line. |
| ☐ | SV-69059r1_rule | The DNS server implementation must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
| ☐ | SV-69061r1_rule | 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. |
| ☐ | SV-69063r1_rule | A DNS server implementation must provide the means to indicate the security status of child zones. |
| ☐ | SV-69065r1_rule | 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. |
| ☐ | SV-69067r1_rule | 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. |
| ☐ | SV-69069r1_rule | 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). |
| ☐ | SV-69071r1_rule | The DNS implementation must protect the authenticity of communications sessions for zone transfers. |
| ☐ | SV-69073r1_rule | The DNS implementation must protect the authenticity of communications sessions for dynamic updates. |
| ☐ | SV-69075r1_rule | The DNS implementation must protect the authenticity of communications sessions for queries. |
| ☐ | SV-69077r1_rule | The DNS server implementation must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |
| ☐ | SV-69079r1_rule | 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. |
| ☐ | SV-69081r1_rule | 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. |
| ☐ | SV-69083r1_rule | The DNS server implementation must prevent unauthorized and unintended information transfer via shared system resources. |
| ☐ | SV-69085r1_rule | 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. |
| ☐ | SV-69087r1_rule | 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. |
| ☐ | SV-69089r1_rule | The DNS server implementation must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-69091r1_rule | 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. |
| ☐ | SV-69093r1_rule | The DNS Name Server software must be configured to refuse queries for its version information. |
| ☐ | SV-69095r1_rule | The HINFO, RP, TXT and LOC RR types must not be used in the zone SOA. |
| ☐ | SV-69097r1_rule | The DNS server implementation must be configured to allow DNS administrators to change the auditing to be performed on all DNS server components, based on all selectable event criteria. |
| ☐ | SV-69099r1_rule | The DNS implementation must limit the number of concurrent sessions for zone transfers to the number of secondary name servers. |
| ☐ | SV-69101r2_rule | The DNS implementation must prohibit recursion on authoritative name servers. |
| ☐ | SV-69103r1_rule | The DNS server implementation must require devices to re-authenticate for each zone transfer and dynamic update request connection attempt. |
| ☐ | SV-69107r1_rule | The DNS server implementation must authenticate the other DNS server before responding to a server-to-server transaction. |
| ☐ | SV-69109r1_rule | The DNS server implementation must authenticate another DNS server before establishing a remote and/or network connection using bidirectional authentication that is cryptographically based. |
| ☐ | SV-69111r1_rule | 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. |
| ☐ | SV-69113r1_rule | A DNS server implementation must provide data origin artifacts for internal name/address resolution queries. |
| ☐ | SV-69115r1_rule | A DNS server implementation must provide data integrity protection artifacts for internal name/address resolution queries. |
| ☐ | SV-69117r1_rule | 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. |
| ☐ | SV-69119r1_rule | A DNS server implementation must request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources. |
| ☐ | SV-69121r1_rule | A DNS server implementation must request data integrity verification on the name/address resolution responses the system receives from authoritative sources. |
| ☐ | SV-69123r1_rule | A DNS server implementation must perform data integrity verification on the name/address resolution responses the system receives from authoritative sources. |
| ☐ | SV-69131r1_rule | A DNS server implementation must perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources. |
| ☐ | SV-69133r1_rule | 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. |
| ☐ | SV-69135r1_rule | The DNS server implementation must utilize cryptographic mechanisms to prevent unauthorized disclosure of non-DNS data stored on the DNS server. |
| ☐ | SV-69137r1_rule | The DNS server implementation must protect the integrity of transmitted information. |
| ☐ | SV-69141r1_rule | 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). |
| ☐ | SV-69143r1_rule | The DNS server implementation must maintain the integrity of information during preparation for transmission. |
| ☐ | SV-69145r1_rule | The DNS server implementation must maintain the integrity of information during reception. |
| ☐ | SV-69147r1_rule | The DNS server implementation must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. |
| ☐ | SV-69149r1_rule | 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. |
| ☐ | SV-69151r1_rule | 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. |
| ☐ | SV-69153r1_rule | 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. |
| ☐ | SV-69155r1_rule | The DNS implementation must generate audit records for the success and failure of start and stop of the name server service or daemon. |
| ☐ | SV-69157r1_rule | The DNS implementation must generate audit records for the success and failure of all name server events. |
| ☐ | SV-69161r1_rule | The DNS server must implement NIST FIPS-validated cryptography for provisioning digital signatures, generating cryptographic hashes, and protecting unclassified information requiring confidentiality. |
| ☐ | SV-69163r1_rule | The salt value for zones signed using NSEC3 RRs must be changed every time the zone is completely re-signed. |
| ☐ | SV-69165r1_rule | The validity period for the RRSIGs covering a zones DNSKEY RRSet must be no less than two days and no more than one week. |
| ☐ | SV-69167r1_rule | NSEC3 must be used for all internal DNS zones. |
| ☐ | SV-69169r1_rule | 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. |
| ☐ | SV-69171r1_rule | 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. |
| ☐ | SV-69173r1_rule | All authoritative name servers for a zone must be located on different network segments. |
| ☐ | SV-69175r1_rule | All authoritative name servers for a zone must have the same version of zone information. |
| ☐ | SV-69177r1_rule | An authoritative name server must be configured to enable DNSSEC Resource Records. |
| ☐ | SV-69179r1_rule | 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. |
| ☐ | SV-69181r1_rule | 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. |
| ☐ | SV-69183r1_rule | 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. |
| ☐ | SV-69185r1_rule | Primary authoritative name servers must be configured to only receive zone transfer requests from specified secondary name servers. |
| ☐ | SV-69187r1_rule | The DNS implementation must be conformant to the IETF DNS specification. |
| ☐ | SV-69189r1_rule | The DNS implementation must enforce a Discretionary Access Control (DAC) policy that limits propagation of access rights. |
| ☐ | SV-69191r1_rule | The DNS implementation must implement internal/external role separation. |
| ☐ | SV-69193r1_rule | The DNS must utilize valid root name servers in the local root zone file. |
| ☐ | SV-69195r1_rule | The DNS name server software must be at the latest version. |
| ☐ | SV-69197r1_rule | The DNS Name Server software must run with restricted privileges. |
| ☐ | SV-69199r1_rule | The IP address for hidden master authoritative name servers must not appear in the name servers set in the zone database. |
| ☐ | SV-69201r1_rule | The platform on which the name server software is hosted must be configured to respond to DNS traffic only. |
| ☐ | SV-69203r1_rule | The platform on which the name server software is hosted must be configured to send outgoing DNS messages from a random port. |
| ☐ | SV-69205r1_rule | 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. |
| ☐ | SV-69207r1_rule | 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. |
| ☐ | SV-69209r1_rule | A zone file must not include resource records that resolve to a fully qualified domain name residing in another zone. |
| ☐ | SV-69211r1_rule | CNAME records must not point to a zone with lesser security for more than six months. |
| ☐ | SV-69213r1_rule | All authoritative name servers for a zone must be geographically disbursed. |
| ☐ | SV-69215r1_rule | The DNS server implementation must, when a component failure is detected, activate a notification to the system administrator. |
| ☐ | SV-69217r1_rule | The DNS server implementation must strongly bind the identity of the DNS server with the DNS information. |
| ☐ | SV-69219r1_rule | The DNS server implementation must provide the means for authorized individuals to determine the identity of the source of the DNS server-provided information. |
| ☐ | SV-69221r1_rule | 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). |
| ☐ | SV-69223r1_rule | 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. |
| ☐ | SV-69225r1_rule | Digital signature algorithm used for DNSSEC-enabled zones must be FIPS-compatible. |
| ☐ | SV-69471r1_rule | The DNS server implementation must produce audit records containing information to establish when (date and time) the events occurred. |
| ☐ | SV-69473r1_rule | The DNS server implementation must utilize cryptographic mechanisms to prevent unauthorized modification of DNS zone data. |
| ☐ | SV-69475r1_rule | 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. |
STIGQter: STIG Summary: