| V-221608 | High | Splunk Enterprise must use SSL 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... |
| V-221609 | High | Splunk Enterprise must use LDAPS for the LDAP connection. | Passwords need to be protected at all times, and encryption is the standard method for protecting passwords. If passwords are not encrypted, they can be plainly read (i.e., clear text) and easily... |
| V-221602 | High | Splunk Enterprise must have all local user accounts removed after implementing organizational level user management system, except for one emergency account of last resort. | User accounts should use an organizational level authentication mechanism such as SAML, LDAP, AD, etc., to provide centralized management.
The use of local accounts should be discouraged, except... |
| V-221600 | High | Splunk Enterprise must be installed with FIPS mode enabled, to implement NIST FIPS 140-2 approved ciphers 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... |
| V-221601 | High | Splunk Enterprise must use organization level authentication to uniquely identify and authenticate users. | To ensure accountability and prevent unauthenticated access, organizational users must be uniquely identified and authenticated to prevent potential misuse and compromise of the system.
Sharing... |
| V-221933 | High | 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... |
| V-221632 | Medium | Splunk Enterprise must enforce a minimum 15-character password length for the account of last resort. | 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... |
| V-221941 | Medium | Splunk Enterprise must enforce the limit of 3 consecutive invalid logon attempts by a user during a 15 minute time period. | By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the... |
| V-221942 | Medium | Splunk Enterprise must be configured with a successful/unsuccessful logon attempts report. | The SIEM or Central Log Server is the mitigation method for most of the other STIGs applied to an organization. Robust alerting and reporting is a key feature in any incident response plan.
The... |
| V-221607 | Medium | Splunk Enterprise must use HTTPS/SSL for access to the user interface. | A replay attack may enable an unauthorized user to gain access to the application. Authentication sessions between the authenticator and the application validating the user credentials must not be... |
| V-221605 | Medium | 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. | 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... |
| V-221628 | Medium | 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. | Detecting when multiple systems are showing anomalies can often indicate an attack. Notifying appropriate personnel can initiate a proper response and mitigation of the attack.
Splunk can... |
| V-221934 | Medium | 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... |
| V-221935 | Medium | 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... |
| V-221932 | Medium | 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... |
| V-221938 | Medium | Splunk Enterprise idle session timeout must be set to not exceed 15 minutes.
| Automatic session termination after a period of inactivity addresses the potential for a malicious actor to exploit the unattended session. Closing any unattended sessions reduces the attack... |
| V-221614 | Medium | Splunk Enterprise must use TCP for data transmission. | If the UDP protocol is used for communication, then data packets that do not reach the server are not detected as a data loss. The use of TCP to transport data improves delivery reliability, adds... |
| V-221613 | Medium | Splunk Enterprise must be configured to protect the log data stored in the indexes from alteration. | Without non-repudiation, it is impossible to positively attribute an action to an individual (or process acting on behalf of an individual).
The records stored by Splunk Enterprise must be... |
| V-221635 | Low | 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... |
| V-221634 | Low | 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... |
| V-221633 | Low | 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... |
| V-221631 | Low | Splunk Enterprise must enforce password complexity for the account of last resort 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... |
| V-221630 | Low | Splunk Enterprise must enforce password complexity for the account of last resort by requiring that at least one lower-case 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... |
| V-221940 | Low | Splunk Enterprise must notify analysts of applicable events for Tier 2 CSSP and JRSS only. | Sending notifications or populating dashboards are ways to monitor and alert on applicable events and allow analysts to mitigate issues.
Tier 2 CSSP and JRSS analysts perform higher-level... |
| V-221625 | Low | 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. | If security personnel are not notified immediately upon storage volume utilization reaching 75 percent they are unable to plan for storage capacity expansion.
Although this may be part of the... |
| V-221626 | Low | 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. | It is critical for the appropriate personnel to be aware if a system is at risk of failing to process audit logs as required. Without a real-time alert, security personnel may be unaware of an... |
| V-221627 | Low | 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. | If the system were to continue processing after audit failure, actions could be taken on the system that could not be tracked and recorded for later forensic analysis. To perform this function,... |
| V-221621 | Low | Splunk Enterprise must be configured to aggregate log records from organization-defined devices and hosts within its scope of coverage. | If the application is not configured to collate records based on the time when the events occurred, the ability to perform forensic analysis and investigations across multiple components is... |
| V-221623 | Low | 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. | Without restricting which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade... |
| V-221629 | Low | Splunk Enterprise must enforce password complexity for the account of last resort by requiring that at least one upper-case 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... |
| V-246917 | Low | The System Administrator (SA) and Information System Security Officer (ISSO) must configure the retention of the log records based on the defined security plan. | If authorized individuals do not have the ability to modify auditing parameters in response to a changing threat environment, the organization may not be able to respond effectively and important... |
| V-221936 | Low | 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. |
| V-221937 | Low | 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... |
| V-221931 | Low | 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... |
| V-221939 | Low | Splunk Enterprise must notify the System Administrator (SA) and Information System Security Officer (ISSO) when account events are received (creation, deletion, modification, disabling).
| Once an attacker establishes access to an application, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to create... |
| V-221612 | Low | 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. | Protection of log data includes ensuring log data is not accidentally lost or deleted. Backing up log records to a different system or onto separate media than the system being audited on an... |
