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


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

See Also


Item Details

References: CAT|II, CCI|CCI-000166, Rule-ID|SV-251662r835283_rule, STIG-ID|SPLK-CL-000090, Vuln-ID|V-251662

Plugin: Unix

Control ID: 1a6668536312c34c3026fa75d9ccd1313aa8f59bbd02265b670a0fe372c26cbb