Splunk Enterprise must enforce the limit of 3 consecutive invalid logon attempts by a user during a 15 minute time period.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-221941	SPLK-CL-000240	SV-221941r879546_rule		Medium

Description
By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account. In most enterprise environments, this requirement is usually mitigated by a properly configured external authentication system, like LDAP. Splunk local authentication takes precedence over other forms of authentication, and cannot be disabled. The mitigation settings in this requirement apply in the event a local account gets created, for example, an emergency account of last resort for recovery.

Description

By limiting the number of failed login attempts, the risk of unauthorized system access via user password guessing, otherwise known as brute forcing, is reduced. Limits are imposed by locking the account. In most enterprise environments, this requirement is usually mitigated by a properly configured external authentication system, like LDAP. Splunk local authentication takes precedence over other forms of authentication, and cannot be disabled. The mitigation settings in this requirement apply in the event a local account gets created, for example, an emergency account of last resort for recovery.

STIG	Date
Splunk Enterprise 7.x for Windows Security Technical Implementation Guide	2023-06-09

Details

Check Text ( C-23655r420291_chk )
Select Settings >> Access Controls >> Password Policy Management. Verify that Lockout is Enabled, Failed login attempts is set to 3, and Lockout threshold in minutes is set to 15. If these settings are not set as described, this is a finding.

Fix Text (F-23644r420292_fix)
Select Settings >> Access Controls >> Password Policy Management. Set Lockout to Enabled. Set Failed login attempts to 3 and Lockout threshold in minutes to 15.