SPLK-CL-000105 - 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.

Information

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 records will be retained.

This helps to ensure that a compromise of the information system being audited does not also result in a compromise of the log records.

This requirement only applies to applications that have a native backup capability for log records. Operating system backup requirements cover applications that do not provide native backup functions.

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

Solution

Implement a backup plan for the Splunk log data, following the Splunk documentation on backing up indexed data. Use the underlying OS backup tools, or another approved backup tool.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Splunk_Enterprise_7-x_for_Windows_V3R1_STIG.zip

Item Details

Category: AUDIT AND ACCOUNTABILITY

References: 800-53|AU-9(2), CAT|III, CCI|CCI-001348, Rule-ID|SV-221612r960948_rule, STIG-ID|SPLK-CL-000105, STIG-Legacy|SV-111579, STIG-Legacy|V-102629, Vuln-ID|V-221612

Plugin: Splunk

Control ID: 499eb95aea1def4f3002c71d7da8117e02ad5a7c76faa7c05ff2f1016b50a7d9