| CARVIEW |
Securing Splunk Enterprise
- Install Splunk Enterprise securely
- Create secure administrator credentials
- 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
- Best practices for hardening Splunk Enterprise servers and the operating systems they use
- Use network access control lists to protect your deployment
- Use access control to secure Splunk data
- About user authentication
- About configuring role-based user access
- Define roles on the Splunk platform with capabilities
- Create and manage users with Splunk Web
- Create and manage roles with Splunk Web
- Find existing users and roles
- Secure access for Splunk knowledge objects
- 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
- 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 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 on Splunk Enterprise
- Configure Ping Identity with leaf or intermediate SSL certificate chains
- Configure SAML SSO for other IdPs
- Configure authentication extensions to interface with your SAML identity provider
- Configure advanced settings for SSO
- Map groups on a SAML identity provider to Splunk roles
- Modify or remove role mappings
- Troubleshoot SAML SSO
- About multifactor authentication with Duo Security
- Configure Splunk Enterprise to use Duo Security multifactor authentication
- Configure Duo multifactor authentication for Splunk Enterprise in the configuration file
- About multifactor authentication with RSA Authentication Manager
- Configure RSA authentication from Splunk Web
- Configure Splunk Enterprise to use RSA Authentication Manager multifactor authentication via the REST endpoint
- Configure Splunk Enterprise to use RSA Authentication Manager multifactor authentication in the configuration file
- User experience when logging into a Splunk instance configured with RSA multifactor authentication
- About securing inter-Splunk communication
- Configure secure communications between Splunk instances with updated cipher suite and message authentication code
- Securing distributed search heads and peers
- Secure deployment servers and clients using certificate authentication
- Secure Splunk Enterprise services with pass4SymmKey
- How to create a role to managge risky command
- Why is the map command a risky command?
- Flagged Risky Commands- Why is Splunk no longer re...
- How to deactivate SPL safeguards on Splunk Enterpr...
- Best practices for search optimization for Splunk ...
- Check if Field is a Multivalue Field
- Set the index with a field when using collect comm...
- Get all events in a 1-minute time window around an...
- Warning User when try to execute outoutlook up com...
- Why do i get a warning triangle before actions on ...
Safeguards for risky commands
The Splunk platform contains built-in search processing language (SPL) safeguards to warn you when you are about to unknowingly run a search that contains commands that might be a security risk. This warning appears when you click a link or type a URL that loads a search that contains risky commands.
The warning does not appear when you create ad hoc searches.
This warning alerts you to the possibility of unauthorized actions by a malicious user. Unauthorized actions include:
- Copying or transferring data (data exfiltration)
- Deleting data
- Overwriting data
A possible scenario when this might occur is when a malicious person creates a search that includes commands that exfiltrate or damage data. The malicious person then sends an unsuspecting user a link to the search. The URL contains a query string (q) and a search identifier (sid), but the sid is not valid. The malicious person hopes the user will use the link and the search will run.
Commands that trigger the warning
Here is the list of search commands in that are classified as risky. Splunk considers these commands risky because, if used incorrectly, they can pose a security risk or you can potentially lose data by running the commands.
collectdeletedumpmapmcollectmeventcollectoutputcsvoutputlookuprunrunshellscriptscriptsendalertsendemailtscollect
Actions in the warning dialog box
Instead of running the search immediately, the Splunk platform analyzes the search for risky commands. If it identifies one or more risky commands, a warning dialog box appears. You have the option to cancel, run, or investigate the search.
- Cancel
- Closes the warning dialog box. The search does not run and the search is removed from the Search bar. Closing the dialog box, by clicking the Close button (X), is the same as clicking Cancel.
- Run
- Runs the search.
- Investigate
- Displays the search in the Search bar so that you can review the SPL. Use this option to copy the syntax of the search. Send a copy of the search, along with any information about the source of the link, to your system administrator.
Deactivate the warning
Only Splunk Enterprise users with write permissions to the Splunk Enterprise instance can edit the web.conf configuration file to turn off the risky SPL command warning dialog box. If you use Splunk Cloud Platform, contact your Splunk account representative to help with updating the web.conf configuration file.
On a Splunk Enterprise instance, you can turn off the warning for a specific command, or for all of the risky commands.
Turn off the warning for a specific command
- Copy the
commands.confconfiguration file, which is located in the$SPLUNK_HOME/etc/system/defaultdirectory. - Paste the copy of the file in the
$SPLUNK_HOME/etc/system/localdirectory. - Use a text editor to open the commands.conf file you copied.
- Locate the command within the file.
- After you locate the command, change the
is_riskysetting for the command fromtruetofalse. - Save the
commands.confconfiguration file and close it. - Restart Splunk Enterprise.
Turn off the warning for all of the commands
- Use a text editor to open the
web.confconfiguration file in the$SPLUNK_HOME/etc/system/default/directory. - Locate the
enable_risky_command_checksetting within the file. - Change the setting value from
truetofalse. - Save the
web.conffile and close it. - Restart Splunk Enterprise.
See also
In the Admin Manual:
| Manage data integrity | Troubleshoot Splunk forwarder TCP tokens |
This documentation applies to the following versions of Splunk® Enterprise: 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
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!