II - Mission Support Sensitive
Rules and Groups employed by this XCCDF Profile
-
SRG-APP-000169-AU-002520
Group -
Splunk Enterprise must enforce password complexity for the account of last resort 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-000174-AU-002570
Group -
Splunk Enterprise must enforce a 60-day maximum password lifetime restriction for the account of last resort.
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 prohibit password reuse for a minimum of five generations for the account of last resort.
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 to...Rule Low Severity -
SRG-APP-000068-AU-000035
Group -
Splunk Enterprise must display the Standard Mandatory DOD Notice and Consent Banner and accept user acknowledgement before granting access to the application.
Display of the DOD-approved use notification before granting access to the application ensures privacy and security notification verbiage used is consistent with applicable federal laws, Executive ...Rule Low 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-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-000141-AU-000090
Group -
When Splunk Enterprise is distributed over multiple servers, each server must be configured to disable non-essential capabilities.
Applications are capable of providing a wide variety of functions and services. Some of the functions and services may not be necessary to support the configuration. This becomes more of an issue i...Rule Medium Severity -
SRG-APP-000118-AU-000100
Group -
Splunk Enterprise installation directories must be secured.
If audit data were to become compromised, competent forensic analysis and discovery of the true source of potentially malicious system activity would be difficult if not impossible to achieve. In a...Rule Medium Severity -
SRG-APP-000516-AU-000340
Group -
Splunk Enterprise forwarders must be configured with Indexer Acknowledgement enabled.
To prevent the loss of data during transmission, a handshake acknowledgement between the sender and the recipient may need configured.Rule Low Severity -
SRG-APP-000389-AU-000180
Group -
Splunk Enterprise idle session timeout must be set to not exceed 15 minutes.
Without reauthentication, users may access resources or perform tasks for which they do not have authorization. When applications provide the capability to change security roles or escalate the fu...Rule Low 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.