Skip to content

BIND 9.x Security Technical Implementation Guide

Rules, Groups, and Values defined within the XCCDF Benchmark

  • SRG-APP-000125-DNS-000012

    <GroupDescription></GroupDescription>
    Group
  • The BIND 9.x server implementation must maintain at least 3 file versions of the local log file.

    &lt;VulnDiscussion&gt;DNS software administrators require DNS transaction logs for a wide variety of reasons including troubleshooting, intrusion d...
    Rule Low Severity
  • SRG-APP-000001-DNS-000001

    <GroupDescription></GroupDescription>
    Group
  • The BIND 9.x secondary name server must limit the number of zones requested from a single master name server.

    &lt;VulnDiscussion&gt;Limiting the number of concurrent sessions reduces the risk of Denial of Service (DoS) to the DNS implementation. Name serve...
    Rule Medium Severity
  • SRG-APP-000001-DNS-000001

    <GroupDescription></GroupDescription>
    Group
  • The BIND 9.x secondary name server must limit the total number of zones the name server can request at any one time.

    &lt;VulnDiscussion&gt;Limiting the number of concurrent sessions reduces the risk of Denial of Service (DoS) to the DNS implementation. Name serve...
    Rule Medium Severity
  • SRG-APP-000001-DNS-000115

    <GroupDescription></GroupDescription>
    Group
  • The BIND 9.x server implementation must limit the number of concurrent session client connections to the number of allowed dynamic update clients.

    &lt;VulnDiscussion&gt;Limiting the number of concurrent sessions reduces the risk of Denial of Service (DoS) to the DNS implementation. Name serv...
    Rule Medium Severity
  • SRG-APP-000142-DNS-000014

    <GroupDescription></GroupDescription>
    Group
  • The BIND 9.x server implementation must be configured to use only approved ports and protocols.

    &lt;VulnDiscussion&gt;In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e....
    Rule Medium Severity
  • SRG-APP-000247-DNS-000036

    <GroupDescription></GroupDescription>
    Group
  • 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.

    &lt;VulnDiscussion&gt;A DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot ...
    Rule Medium Severity
  • SRG-APP-000246-DNS-000035

    <GroupDescription></GroupDescription>
    Group
  • A BIND 9.x server implementation must prohibit recursion on authoritative name servers.

    &lt;VulnDiscussion&gt;A potential vulnerability of DNS is that an attacker can poison a name server's cache by sending queries that will cause the ...
    Rule Medium Severity
  • SRG-APP-000516-DNS-000088

    <GroupDescription></GroupDescription>
    Group
  • The master servers in a BIND 9.x implementation must notify authorized secondary name servers when zone files are updated.

    &lt;VulnDiscussion&gt;It is important to maintain the integrity of a zone file. The serial number of the SOA record is used to indicate to secondar...
    Rule Low Severity
  • SRG-APP-000516-DNS-000088

    <GroupDescription></GroupDescription>
    Group
  • The secondary name servers in a BIND 9.x implementation must be configured to initiate zone update notifications to other authoritative zone name servers.

    &lt;VulnDiscussion&gt;It is important to maintain the integrity of a zone file. The serial number of the SOA record is used to indicate to secondar...
    Rule Low Severity
  • SRG-APP-000516-DNS-000110

    <GroupDescription></GroupDescription>
    Group
  • The BIND 9.X implementation must not utilize a TSIG or DNSSEC key for more than one year.

    &lt;VulnDiscussion&gt;Cryptographic keys are the backbone of securing DNS information over the wire, maintaining DNS data integrity, and the provid...
    Rule Medium Severity
  • SRG-APP-000514-DNS-000075

    <GroupDescription></GroupDescription>
    Group
  • A BIND 9.x server must implement NIST FIPS-validated cryptography for provisioning digital signatures and generating cryptographic hashes.

    &lt;VulnDiscussion&gt;The use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The applic...
    Rule High Severity
  • SRG-APP-000231-DNS-000033

    <GroupDescription></GroupDescription>
    Group
  • The DNSSEC keys used with the BIND 9.x implementation must be owned by a privileged account.

    &lt;VulnDiscussion&gt;Information at rest refers to the state of information when it is located on a secondary storage device within an organizatio...
    Rule Medium Severity
  • SRG-APP-000231-DNS-000033

    <GroupDescription></GroupDescription>
    Group
  • The DNSSEC keys used with the BIND 9.x implementation must be group owned by a privileged account.

    &lt;VulnDiscussion&gt;Information at rest refers to the state of information when it is located on a secondary storage device within an organizatio...
    Rule Medium Severity
  • SRG-APP-000231-DNS-000033

    <GroupDescription></GroupDescription>
    Group
  • 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.

    &lt;VulnDiscussion&gt;Information at rest refers to the state of information when it is located on a secondary storage device within an organizatio...
    Rule Medium Severity
  • SRG-APP-000176-DNS-000094

    <GroupDescription></GroupDescription>
    Group
  • 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.

    &lt;VulnDiscussion&gt;The private key in the ZSK key pair must be protected from unauthorized access. If possible, the private key should be stored...
    Rule High Severity
  • SRG-APP-000516-DNS-000112

    <GroupDescription></GroupDescription>
    Group
  • 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.

    &lt;VulnDiscussion&gt;The private keys in the KSK and ZSK key pairs must be protected from unauthorized access. If possible, the private keys shoul...
    Rule Medium Severity
  • SRG-APP-000516-DNS-000086

    <GroupDescription></GroupDescription>
    Group
  • 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.

    &lt;VulnDiscussion&gt;To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every ...
    Rule Medium Severity
  • SRG-APP-000516-DNS-000086

    <GroupDescription></GroupDescription>
    Group
  • 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.

    &lt;VulnDiscussion&gt;To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every ...
    Rule Medium Severity
  • SRG-APP-000516-DNS-000086

    <GroupDescription></GroupDescription>
    Group
  • 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.

    &lt;VulnDiscussion&gt;To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every ...
    Rule Medium Severity
  • SRG-APP-000176-DNS-000096

    <GroupDescription></GroupDescription>
    Group
  • The BIND 9.x server signature generation using the KSK must be done off-line, using the KSK-private key stored off-line.

    &lt;VulnDiscussion&gt;The private key in the KSK key pair must be protected from unauthorized access. The private key should be stored off-line (wi...
    Rule High Severity
  • SRG-APP-000213-DNS-000024

    <GroupDescription></GroupDescription>
    Group
  • 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.

    &lt;VulnDiscussion&gt;DNSSEC is required for securing the DNS query/response transaction by providing data origin authentication and data integrity...
    Rule High Severity
  • SRG-APP-000214-DNS-000025

    <GroupDescription></GroupDescription>
    Group
  • A BIND 9.x server implementation must provide the means to indicate the security status of child zones.

    &lt;VulnDiscussion&gt;If name server replies are invalid or cannot be validated, many networking functions and communication would be adversely aff...
    Rule Medium Severity
  • SRG-APP-000214-DNS-000079

    <GroupDescription></GroupDescription>
    Group
  • 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.

    &lt;VulnDiscussion&gt;The best way for a zone administrator to minimize the impact of a key compromise is by limiting the validity period of RRSIGs...
    Rule Medium Severity
  • SRG-APP-000516-DNS-000099

    <GroupDescription></GroupDescription>
    Group
  • The core BIND 9.x server files must be owned by the root or BIND 9.x process account.

    &lt;VulnDiscussion&gt;Discretionary Access Control (DAC) is based on the premise that individual users are "owners" of objects and therefore have d...
    Rule Medium Severity
  • SRG-APP-000516-DNS-000099

    <GroupDescription></GroupDescription>
    Group
  • The core BIND 9.x server files must be group owned by a group designated for DNS administration only.

    &lt;VulnDiscussion&gt;Discretionary Access Control (DAC) is based on the premise that individual users are "owners" of objects and therefore have d...
    Rule Medium Severity

The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.

Capacity
Modules