Skip to content

I - Mission Critical Classified

Rules and Groups employed by this XCCDF Profile

  • SRG-APP-000167-AU-002500

    Group
  • Splunk Enterprise must be configured to enforce password complexity by requiring that at least one lowercase character be used.

    Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resistin...
    Rule Low Severity
  • SRG-APP-000168-AU-002510

    Group
  • Splunk Enterprise must be configured to enforce password complexity by requiring that at least one numeric character be used.

    Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resistin...
    Rule Low Severity
  • SRG-APP-000164-AU-002480

    Group
  • Splunk Enterprise must be configured to enforce a minimum 15-character password length.

    The shorter the password, the lower the number of possible combinations that need to be tested before the password is compromised. Password complexity, or strength, is a measure of the effectivene...
    Rule Low Severity
  • SRG-APP-000169-AU-002520

    Group
  • Splunk Enterprise must be configured to enforce password complexity by requiring that at least one special character be used.

    Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resistin...
    Rule Low Severity
  • SRG-APP-000172-AU-002550

    Group
  • Splunk Enterprise must be installed in FIPS mode to implement NIST FIPS-approved cryptography for all cryptographic functions.

    FIPS 140-2 precludes the use of unvalidated cryptography for the cryptographic protection of sensitive or valuable data within Federal systems. Unvalidated cryptography is viewed by NIST as providi...
    Rule High Severity
  • SRG-APP-000174-AU-002570

    Group
  • Splunk Enterprise must be configured to enforce a 60-day maximum password lifetime restriction.

    Any password, no matter how complex, can eventually be cracked. Therefore, passwords need to be changed at specific intervals. If the application does not limit the lifetime of passwords and force ...
    Rule Low Severity
  • SRG-APP-000165-AU-002580

    Group
  • Splunk Enterprise must be configured to prohibit password reuse for a minimum of five generations.

    Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. To meet password policy requirements, passwords need t...
    Rule Low Severity
  • SRG-APP-000610-AU-000050

    Group
  • Splunk Enterprise must use TLS 1.2 and SHA-2 or higher cryptographic algorithms.

    Without cryptographic integrity protections, information can be altered by unauthorized users without detection. To protect the integrity of the authenticator and authentication mechanism used for...
    Rule High Severity
  • SRG-APP-000427-AU-000040

    Group
  • Splunk Enterprise must only allow the use of DOD-approved certificate authorities for cryptographic functions.

    Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD systems or by organizations with insufficient secur...
    Rule Medium Severity
  • SRG-APP-000439-AU-004310

    Group
  • Splunk Enterprise must be configured to protect the confidentiality and integrity of transmitted information.

    Without protection of the transmitted information, confidentiality and integrity may be compromised since unprotected communications can be intercepted and either read or altered. This requiremen...
    Rule High Severity
  • SRG-APP-000391-AU-002290

    Group
  • Splunk Enterprise must accept the DOD CAC or other PKI credential for identity management and personal authentication.

    The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DOD has mandated the use of the CAC to support identity management and personal authentication f...
    Rule High Severity

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