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

Information

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.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

If the server does not store index data, this fix is N/A.

Edit the following file in the installation folder:

$SPLUNK_HOME/etc/system/local/indexes.conf

Add the following line to each organization-defined index stanza in brackets [ ]:

enableDataIntegrityControl=true

Item Details

Audit Name: DISA STIG Splunk Enterprise 7.x for Windows v3r2 REST API

Category: AUDIT AND ACCOUNTABILITY

Plugin: Splunk

Control ID: 3efc8697bb7a840e2649fc52dbb85d46b41f3e2ef2491b45c16ee93551fe2ca2

Detections

Analytics

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

Information

Solution

See Also

Item Details