I - Mission Critical Sensitive
Rules and Groups employed by this XCCDF Profile
-
SRG-APP-000395-DNS-000050
<GroupDescription></GroupDescription>Group -
The DNS server implementation must authenticate another DNS server before establishing a remote and/or network connection using bidirectional authentication that is cryptographically based.
<VulnDiscussion>Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. B...Rule Medium Severity -
SRG-APP-000420-DNS-000053
<GroupDescription></GroupDescription>Group -
A DNS server implementation must provide data origin artifacts for internal name/address resolution queries.
<VulnDiscussion>The major threat associated with DNS forged responses or failures is the integrity of the DNS data returned in the response. ...Rule Medium Severity -
SRG-APP-000421-DNS-000054
<GroupDescription></GroupDescription>Group -
A DNS server implementation must provide data integrity protection artifacts for internal name/address resolution queries.
<VulnDiscussion>The major threat associated with DNS forged responses or failures is the integrity of the DNS data returned in the response. ...Rule Medium Severity -
SRG-APP-000422-DNS-000055
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>The major threat associated with DNS forged responses or failures is the integrity of the DNS data returned in the response. ...Rule Medium Severity -
SRG-APP-000423-DNS-000056
<GroupDescription></GroupDescription>Group -
A DNS server implementation must request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources.
<VulnDiscussion>If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it m...Rule Medium Severity -
SRG-APP-000424-DNS-000057
<GroupDescription></GroupDescription>Group -
A DNS server implementation must request data integrity verification on the name/address resolution responses the system receives from authoritative sources.
<VulnDiscussion>If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it m...Rule Medium Severity -
SRG-APP-000425-DNS-000058
<GroupDescription></GroupDescription>Group -
A DNS server implementation must perform data integrity verification on the name/address resolution responses the system receives from authoritative sources.
<VulnDiscussion>If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it m...Rule Medium Severity -
SRG-APP-000426-DNS-000059
<GroupDescription></GroupDescription>Group -
A DNS server implementation must perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.
<VulnDiscussion>If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it m...Rule Medium Severity -
SRG-APP-000439-DNS-000063
<GroupDescription></GroupDescription>Group -
The Infoblox system must be configured to must protect the integrity of transmitted information.
<VulnDiscussion>Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communi...Rule Medium Severity -
SRG-APP-000440-DNS-000065
<GroupDescription></GroupDescription>Group -
The Infoblox system 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).
<VulnDiscussion>Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mec...Rule Medium Severity -
SRG-APP-000441-DNS-000066
<GroupDescription></GroupDescription>Group -
The DNS server implementation must maintain the integrity of information during preparation for transmission.
<VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including...Rule Medium Severity -
SRG-APP-000442-DNS-000067
<GroupDescription></GroupDescription>Group -
The DNS server implementation must maintain the integrity of information during reception.
<VulnDiscussion>Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, duri...Rule Medium Severity -
SRG-APP-000451-DNS-000069
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Failing to an unsecure condition negatively impacts application security and can lead to system compromise. Failure condition...Rule Medium Severity -
SRG-APP-000474-DNS-000073
<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-000514-DNS-000075
<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 High Severity -
SRG-APP-000516-DNS-000078
<GroupDescription></GroupDescription>Group -
The Zone Signing Key (ZSK) rollover interval must be configured to less than two months.
<VulnDiscussion>An attacker that has compromised a ZSK can use that key only during the KSK's signature validity interval. An attacker that h...Rule Medium Severity -
SRG-APP-000516-DNS-000084
<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-DNS-000085
<GroupDescription></GroupDescription>Group -
The Infoblox system 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 -
SRG-APP-000516-DNS-000087
<GroupDescription></GroupDescription>Group -
All authoritative name servers for a zone must be located on different network segments.
<VulnDiscussion>Most enterprises have an authoritative primary server and a host of authoritative secondary name servers. It is essential tha...Rule Medium Severity -
SRG-APP-000516-DNS-000089
<GroupDescription></GroupDescription>Group -
An authoritative name server must be configured to enable DNSSEC Resource Records.
<VulnDiscussion>The specification for a digital signature mechanism in the context of the DNS infrastructure is in IETF's DNSSEC standard. In...Rule Medium Severity -
SRG-APP-000516-DNS-000090
<GroupDescription></GroupDescription>Group -
Digital signature algorithm used for DNSSEC-enabled zones must be FIPS-compatible.
<VulnDiscussion>The choice of digital signature algorithm will be based on recommended algorithms in well-known standards. NIST's Digital Sig...Rule High Severity -
SRG-APP-000516-DNS-000091
<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-DNS-000092
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Instead of having the same set of authoritative name servers serve different types of clients, an enterprise could have two d...Rule Medium Severity -
SRG-APP-000516-DNS-000093
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>Instead of having the same set of authoritative name servers serve different types of clients, an enterprise could have two d...Rule Medium Severity -
SRG-APP-000516-DNS-000099
<GroupDescription></GroupDescription>Group -
The DNS implementation must enforce a Discretionary Access Control (DAC) policy that limits propagation of access rights.
<VulnDiscussion>Discretionary Access Control (DAC) is based on the premise that individual users are "owners" of objects and therefore have d...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.