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-251692

CAT I (High)

Splunk Enterprise must accept the DOD CAC or other PKI credential for identity management and personal authentication.

Rule ID

SV-251692r992052_rule

STIG

Splunk Enterprise 8.x for Linux Security Technical Implementation Guide

Version

V2R3

CCIs

CCI-001953CCI-004047

Discussion

The use of PIV credentials facilitates standardization and reduces the risk of unauthorized access. DOD has mandated the use of the CAC to support identity management and personal authentication for systems covered under Homeland Security Presidential Directive (HSPD) 12, as well as a primary component of layered protection for national security systems. DOD has approved other methods of PKI, including YubiKey, RSA tokens, etc. If the application cannot meet this requirement, the risk may be mitigated through use of an authentication server.

Check Content

If the instance being checked is in a distributed environment and has the web interface disabled, this check is Not Applicable.

Verify that Splunk Enterprise is configured to use the DOD CAC or other PKI credential to log in to the application.

If it is not configured to allow the use of the DOD CAC or other PKI credential, this is a finding.

Fix Text

Configure an SSO proxy service using Apache, IIS, F5, SAML, etc., to provide PKI credentials to Splunk Enterprise. 

Examples for Apache and F5 are provided using the supplemental documentation included in this package to be used in addition to the Splunk documentation.