| Checked | Name | Title |
|---|
| ☐ | SV-207532r612253_rule | A BIND 9.x server implementation must be running in a chroot(ed) directory structure. |
| ☐ | SV-207533r612253_rule | A BIND 9.x server implementation must be operating on a Current-Stable version as defined by ISC. |
| ☐ | SV-207534r612253_rule | The platform on which the name server software is hosted must only run processes and services needed to support the BIND 9.x implementation. |
| ☐ | SV-207535r612253_rule | The BIND 9.x server software must run with restricted privileges. |
| ☐ | SV-207536r612253_rule | The host running a BIND 9.X implementation must implement a set of firewall rules that restrict traffic on the DNS interface. |
| ☐ | SV-207537r612253_rule | The host running a BIND 9.x implementation must use a dedicated management interface in order to separate management traffic from DNS specific traffic. |
| ☐ | SV-207538r612253_rule | The host running a BIND 9.x implementation must use an interface that is configured to process only DNS traffic. |
| ☐ | SV-207539r612253_rule | A BIND 9.x server implementation must be configured to allow DNS administrators to audit all DNS server components, based on selectable event criteria, and produce audit records within all DNS server components that contain information for failed security verification tests, information to establish the outcome and source of the events, any information necessary to determine cause of failure, and any information necessary to return to operations with least disruption to mission processes. |
| ☐ | SV-207540r612253_rule | The BIND 9.x server implementation must not be configured with a channel to send audit records to null. |
| ☐ | SV-207541r612253_rule | The BIND 9.x server logging configuration must be configured to generate audit records for all DoD-defined auditable events to a local file by enabling triggers for all events with a severity of info, notice, warning, error, and critical for all DNS components. |
| ☐ | SV-207542r612253_rule | In the event of an error when validating the binding of other DNS servers identity to the BIND 9.x information, when anomalies in the operation of the signed zone transfers are discovered, for the success and failure of start and stop of the name server service or daemon, and for the success and failure of all name server events, a BIND 9.x server implementation must generate a log entry. |
| ☐ | SV-207543r612253_rule | The print-severity variable for the configuration of BIND 9.x server logs must be configured to produce audit records containing information to establish what type of events occurred. |
| ☐ | SV-207544r612253_rule | The print-time variable for the configuration of BIND 9.x server logs must be configured to establish when (date and time) the events occurred. |
| ☐ | SV-207545r612253_rule | The print-category variable for the configuration of BIND 9.x server logs must be configured to record information indicating which process generated the events. |
| ☐ | SV-207546r612253_rule | The BIND 9.x server implementation must be configured with a channel to send audit records to a remote syslog. |
| ☐ | SV-207547r612253_rule | The BIND 9.x server implementation must be configured with a channel to send audit records to a local file. |
| ☐ | SV-207548r612253_rule | The BIND 9.x server implementation must maintain at least 3 file versions of the local log file. |
| ☐ | SV-207549r612253_rule | The BIND 9.x secondary name server must limit the number of zones requested from a single master name server. |
| ☐ | SV-207550r612253_rule | The BIND 9.x secondary name server must limit the total number of zones the name server can request at any one time. |
| ☐ | SV-207551r612253_rule | The BIND 9.x server implementation must limit the number of concurrent session client connections to the number of allowed dynamic update clients. |
| ☐ | SV-207552r612253_rule | The BIND 9.x server implementation must be configured to use only approved ports and protocols. |
| ☐ | SV-207553r612253_rule | A BIND 9.x 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-207554r612253_rule | A BIND 9.x server implementation must prohibit recursion on authoritative name servers. |
| ☐ | SV-207555r612253_rule | The master servers in a BIND 9.x implementation must notify authorized secondary name servers when zone files are updated. |
| ☐ | SV-207556r612253_rule | The secondary name servers in a BIND 9.x implementation must be configured to initiate zone update notifications to other authoritative zone name servers. |
| ☐ | SV-207557r612253_rule | On the BIND 9.x server the platform on which the name server software is hosted must be configured to send outgoing DNS messages from a random port. |
| ☐ | SV-207558r612253_rule | A BIND 9.x caching name server must implement DNSSEC validation to check all DNS queries for invalid input. |
| ☐ | SV-207559r612253_rule | A BIND 9.x master name server must limit the number of concurrent zone transfers between authorized secondary name servers. |
| ☐ | SV-207560r612253_rule | A BIND 9.x implementation configured as a caching name server must restrict recursive queries to only the IP addresses and IP address ranges of known supported clients. |
| ☐ | SV-207561r612253_rule | The BIND 9.x server implementation must uniquely identify and authenticate the other DNS server before responding to a server-to-server transaction, zone transfer and/or dynamic update request using cryptographically based bidirectional authentication to protect the integrity of the information in transit. |
| ☐ | SV-207562r612253_rule | The BIND 9.x server implementation must utilize separate TSIG key-pairs when securing server-to-server transactions. |
| ☐ | SV-207563r612253_rule | The TSIG keys used with the BIND 9.x implementation must be owned by a privileged account. |
| ☐ | SV-207564r612253_rule | The TSIG keys used with the BIND 9.x implementation must be group owned by a privileged account. |
| ☐ | SV-207565r612253_rule | The read and write access to a TSIG key file used by a BIND 9.x server must be restricted to only the account that runs the name server software. |
| ☐ | SV-207566r612253_rule | The BIND 9.X implementation must not utilize a TSIG or DNSSEC key for more than one year. |
| ☐ | SV-207567r612253_rule | A BIND 9.x server must implement NIST FIPS-validated cryptography for provisioning digital signatures and generating cryptographic hashes. |
| ☐ | SV-207568r612253_rule | The DNSSEC keys used with the BIND 9.x implementation must be owned by a privileged account. |
| ☐ | SV-207569r612253_rule | The DNSSEC keys used with the BIND 9.x implementation must be group owned by a privileged account. |
| ☐ | SV-207570r612253_rule | Permissions assigned to the DNSSEC keys used with the BIND 9.x implementation must enforce read-only access to the key owner and deny access to all other users. |
| ☐ | SV-207571r612253_rule | The BIND 9.x server private key corresponding to the ZSK pair must be the only DNSSEC key kept on a name server that supports dynamic updates. |
| ☐ | SV-207572r612253_rule | On the BIND 9.x server the private keys corresponding to both the ZSK and the KSK must not be kept on the BIND 9.x DNSSEC-aware primary authoritative name server when the name server does not support dynamic updates. |
| ☐ | SV-207573r612253_rule | The two files generated by the BIND 9.x server dnssec-keygen program must be owned by the root account, or deleted, after they have been copied to the key file in the name server. |
| ☐ | SV-207574r612253_rule | The two files generated by the BIND 9.x server dnssec-keygen program must be group owned by the server administrator account, or deleted, after they have been copied to the key file in the name server. |
| ☐ | SV-207575r612253_rule | Permissions assigned to the dnssec-keygen keys used with the BIND 9.x implementation must enforce read-only access to the key owner and deny access to all other users. |
| ☐ | SV-207576r612253_rule | The BIND 9.x server signature generation using the KSK must be done off-line, using the KSK-private key stored off-line. |
| ☐ | SV-207577r612253_rule | 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 t must perform integrity verification and data origin verification for all DNS information. |
| ☐ | SV-207578r612253_rule | A BIND 9.x server implementation must provide the means to indicate the security status of child zones. |
| ☐ | SV-207579r612253_rule | The BIND 9.x server validity period for the RRSIGs covering the DS RR for zones delegated children must be no less than two days and no more than one week. |
| ☐ | SV-207580r612253_rule | The core BIND 9.x server files must be owned by the root or BIND 9.x process account. |
| ☐ | SV-207581r612253_rule | The core BIND 9.x server files must be group owned by a group designated for DNS administration only. |
| ☐ | SV-207582r612253_rule | The permissions assigned to the core BIND 9.x server files must be set to utilize the least privilege possible. |
| ☐ | SV-207583r612253_rule | On a BIND 9.x server 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-207584r612253_rule | On a BIND 9.x server 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-207585r612253_rule | On a BIND 9.x server 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-207586r612253_rule | A BIND 9.x server implementation must implement internal/external role separation. |
| ☐ | SV-207587r612253_rule | On the BIND 9.x server the IP address for hidden master authoritative name servers must not appear in the name servers set in the zone database. |
| ☐ | SV-207588r612253_rule | A BIND 9.x implementation operating in a split DNS configuration must be approved by the organizations Authorizing Official. |
| ☐ | SV-207589r612253_rule | On the BIND 9.x server the private key corresponding to the ZSK, stored on name servers accepting dynamic updates, must be owned by root. |
| ☐ | SV-207590r612253_rule | On the BIND 9.x server the private key corresponding to the ZSK, stored on name servers accepting dynamic updates, must be group owned by root. |
| ☐ | SV-207591r612253_rule | A BIND 9.x server implementation must enforce approved authorizations for controlling the flow of information between authoritative name servers and specified secondary name servers based on DNSSEC policies. |
| ☐ | SV-207592r612253_rule | A BIND 9.x server validity period for the RRSIGs covering a zones DNSKEY RRSet must be no less than two days and no more than one week. |
| ☐ | SV-207593r612253_rule | A BIND 9.x server NSEC3 must be used for all internal DNS zones. |
| ☐ | SV-207594r612253_rule | Every NS record in a zone file on a BIND 9.x server must point to an active name server and that name server must be authoritative for the domain specified in that record. |
| ☐ | SV-207595r612253_rule | On a BIND 9.x server all authoritative name servers for a zone must be located on different network segments. |
| ☐ | SV-207596r612253_rule | On a BIND 9.x server all authoritative name servers for a zone must have the same version of zone information. |
| ☐ | SV-207597r612253_rule | On a BIND 9.x server all root name servers listed in the local root zone file hosted on a BIND 9.x authoritative name server must be valid for that zone. |
| ☐ | SV-207598r612253_rule | On a BIND 9.x server all root name servers listed in the local root zone file hosted on a BIND 9.x authoritative name server must be empty or removed. |
| ☐ | SV-207599r612253_rule | On the BIND 9.x server a zone file must not include resource records that resolve to a fully qualified domain name residing in another zone. |
| ☐ | SV-207600r612253_rule | On the BIND 9.x server CNAME records must not point to a zone with lesser security for more than six months. |
| ☐ | SV-207601r612253_rule | The BIND 9.x server implementation must prohibit the forwarding of queries to servers controlled by organizations outside of the U.S. Government. |
STIGQter: STIG Summary: