Splunk Enterprise 7.x for Windows Security Technical Implementation Guide
Rules, Groups, and Values defined within the XCCDF Benchmark
-
SRG-APP-000172-AU-002550
Group -
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 c...Rule High Severity -
SRG-APP-000080-AU-000010
Group -
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 protect...Rule Medium Severity -
SRG-APP-000516-AU-000340
Group -
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 d...Rule Medium Severity -
SRG-APP-000086-AU-000020
Group -
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 signifi...Rule Low Severity -
SRG-APP-000090-AU-000070
Group -
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 ...Rule Low Severity -
SRG-APP-000359-AU-000120
Group -
SRG-APP-000360-AU-000130
Group -
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 impe...Rule Low Severity -
SRG-APP-000361-AU-000140
Group -
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, som...Rule Low Severity -
SRG-APP-000516-AU-000350
Group -
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 aggregat...Rule Medium Severity -
SRG-APP-000166-AU-002490
Group -
Splunk Enterprise must enforce password complexity for the account of last resort 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 resistin...Rule Low Severity -
SRG-APP-000167-AU-002500
Group
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.