I - Mission Critical Public
Rules and Groups employed by this XCCDF Profile
-
SRG-APP-000516-DNS-000088
<GroupDescription></GroupDescription>Group -
All authoritative name servers for a zone must have the same version of zone information.
<VulnDiscussion>The only protection approach for content control of DNS zone file is the use of a zone file integrity checker. The effectiven...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 the Internet Engineering T...Rule Medium Severity -
SRG-APP-000516-DNS-000090
<GroupDescription></GroupDescription>Group -
The 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 resource records (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-000095
<GroupDescription></GroupDescription>Group -
Primary authoritative name servers must be configured to only receive zone transfer requests from specified secondary name servers.
<VulnDiscussion>Authoritative name servers (especially primary name servers) should be configured with an allow-transfer access control sub-s...Rule Medium Severity -
SRG-APP-000516-DNS-000099
<GroupDescription></GroupDescription>Group -
The Infoblox system must use a security policy that limits the 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 -
SRG-APP-000516-DNS-000101
<GroupDescription></GroupDescription>Group -
The DNS implementation must implement internal/external role separation.
<VulnDiscussion>DNS servers with an internal role only process name/address resolution requests from within the organization (i.e., internal ...Rule Medium Severity -
SRG-APP-000516-DNS-000102
<GroupDescription></GroupDescription>Group -
The Infoblox DNS server must use current and valid root name servers.
<VulnDiscussion>All caching name servers must be authoritative for the root zone because, without this starting point, they would have no kno...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.