STIGUI
V-221601CAT I — High severitySV-221601r960969_rule

Splunk Enterprise must use organization level authentication to uniquely identify and authenticate users.

Rule version SPLK-CL-000020 · STIG v3 · 2024-08-27

Discussion

To ensure accountability and prevent unauthenticated access, organizational users must be uniquely identified and authenticated to prevent potential misuse and compromise of the system.

Sharing of accounts prevents accountability and non-repudiation. Organizational users must be uniquely identified and authenticated for all accesses. The use of an organizational level authentication mechanism provides centralized management of accounts, and provides many benefits not normally leveraged by local account mechanisms.

Check

If the instance being checked is in a distributed environment and has the web interface disabled, this check is N/A.

Select Settings >> Access Controls >> Authentication method.

Verify that LDAP or SAML is selected.

If LDAP or SAML is not selected, this is a finding.

Fix

Select Settings >> Access Controls >> Authentication method.

If using LDAP for user accounts: Select LDAP and create an LDAP strategy with the proper settings to connect to the LDAP server. Map the appropriate LDAP groups to the appropriate Splunk roles for proper user access.

If using SAML for user accounts: Select SAML and create an SAML strategy with the proper settings to connect to the SAML provider. Map the appropriate SAML groups to the appropriate Splunk roles for proper user access.

Identifiers

Group ID
V-221601
Group title
SRG-APP-000148-AU-002270
Rule ID
SV-221601r960969_rule
Check ID
C-23316r663925_chk
Fix ID
F-23305r416261_fix