Domain Name System (DNS) Security Requirements Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-APP-000473
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing t...Rule Medium Severity -
SRG-APP-000474
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing t...Rule Medium Severity -
SRG-APP-000504
<GroupDescription></GroupDescription>Group -
The DNS implementation must generate audit records for the success and failure of start and stop of the name server service or daemon.
<VulnDiscussion>Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is ...Rule Medium Severity -
SRG-APP-000504
<GroupDescription></GroupDescription>Group -
The DNS implementation must generate audit records for the success and failure of all name server events.
<VulnDiscussion>Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is ...Rule Medium Severity -
SRG-APP-000514
<GroupDescription></GroupDescription>Group -
The DNS server must implement NIST FIPS-validated cryptography for provisioning digital signatures, generating cryptographic hashes, and protecting unclassified information requiring confidentiality.
<VulnDiscussion>Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The applicatio...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The salt value for zones signed using NSEC3 RRs must be changed every time the zone is completely re-signed.
<VulnDiscussion>NSEC3 RRs contain other options than just the (hashed) next name and RRType bitmap. There are also 2 values associated with t...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Authoritative name servers for an enterprise may be configured to receive requests from both external and internal clients. ...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
The validity period for the RRSIGs covering a zones DNSKEY RRSet must be no less than two days and no more than one week.
<VulnDiscussion>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
<GroupDescription></GroupDescription>Group -
NSEC3 must be used for all internal DNS zones.
<VulnDiscussion>To ensure that RRs associated with a query are really missing in a zone file and have not been removed in transit, the DNSSEC...Rule Medium Severity -
SRG-APP-000516
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Poorly constructed NS records pose a security risk because they create conditions under which an adversary might be able to p...Rule Medium Severity
Node 2
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.