STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Splunk Enterprise 8.x for Linux Security Technical Implementation Guide

V-251664

CAT II (Medium)

In a distributed environment, Splunk Enterprise indexers must be configured to ingest log records from its forwarders.

Rule ID

SV-251664r960873_rule

STIG

Splunk Enterprise 8.x for Linux Security Technical Implementation Guide

Version

V2R3

CCIs

CCI-000174

Discussion

Log servers (e.g., syslog servers) are often used on network segments to consolidate from the devices and hosts on that network segment. However, this does not achieve compliance with the DoD requirement for a centralized enclave log server. To comply with this requirement, create a central log server that aggregates multiple log servers, or use another method to ensure log analysis and management is centrally managed and available to enterprise forensics and analysis tools. This server is often called a log aggregator, SIEM, or events server.

Check Content

This check is applicable to the instance with the Indexer role or the Forwarder role, which may be a different instance in a distributed environment.

Verify the Splunk Enterprise Environment is configured to ingest log records from different hosts.

On the forwarders, check if the output.conf file is configured with the details of the indexer is ingesting the log data (e.g., Hostname, port# etc.).

On the indexer, check if the input.conf file is configured with the details of the forwarders that are sending the data.

If the Splunk Enterprise is not configured to perform analysis of log records from across multiple hosts, this is a finding.

Fix Text

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

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