Skip to content
ATO Pathways
  Log In

II - Mission Support Classified

Rules and Groups employed by this XCCDF Profile

  • SRG-APP-000426

    <GroupDescription></GroupDescription>
    Group
    Show

  • A DNS server implementation must perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources.

    &lt;VulnDiscussion&gt;If data origin authentication and data integrity verification are not performed, the resultant response could be forged, it m...
    Rule Medium Severity
    Show

  • SRG-APP-000427

    <GroupDescription></GroupDescription>
    Group
    Show

  • If the DNS server is using SIG(0), the DNS server implementation must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected transactions.

    &lt;VulnDiscussion&gt;Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that se...
    Rule Medium Severity
    Show

  • SRG-APP-000428

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS server implementation must utilize cryptographic mechanisms to prevent unauthorized modification of DNS zone data.

    &lt;VulnDiscussion&gt;Applications handling data requiring "data at rest" protections must employ cryptographic mechanisms to prevent unauthorized ...
    Rule High Severity
    Show

  • SRG-APP-000429

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS server implementation must utilize cryptographic mechanisms to prevent unauthorized disclosure of non-DNS data stored on the DNS server.

    &lt;VulnDiscussion&gt;Applications handling data requiring "data-at-rest" protections must employ cryptographic mechanisms to prevent unauthorized ...
    Rule High Severity
    Show

  • SRG-APP-000439

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS server implementation must protect the integrity of transmitted information.

    &lt;VulnDiscussion&gt;Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communi...
    Rule High Severity
    Show

  • SRG-APP-000440

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS server implementation 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).

    &lt;VulnDiscussion&gt;Encrypting information for transmission protects information from unauthorized disclosure and modification. Cryptographic mec...
    Rule Medium Severity
    Show

  • SRG-APP-000441

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS server implementation must maintain the integrity of information during preparation for transmission.

    &lt;VulnDiscussion&gt;Information can be either unintentionally or maliciously disclosed or modified during preparation for transmission, including...
    Rule Medium Severity
    Show

  • SRG-APP-000442

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS server implementation must maintain the integrity of information during reception.

    &lt;VulnDiscussion&gt;Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, duri...
    Rule Medium Severity
    Show

  • SRG-APP-000447

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS server implementation must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received.

    &lt;VulnDiscussion&gt;A common vulnerability of applications is unpredictable behavior when invalid inputs are received. This requirement guards ag...
    Rule Medium Severity
    Show

  • SRG-APP-000451

    <GroupDescription></GroupDescription>
    Group
    Show

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

    &lt;VulnDiscussion&gt;Failing to an unsecure condition negatively impacts application security and can lead to system compromise. Failure condition...
    Rule Medium Severity
    Show

  • SRG-APP-000473

    <GroupDescription></GroupDescription>
    Group
    Show

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

    &lt;VulnDiscussion&gt;Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing t...
    Rule Medium Severity
    Show

  • SRG-APP-000474

    <GroupDescription></GroupDescription>
    Group
    Show

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

    &lt;VulnDiscussion&gt;Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing t...
    Rule Medium Severity
    Show

  • SRG-APP-000504

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS implementation must generate audit records for the success and failure of start and stop of the name server service or daemon.

    &lt;VulnDiscussion&gt;Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is ...
    Rule Medium Severity
    Show

  • SRG-APP-000504

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS implementation must generate audit records for the success and failure of all name server events.

    &lt;VulnDiscussion&gt;Auditing and logging are key components of any security architecture. It is essential for security personnel to know what is ...
    Rule Medium Severity
    Show

  • SRG-APP-000514

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DNS server must implement NIST FIPS-validated cryptography for provisioning digital signatures, generating cryptographic hashes, and protecting unclassified information requiring confidentiality.

    &lt;VulnDiscussion&gt;Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The applicatio...
    Rule Medium Severity
    Show

  • SRG-APP-000516

    <GroupDescription></GroupDescription>
    Group
    Show

  • The salt value for zones signed using NSEC3 RRs must be changed every time the zone is completely re-signed.

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

  • SRG-APP-000516

    <GroupDescription></GroupDescription>
    Group
    Show

  • The validity period for the RRSIGs covering a zones 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

    <GroupDescription></GroupDescription>
    Group
    Show

  • NSEC3 must be used for all internal DNS zones.

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

  • SRG-APP-000516

    <GroupDescription></GroupDescription>
    Group
    Show

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

    &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

    <GroupDescription></GroupDescription>
    Group
    Show

  • The two files generated by the dnssec-keygen program must be made accessible only to the server administrator account, or deleted, after they have been copied to the key file in the name server.

    &lt;VulnDiscussion&gt;To enable zone transfer (requests and responses) through authenticated messages, it is necessary to generate a key for every ...
    Rule Medium Severity
    Show

  • SRG-APP-000516

    <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

    <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

    <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 IETF's DNSSEC standard. I...
    Rule Medium Severity
    Show

  • SRG-APP-000516

    <GroupDescription></GroupDescription>
    Group
    Show

  • 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 Medium Severity
    Show

  • SRG-APP-000516

    <GroupDescription></GroupDescription>
    Group
    Show

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

    &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

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