STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to Splunk Enterprise 8.x for Linux Security Technical Implementation Guide

V-251668

CAT II (Medium)

Splunk Enterprise must be configured to offload log records onto a different system or media than the system being audited.

Rule ID

SV-251668r961395_rule

STIG

Splunk Enterprise 8.x for Linux Security Technical Implementation Guide

Version

V2R3

CCIs

CCI-001851

Discussion

Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Offloading is a common process in information systems with limited audit storage capacity. Although this may be part of the operating system function, for the enterprise events management system, this is most often a function managed through the application since it is a critical function and requires the use of a large amount of external storage.

Check Content

Verify the Splunk Enterprise Environment is configured to offload log records to an external source.

On the forwarder, check that the outputs.conf file is configured with the details of the source that the logs will be sent to (e.g. Hostname, port# etc.).

If the Splunk Enterprise is not configured to offload log records to an external source, this is a finding.

Fix Text

This configuration is performed on the machine used as a forwarder, which is always a separate machine regardless of environment.

On the forwarders, configure the outputs.conf with the information of the indexer that the data will be sent to for analysis. 

This configuration is performed on the machine used as the assigned indexer to the forwarder in a distributed environment.

On the indexer, configure the inputs.conf file with the information of the forwarders that are sending the data for analysis.