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

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

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, some type of heartbeat configuration with all of the devices and hosts must be configured.

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

Solution

If the Splunk instance is used for Tier 2 CSSP (formerly CND-SP) or JRSS analysis, this fix is N/A.

Configure Splunk Enterprise using the reporting and notification tools to create a report with notification to the SA and ISSO of any audit failure events, such as loss of communication or logs no longer being collected.

See Also

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

Item Details

References: CAT|III, CCI|CCI-001861, Rule-ID|SV-221627r508660_rule, STIG-ID|SPLK-CL-000310, STIG-Legacy|SV-111345, STIG-Legacy|V-102401, Vuln-ID|V-221627

Plugin: Splunk

Control ID: 507bb7ec71fb8c94b8d036eb40a47d06830c9ab0e7b2f41d91775b9b6bd66676