Splunk Enterprise must use an SSO proxy service, F5 device, or SAML implementation to accept the DOD common access card (CAC) or other smart card credential for identity management, personal authentication, and multifactor authentication.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-221605	SRG-APP-000391-AU-002290	SPLK-CL-000045	SV-221605r992017_rule	2024-08-27	3

Description
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. If the application cannot meet this requirement, the risk may be mitigated through use of an authentication server.

Description

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. If the application cannot meet this requirement, the risk may be mitigated through use of an authentication server.

ℹ️ Check
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 credential to log into the application. If it is not configured to allow the use of the DOD CAC credential, this is a finding.

✔️ Fix
Configure an SSO proxy service using Apache, IIS, F5, SAML, etc., to provide CAC 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.