Password best practices for administrators
Passwords are one of the most common points of unauthorized access in successful security breaches.
The National Institute of Standards and Technology (NIST) proposes significant changes to the rules governing passwords, upending many of the classic ways to prevent weak passwords. Splunk provides the traditional means to drive more secure passwords and continues to monitor and update security requirements based on customer feedback.
Splunk Enterprise provides configuration options for the following password characteristics:
- Expiration and password reuse (history)
- Lockout after failed attempts
To set up a password policy, see the following topics:
- Configure Splunk password policies
- Configure a Splunk password policy in Authentication.conf (on Splunk Enterprise only)
Password policy best practices
The following best practices help significantly lower the chances of unauthorized access to Splunk and other systems:
Require a longer password length
- Long passwords or passphrases are the best way to secure access. Using passwords of ten or more characters prevents the use of rainbow tables and dramatically inhibits password-cracking software that decodes password hashes. A password is more secure when it requires more characters. The required minimum is 8 characters and you can set a length up to 256 characters.
Require a complex password
- Traditional guidance requires the use of multiple character types in a password, such as lowercase and uppercase letters, numbers, and special characters. This helps prevent dictionary words in passwords and increases resistance to brute-force attacks.
Because complex passwords can be difficult to remember and do not add significantly to the strength of passwords, NIST no longer suggests this requirement. However, Splunk Enterprise supplies this option because it is still commonly part of regulatory compliance for many organizations.
Use Password expiration
- Traditional guidance is to force users to change passwords four or more times per year. Many compliance regulations require this value be set to 90 days or fewer. NIST guidance no longer recommends this, because users tend to change the last character in their password. As a result, any compromised passwords can be used to guess new passwords. Set the maximum password age to any value from 0 to 3650 days, where a value of 0 means that passwords do not expire.
Password expiration is off by default on Splunk platform instances.
Enforce Password History
- Enable password history to ensure that a user's most recent passwords are saved. Any password saved to a user's history cannot be used again. With this policy, you discourage users from alternating between several common passwords.
Password history is off by default.
Use password lockout
Password lockout temporarily locks users out of the system after a certain number of failed attempts. Password lockout is on by default and occurs five attempts. You can specify how many attempts the user has, and how long the lockout period must last. The default is 30 minutes. In less secure environments, you can set the lockout time for longer to be sure that an unverified user cannot access the system.
Password lockout is on by default.
Some best practices for your servers and operating system
Configure Splunk password policies
This documentation applies to the following versions of Splunk® Enterprise: 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 9.0.0