CARVIEW |
Securing Splunk Enterprise
- Install Splunk Enterprise securely
- Secure your admin account
- About TLS encryption and cipher suites
- Securing Splunk Enterprise with FIPS
- About default certificate authentication
- Secure Splunk Enterprise on your network
- Disable unnecessary Splunk Enterprise components
- Secure Splunk Enterprise service accounts
- Deploy secure passwords across multiple servers
- Harden the network port that App Key Value Store uses
- Some best practices for your servers and operating system
- Use access control to secure Splunk data
- About user authentication
- About configuring role-based user access
- About defining roles with capabilities
- Add and edit roles with Splunk Web
- Add and edit roles with authorize.conf
- Configure access to manager consoles and apps in Splunk Enterprise
- Find existing users and roles
- Delete all user accounts
- Secure access for Splunk knowledge objects
- Use network access control lists to protect your deployment
- Set up user authentication with LDAP
- Manage Splunk user roles with LDAP
- LDAP prerequisites and considerations
- Secure LDAP authentication with transport layer security (TLS) certificates
- How the Splunk platform works with multiple LDAP servers for authentication
- Configure LDAP with Splunk Web
- Map LDAP groups to Splunk roles in Splunk Web
- Configure LDAP with the configuration file
- Map LDAP groups and users to Splunk roles using configuration files
- Test your LDAP configuration on Splunk Enterprise
- Change authentication schemes from native to LDAP on Splunk Enterprise
- Remove an LDAP user safely on Splunk Enterprise
- Configure single sign-on with SAML
- Configure SSO with PingIdentity as your SAML identity provider
- Configure SSO with Okta as your identity provider
- Configure SSO with Microsoft Azure AD or AD FS as your Identity Provider
- Configure SSO with OneLogin as your identity provider
- Configure SSO with Optimal as your identity provider
- Configure SSO in Computer Associates (CA) SiteMinder
- Secure SSO with TLS certificates
- Configuring SAML in a search head cluster
- Configure Ping Identity with leaf or intermediate SSL certificate chains
- Configure SAML SSO for other IdPs
- Configure advanced settings for SSO
- Map groups on a SAML identity provider to Splunk roles
- Modify or remove role mappings
- Configure SAML SSO in the configuration files
- Troubleshoot SAML SSO
- Is pass4symmkey a critical security option for ind...
- Disabling Splunk Secure Gateway in a Cluster Deplo...
- Add Enterprise Security to on prem clustered envir...
- How to set a new pass4SymmKey password on a search...
- Verify Cluster Security Key
- Installing Enterprise Security on a Search Head Cl...
- Is there a method to change the pass4SymmKey value...
- How to install a fresh install of Enterprise Secur...
- Search Head Clustering, Enterprise Security and PC...
- Why am I getting an error telling me the Pass4Symm...
Secure your clusters with pass4SymmKey
Splunk provides a security key to let your search head or indexer clustering nodes authenticate with each other. When you set up an indexer cluster or search head cluster, you assign the same key to each node in the cluster. You use the pass4SymmKey
setting in the server.conf
file. You can set the key through Splunk Web, the configuration file, or the CLI.
pass4SymmKey
controls authentication between Splunk platform instances. It does not manage user access, nor does it negate the need to use valid SSL/TLS certificates to secure the instances.
Configure pass4SymmKey for search head clustering
Configure pass4SymmKey
when you deploy the search head cluster. See Deploy a search head cluster.
For details on configuring pass4SymmKey
on a search head cluster, including how to set it post-deployment, see Set a security key for the search head cluster.
Configure pass4SymmKey for indexer clustering
Configure pass4SymmKey
when you deploy the indexer cluster, while enabling the master node. See Enable the indexer cluster master node.
For more details on setting pass4SymmKey
on an indexer cluster, see Configure the security key.
How apps encrypt pass4SymmKey
When you specify pass4SymmKey
in clear-text for an app directory on a Splunk instance (for example: etc/apps/myapp/default/server.conf
), the software writes an obfuscated version of the key to the local file (in this example, system/local/server.conf
) when you restart the instance. Configuration files in the default directory are generally read-only, and the software writes the information to the local file, which is editable.
Placing a password directly into an app's local directory (for example: etc/apps/myapp/local/server.conf
), replaces it with the encrypted version.
When the configuration is listed using curl
or a splunkd
endpoint, the pass4SymmKey
appears encrypted. If the configuration location is read-only, Splunk software likewise writes to local.
Use OpenSSL to generate a random passphrase for pass4SymmKey
You can use the OpenSSL utilities that come with Splunk software to generate a passphrase that you can use with pass4SymmKey
.
For the strongest security, select a passphrase that is at least 12 characters long and checks out against a dictionary of known bad passphrases, like abc123
, password
, qwerty
, admin
, and so on. The OpenSSL utility that comes with Splunk software lets you randomly generate a passphrase that you can then use to set pass4SymmKey
with on all nodes of your Splunk deployment.
- On a Splunk instance, open a shell prompt.
- Change to the
$SPLUNK_HOME/bin
directory. - Run the following command to generate a random 12-character passphrase:
splunk cmd openssl rand -base64 9
- Copy the output of the command to your clipboard.
- For all machines that you want to use the new passphrase:
- Edit
$SPLUNK_HOME/etc/system/local/server.conf
. - Set
pass4SymmKey = <new passphrase that you just generated>
- Save
$SPLUNK_HOME/etc/system/local/server.conf
. - Restart Splunk software.
- Edit
Secure your deployment server and clients using certificate authentication | Use Splunk Enterprise to audit your system activity |
This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13
Comments
You must be logged into splunk.com in order to post comments. Log in now.
Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.
Your Comment Has Been Posted Above
Feedback submitted, thanks!