Skip to content
ATO Pathways
  Log In

I - Mission Critical Sensitive

Rules and Groups employed by this XCCDF Profile

  • SRG-APP-000001-DNS-000001

    <GroupDescription></GroupDescription>
    Group
    Show

  • Infoblox systems that perform zone transfers to non-Grid DNS servers must limit the number of concurrent sessions for zone transfers.

    &lt;VulnDiscussion&gt;Limiting the number of concurrent sessions reduces the risk of denial-of-service (DoS) to the DNS implementation. Infoblox...
    Rule Medium Severity
    Show

  • SRG-APP-000001-DNS-000115

    <GroupDescription></GroupDescription>
    Group
    Show

  • The Infoblox system must limit the number of concurrent 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
    Show

  • SRG-APP-000333-DNS-000107

    <GroupDescription></GroupDescription>
    Group
    Show

  • The Infoblox DNS server must not reveal sensitive information to an attacker. This includes HINFO, RP, LOC resource, and sensitive TXT record data.

    &lt;VulnDiscussion&gt;There are several types of resource records (RRs) in the DNS that are meant to convey information to humans and applications ...
    Rule Medium Severity
    Show

  • SRG-APP-000125-DNS-000012

    <GroupDescription></GroupDescription>
    Group
    Show

  • The Infoblox system audit records must be backed up at least every seven days onto a different system or system component than the system or component being audited.

    &lt;VulnDiscussion&gt;Protection of log data includes ensuring that log data is not accidentally lost or deleted. Backing up audit records to a dif...
    Rule Medium Severity
    Show

  • SRG-APP-000218-DNS-000027

    <GroupDescription></GroupDescription>
    Group
    Show

  • All authoritative name servers for a zone must be geographically disbursed.

    &lt;VulnDiscussion&gt;In addition to network-based dispersion, authoritative name servers should be dispersed geographically as well. In other word...
    Rule Medium Severity
    Show

  • SRG-APP-000383-DNS-000047

    <GroupDescription></GroupDescription>
    Group
    Show

  • Recursion must be disabled on Infoblox DNS servers that are configured as 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
    Show

  • SRG-APP-000516-DNS-000078

    <GroupDescription></GroupDescription>
    Group
    Show

  • The validity period for the Resource Record Signatures (RRSIGs) covering a zone's DNSKEY RRSet 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
    Show

  • SRG-APP-000516-DNS-000084

    <GroupDescription></GroupDescription>
    Group
    Show

  • NSEC3 must be used for all DNSSEC signed zones.

    &lt;VulnDiscussion&gt;To ensure that resource records (RRs) associated with a query are really missing in a zone file and have not been removed in ...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000085

    <GroupDescription></GroupDescription>
    Group
    Show

  • The Infoblox DNS server must be configured so that each name server (NS) record in a zone file points to an active name server authoritative for the domain specified in that record.

    &lt;VulnDiscussion&gt;Poorly constructed NS records pose a security risk because they create conditions under which an adversary might be able to p...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000087

    <GroupDescription></GroupDescription>
    Group
    Show

  • All authoritative name servers for a zone must be located on different network segments.

    &lt;VulnDiscussion&gt;Most enterprises have an authoritative primary server and a host of authoritative secondary name servers. It is essential tha...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000088

    <GroupDescription></GroupDescription>
    Group
    Show

  • All authoritative name servers for a zone must have the same version of zone information.

    &lt;VulnDiscussion&gt;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
    Show

  • SRG-APP-000516-DNS-000089

    <GroupDescription></GroupDescription>
    Group
    Show

  • An authoritative name server must be configured to enable DNSSEC resource records.

    &lt;VulnDiscussion&gt;The specification for a digital signature mechanism in the context of the DNS infrastructure is in the Internet Engineering T...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000090

    <GroupDescription></GroupDescription>
    Group
    Show

  • The digital signature algorithm used for DNSSEC-enabled zones must be FIPS compatible.

    &lt;VulnDiscussion&gt;The choice of digital signature algorithm will be based on recommended algorithms in well-known standards. NIST's Digital Sig...
    Rule High Severity
    Show

  • SRG-APP-000516-DNS-000091

    <GroupDescription></GroupDescription>
    Group
    Show

  • 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.

    &lt;VulnDiscussion&gt;Authoritative name servers for an enterprise may be configured to receive requests from both external and internal clients. ...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000092

    <GroupDescription></GroupDescription>
    Group
    Show

  • 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.

    &lt;VulnDiscussion&gt;Instead of having the same set of authoritative name servers serve different types of clients, an enterprise could have two d...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000093

    <GroupDescription></GroupDescription>
    Group
    Show

  • 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.

    &lt;VulnDiscussion&gt;Instead of having the same set of authoritative name servers serve different types of clients, an enterprise could have two d...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000095

    <GroupDescription></GroupDescription>
    Group
    Show

  • Primary authoritative name servers must be configured to only receive zone transfer requests from specified secondary name servers.

    &lt;VulnDiscussion&gt;Authoritative name servers (especially primary name servers) should be configured with an allow-transfer access control sub-s...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000099

    <GroupDescription></GroupDescription>
    Group
    Show

  • The Infoblox system must use a security policy that limits the propagation of access rights.

    &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
    Show

  • SRG-APP-000516-DNS-000101

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS implementation must implement internal/external role separation.

    &lt;VulnDiscussion&gt;DNS servers with an internal role only process name/address resolution requests from within the organization (i.e., internal ...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000102

    <GroupDescription></GroupDescription>
    Group
    Show

  • The Infoblox DNS server must use current and valid root name servers.

    &lt;VulnDiscussion&gt;All caching name servers must be authoritative for the root zone because, without this starting point, they would have no kno...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000103

    <GroupDescription></GroupDescription>
    Group
    Show

  • The Infoblox NIOS version must be at the appropriate version.

    &lt;VulnDiscussion&gt;Each newer version of the name server software, especially the BIND software, generally is devoid of vulnerabilities found in...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000108

    <GroupDescription></GroupDescription>
    Group
    Show

  • The IP address for hidden master authoritative name servers must not appear in the name servers set in the zone database.

    &lt;VulnDiscussion&gt;A hidden master authoritative server is an authoritative DNS server in which the IP address does not appear in the name serve...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000109

    <GroupDescription></GroupDescription>
    Group
    Show

  • The Infoblox system must be configured to respond to DNS traffic only.

    &lt;VulnDiscussion&gt;OS configuration practices as issued by the US Computer Emergency Response Team (US CERT) and the National Institute of Stand...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000110

    <GroupDescription></GroupDescription>
    Group
    Show

  • The Infoblox DNS server must send outgoing DNS messages from a random port.

    &lt;VulnDiscussion&gt;OS configuration practices as issued by the US Computer Emergency Response Team (US CERT) and the National Institute of Stand...
    Rule Medium Severity
    Show

  • SRG-APP-000516-DNS-000112

    <GroupDescription></GroupDescription>
    Group
    Show

  • The private keys corresponding to both the Zone Signing Key (ZSK) and the Key Signing Key (KSK) must not be kept on the 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 High Severity
    Show

Node 2

siemur/test-space

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