II - Mission Support Classified
Rules and Groups employed by this XCCDF Profile
-
SRG-APP-000516-DNS-000099
<GroupDescription></GroupDescription>Group -
The permissions assigned to the core BIND 9.x server files must be set to utilize the least privilege possible.
<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-000091
<GroupDescription></GroupDescription>Group -
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.
<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 -
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.
<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 -
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.
<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-000101
<GroupDescription></GroupDescription>Group -
A BIND 9.x server 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 High Severity -
SRG-APP-000516-DNS-000108
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>A hidden master authoritative server is an authoritative DNS server whose IP address does not appear in the name server set f...Rule Medium Severity -
SRG-APP-000516-DNS-000500
<GroupDescription></GroupDescription>Group -
A BIND 9.x implementation operating in a split DNS configuration must be approved by the organizations Authorizing Official.
<VulnDiscussion>BIND 9.x has implemented an option to use "view" statements to allow for split DNS architecture to be configured on a single ...Rule High Severity -
SRG-APP-000516-DNS-000111
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>The private ZSK key must be protected from unauthorized access. This strategy is not feasible in situations in which the DNS...Rule Medium Severity -
SRG-APP-000516-DNS-000111
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>The private ZSK key must be protected from unauthorized access. This strategy is not feasible in situations in which the DNS...Rule Medium Severity -
SRG-APP-000215-DNS-000003
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>A mechanism to detect and prevent unauthorized communication flow must be configured or provided as part of the system design...Rule Medium Severity -
SRG-APP-000516-DNS-000078
<GroupDescription></GroupDescription>Group -
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.
<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-DNS-000084
<GroupDescription></GroupDescription>Group -
A BIND 9.x server 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 -
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.
<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 -
On a BIND 9.x server 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-000088
<GroupDescription></GroupDescription>Group -
On a BIND 9.x server all authoritative name servers for a zone must have the same version of zone information.
<VulnDiscussion>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 Medium Severity -
SRG-APP-000516-DNS-000102
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>All caching name servers must be authoritative for the root zone because, without this starting point, they would have no kno...Rule Low Severity -
SRG-APP-000516-DNS-000102
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>A potential vulnerability of DNS is that an attacker can poison a name servers cache by sending queries that will cause the s...Rule Low Severity -
SRG-APP-000516-DNS-000113
<GroupDescription></GroupDescription>Group -
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.
<VulnDiscussion>If a name server were able to claim authority for a resource record in a domain for which it was not authoritative, this woul...Rule Medium Severity -
SRG-APP-000516-DNS-000114
<GroupDescription></GroupDescription>Group -
On the BIND 9.x server CNAME records must not point to a zone with lesser security for more than six months.
<VulnDiscussion>The use of CNAME records for exercises, tests, or zone-spanning aliases should be temporary (e.g., to facilitate a migration)...Rule Low Severity -
SRG-APP-000516-DNS-000500
<GroupDescription></GroupDescription>Group -
The BIND 9.x server implementation must prohibit the forwarding of queries to servers controlled by organizations outside of the U.S. Government.
<VulnDiscussion>If remote servers to which DoD DNS servers send queries are controlled by entities outside of the U.S. Government the possibi...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.