UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

Splunk Enterprise must enforce password complexity for the account of last resort by requiring that at least one special character be used.


Overview

Finding ID Version Rule ID IA Controls Severity
V-221633 SPLK-CL-000370 SV-221633r992025_rule Low
Description
Use of a complex password helps to increase the time and resources required to compromise the password. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password complexity is one factor in determining how long it takes to crack a password. The more complex the password, the greater the number of possible combinations that need to be tested before the password is compromised. Special characters are those characters that are not alphanumeric. Examples include: ~ ! @ # $ % ^ *. 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 2024-06-10

Details

Check Text ( C-23348r416356_chk )
Select Settings >> Access Controls >> Password Policy Management and verify that Special character is set to greater than 0.

If Special character is set to 0, this is a finding.
Fix Text (F-23337r416357_fix)
Select Settings >> Access Controls >> Password Policy Management and set Special character to greater than 0.