| CARVIEW |
Securing Splunk Enterprise
- Install Splunk Enterprise securely
- Create a secure administrator password
- About TLS encryption and cipher suites
- Securing Splunk Enterprise with FIPS
- About default certificate authentication
- Harden the Splunk Enterprise installation directory on Windows
- 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
- Password best practices for administrators
- Configure Splunk password policies
- Configure a Splunk Enterprise password policy using the Authentication.conf configuration file
- Password best practices for users
- Unlock a user account
- Change a user password
- Manage out-of-sync passwords in a search head cluster
- Use access control to secure Splunk data
- About user authentication
- About configuring role-based user access
- About defining roles with capabilities
- Add and edit users
- 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 on Splunk Enterprise
- 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
- Help upgrading Splunk indexer cluster from 6.4 to ...
- Is Splunk Enterprise 9.4.0 (build 6b4ebe426ca6) af...
- Active KVStore version upgrade precheck FAILED
- How to upgrade the one indexer in indexer cluster
- schedule report failed
- Enterprise License Violation
- How do I debug Python code running in Splunk Enter...
- DBConnect errors and performance
- Anyone have experience with deployment servers in ...
- Routing of events located at Indexers / Search Hea...
Disable unnecessary Splunk Enterprise components
You can disable certain components of Splunk Enterprise to reduce potential attack surfaces in your deployment if you don't need to use them.
Disable unnecessary Splunk Enterprise components in single-server Splunk Enterprise deployments
- Where possible, do not run Splunk Web on forwarders of any kind.
- Where possible, disable any configuration that lets forwarders receive data on Transmission Control Protocol (TCP) or user datagram protocol (UDP) network ports or from other Splunk Enterprise instances.
Disable unnecessary Splunk Enterprise components in multiserver Splunk Enterprise deployments
- Where possible, disable any configuration that lets Search heads receive data on TCP or UDP network ports or from other Splunk Enterprise instances
- If users do not log in to Splunk Web on indexers in a distributed environment, disable Splunk Web on those indexers.
Disable Splunk Web
The fastest way to turn off Splunk Web on an instance that is capable of running it is to use Splunk Web.
- From the system bar, choose Settings > Server settings.
- Select General settings.
- In the Splunk Web section, in the Run Splunk Web radio button, select No.
- Select Save.
- Restart the Splunk Enterprise instance.
You can also deactivate Splunk Web by editing the web.conf configuration file and giving the startwebserver a value of 0 or false. You must have administrative access to the machine where you want to disable Splunk Web, and familiarity with command line tools.
- On the Splunk Enterprise instance where you want to deactivate Splunk Web, open a shell prompt or terminal window.
- From this prompt, go to the $SPLUNK_HOME/etc/system/local directory.
- Open the web.conf configuration file for editing. You might need to create this file.
- Add the following line to the
[settings]stanza within the web.conf filestartwebserver = 0
- Save the web.conf file and close it.
- Restart the Splunk Enterprise instance.
| Secure Splunk Enterprise on your network | Secure Splunk Enterprise service accounts |
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, 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.1.11, 8.1.12, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.1.7, 9.1.8, 9.1.9, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.2.5, 9.2.6, 9.3.0, 9.3.1, 9.3.2, 9.3.3, 9.3.4, 9.4.0, 9.4.1, 9.4.2
Comments
Download manual
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!