| Checked | Name | Title |
|---|
| ☐ | SV-221600r508660_rule | Splunk Enterprise must be installed with FIPS mode enabled, to implement NIST FIPS 140-2 approved ciphers for all cryptographic functions. |
| ☐ | SV-221601r663926_rule | Splunk Enterprise must use organization level authentication to uniquely identify and authenticate users. |
| ☐ | SV-221602r508660_rule | Splunk Enterprise must have all local user accounts removed after implementing organizational level user management system, except for one emergency account of last resort. |
| ☐ | SV-221605r663928_rule | Splunk Enterprise must use an SSO proxy service, F5 device, or SAML implementation to accept the DoD CAC or other smart card credential for identity management, personal authentication, and multifactor authentication. |
| ☐ | SV-221607r508660_rule | Splunk Enterprise must use HTTPS/SSL for access to the user interface. |
| ☐ | SV-221608r508660_rule | Splunk Enterprise must use SSL to protect the confidentiality and integrity of transmitted information. |
| ☐ | SV-221609r663930_rule | Splunk Enterprise must use LDAPS for the LDAP connection. |
| ☐ | SV-221612r508660_rule | Splunk Enterprise must be configured to back up the log records repository at least every seven days onto a different system or system component other than the system or component being audited. |
| ☐ | SV-221613r508660_rule | Splunk Enterprise must be configured to protect the log data stored in the indexes from alteration. |
| ☐ | SV-221614r508660_rule | Splunk Enterprise must use TCP for data transmission. |
| ☐ | SV-221621r508660_rule | Splunk Enterprise must be configured to aggregate log records from organization-defined devices and hosts within its scope of coverage. |
| ☐ | SV-221623r538427_rule | Splunk Enterprise must allow only the Information System Security Manager (ISSM) (or individuals or roles appointed by the ISSM) to be assigned to the Power User role. |
| ☐ | SV-221625r508660_rule | Splunk Enterprise must be configured to send an immediate alert to the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) when allocated log record storage volume reaches 75 percent of the repository maximum log record storage capacity. |
| ☐ | SV-221626r508660_rule | Splunk Enterprise must notify the System Administrator (SA) and Information System Security Officer (ISSO) (at a minimum) of all audit failure events, such as loss of communications with hosts and devices, or if log records are no longer being received. |
| ☐ | SV-221627r508660_rule | Splunk Enterprise must notify the System Administrator (SA) or Information System Security Officer (ISSO) if communication with the host and devices within its scope of coverage is lost. |
| ☐ | SV-221628r508660_rule | Splunk Enterprise must be configured to notify the System Administrator (SA) and Information System Security Officer (ISSO), at a minimum, when an attack is detected on multiple devices and hosts within its scope of coverage. |
| ☐ | SV-221629r508660_rule | Splunk Enterprise must enforce password complexity for the account of last resort by requiring that at least one upper-case character be used. |
| ☐ | SV-221630r508660_rule | Splunk Enterprise must enforce password complexity for the account of last resort by requiring that at least one lower-case character be used. |
| ☐ | SV-221631r508660_rule | Splunk Enterprise must enforce password complexity for the account of last resort by requiring that at least one numeric character be used. |
| ☐ | SV-221632r508660_rule | Splunk Enterprise must enforce a minimum 15-character password length for the account of last resort. |
| ☐ | SV-221633r508660_rule | Splunk Enterprise must enforce password complexity for the account of last resort by requiring that at least one special character be used. |
| ☐ | SV-221634r508660_rule | Splunk Enterprise must enforce a 60-day maximum password lifetime restriction for the account of last resort. |
| ☐ | SV-221635r508660_rule | Splunk Enterprise must prohibit password reuse for a minimum of five generations for the account of last resort. |
| ☐ | SV-221931r508660_rule | Splunk Enterprise must display the Standard Mandatory DoD Notice and Consent Banner and accept user acknowledgement before granting access to the application. |
| ☐ | SV-221932r508660_rule | Splunk Enterprise must only allow the use of DoD-approved certificate authorities for cryptographic functions. |
| ☐ | SV-221933r508660_rule | Splunk Enterprise must use TLS 1.2 and SHA-2 or higher cryptographic algorithms. |
| ☐ | SV-221934r508660_rule | When Splunk Enterprise is distributed over multiple servers, each server must be configured to disable non-essential capabilities. |
| ☐ | SV-221935r508660_rule | Splunk Enterprise installation directories must be secured. |
| ☐ | SV-221936r508660_rule | Splunk Enterprise forwarders must be configured with Indexer Acknowledgement enabled. |
| ☐ | SV-221937r508660_rule | Splunk Enterprise idle session timeout must be set to not exceed 15 minutes. |
| ☐ | SV-221938r508660_rule | Splunk Enterprise idle session timeout must be set to not exceed 15 minutes. |
| ☐ | SV-221939r508660_rule | Splunk Enterprise must notify the System Administrator (SA) and Information System Security Officer (ISSO) when account events are received (creation, deletion, modification, disabling). |
| ☐ | SV-221940r508660_rule | Splunk Enterprise must notify analysts of applicable events for Tier 2 CSSP and JRSS only. |
| ☐ | SV-221941r508660_rule | Splunk Enterprise must enforce the limit of 3 consecutive invalid logon attempts by a user during a 15 minute time period. |
| ☐ | SV-221942r508660_rule | Splunk Enterprise must be configured with a successful/unsuccessful logon attempts report. |
STIGQter: STIG Summary: