| Finding ID |
Severity |
Title |
Description |
|
V-251692
|
High |
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 for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as a primary component of layered protection for national... |
|
V-251691
|
High |
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 requirement applies only to those applications that are either distributed or can allow access to data non-locally. Use of this requirement will be limited to situations... |
|
V-251689
|
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 for the cryptographic module used by the network device, the application, operating system, or protocol must be configured to use one of the following hash functions... |
|
V-251686
|
High |
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 providing no protection to the information or data. In effect, the data would be considered unprotected plaintext. If the agency specifies that the... |
|
V-251679
|
High |
Splunk Enterprise must use organization-level authentication to uniquely identify and authenticate users. |
To assure accountability and prevent unauthenticated access, organizational users must be uniquely identified and authenticated to prevent potential misuse and compromise of the system.
Sharing of accounts prevents accountability and non-repudiation. Organizational users must be uniquely identified and authenticated for all accesses. |
|
V-251690
|
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 security controls. If the CA used for verifying the certificate is not a DOD-approved CA, trust of this CA has not been established.... |
|
V-251680
|
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 vulnerable to a replay attack.
Anti-replay is a cryptographically based mechanism; thus, it must use FIPS-approved algorithms. An authentication process resists... |
|
V-251678
|
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 in distributed environments, where the application functions are spread out over multiple servers. These unnecessary capabilities or services... |
|
V-251677
|
Medium |
Analysis, viewing, and indexing functions, services, and applications used as part of Splunk Enterprise must be configured to comply with DoD-trusted path and access requirements. |
Access to Splunk Enterprise for analysis, viewing, indexing functions, services, and applications, such as analysis tools and other vendor-provided applications, must be secured. Software used to perform additional functions, which resides on the server, must also be secured or could provide a vector for unauthorized access to the events repository. |
|
V-251676
|
Medium |
Splunk Enterprise must be configured with a report 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. |
|
V-251675
|
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 data integrity, and gives the option to encrypt the traffic. |
|
V-251674
|
Medium |
Splunk Enterprise must be configured to retain the identity of the original source host or device where the event occurred as part of the log record. |
In this case the information producer is the device based on IP address or some other identifier of the device producing the information. The source of the record must be bound to the record using cryptographic means.
Some events servers allow the administrator to retain only portions of the record... |
|
V-251672
|
Medium |
Splunk Enterprise installation directories must be secured. |
If audit data were to become compromised, then competent forensic analysis and discovery of the true source of potentially malicious system activity is difficult if not impossible to achieve. In addition, access to audit records provides information an attacker could potentially use to his or her advantage.
To ensure the... |
|
V-251668
|
Medium |
Splunk Enterprise must be configured to offload log records onto a different system or media than the system being audited. |
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.
Offloading is a common process in information systems with limited audit storage capacity. Although this may be part of the operating system function, for the enterprise events management system, this is most often a function managed... |
|
V-251666
|
Medium |
Splunk Enterprise must be configured to retain the DoD-defined attributes of the log records sent by the devices and hosts. |
Log records can be generated from various components within the application (e.g., process, module). Certain specific application functionalities may be audited as well. The list of audited events is the set of events for which audits are to be generated. This set of events is typically a subset of the... |
|
V-251664
|
Medium |
In a distributed environment, Splunk Enterprise indexers must be configured to ingest log records from its forwarders. |
Log servers (e.g., syslog servers) are often used on network segments to consolidate from the devices and hosts on that network segment. However, this does not achieve compliance with the DoD requirement for a centralized enclave log server.
To comply with this requirement, create a central log server that aggregates... |
|
V-251662
|
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 protected against alteration. A hash is one way of performing this function. The server must not allow the removal of identifiers... |
|
V-251660
|
Medium |
Splunk Enterprise must automatically lock the account until the locked account is released by an administrator when three unsuccessful login attempts in 15 minutes are exceeded. |
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 account. |
|
V-251659
|
Medium |
Splunk Enterprise must enforce the limit of three 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 account.
In most enterprise environments, this requirement is usually mitigated by a properly configured external authentication system, like LDAP.... |
|
V-251657
|
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 surface to the application.
Satisfies: SRG-APP-000295-AU-000190, SRG-APP-000389-AU-000180 |
|
V-251688
|
Low |
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 to be changed at specific policy-based intervals.
If the information system or application allows the user to consecutively reuse their password when... |
|
V-251687
|
Low |
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 users to change their passwords, there is the risk that the system and/or application passwords could be compromised.
This... |
|
V-251685
|
Low |
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 resisting attempts at guessing and brute-force attacks.
Password complexity is one factor in determining how long it takes to... |
|
V-251684
|
Low |
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 effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that... |
|
V-251683
|
Low |
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 resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-251682
|
Low |
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 resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-251681
|
Low |
Splunk Enterprise must be configured to enforce password complexity by requiring that at least one uppercase 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 resisting attempts at guessing and brute-force attacks.
Password complexity is one factor of several that determine how long it... |
|
V-251673
|
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 organizationally defined frequency helps to ensure that in the event of a catastrophic system failure, the log... |
|
V-251671
|
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, some type of heartbeat configuration with all of the devices and hosts must be configured. |
|
V-251670
|
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 impending failure of the audit function and application operation may be adversely affected. |
|
V-251669
|
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 operating system function, for the enterprise events management system, this is most often a function managed through the application since... |
|
V-251667
|
Low |
Splunk Enterprise must allow only the individuals appointed by the information system security manager (ISSM) to have full admin rights to the system. |
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 the system's performance by overwhelming the audit log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the... |
|
V-251665
|
Low |
The System Administrator (SA) and Information System Security Manager (ISSM) 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 forensic information may be lost.
The organization must define and document log retention requirements for each device and host and... |
|
V-251663
|
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 significantly degraded. Centralized log aggregation must also include logs from databases and servers (e.g., Windows) that do not natively send logs... |
|
V-251661
|
Low |
Splunk Enterprise must display the Standard Mandatory DOD Notice and Consent Banner before granting access to the server. |
|
|
V-251658
|
Low |
Splunk Enterprise must notify the system administrator (SA) and information system security officer (ISSO) when account events are received (creation, deletion, modification, or disabling). |
Once an attacker establishes access to an application, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply create a new account. Sending notification of account creation events to the system administrator and ISSO is one method... |
