Skip to content
Log In

Splunk Enterprise must be configured to protect the log data stored in the indexes from alteration.

An XCCDF Rule

Description

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 or date/time, or it must severely restrict the ability to do so.

ID
SV-251662r960864_rule
Version
SPLK-CL-000090
Severity
Medium
References
Updated

Remediation Templates

A Manual Procedure

If the indexes.conf file does not exist, copy the file from $SPLUNK_HOME/etc/system/default to the $SPLUNK_HOME/etc/system/local directory.

Modify the following lines in the indexes.conf file under each index:

enableDataIntegrityControl = 1 or True