Splunk® Enterprise

Securing Splunk Enterprise

Download manual as PDF

Download topic as PDF

How to secure and harden your Splunk software installation

Use this checklist as a roadmap for this manual to help you secure your Splunk Enterprise configuration and protect your data.

Set up authenticated users and manage user access

Use certificates and encryption to secure communications for your Splunk Enterprise configuration

Splunk Enterprise comes with a set of default certificates and keys that demonstrate encryption. Where possible, deploy your own certificates and configure them to secure Splunk Enterprise communications. See About securing Splunk with SSL.

Harden your Splunk Enterprise instances to reduce vulnerability and risk

Audit your system regularly

Audit events provide information about what has changed in your Splunk Enterprise configuration. It gives you the where and when, as well as the identity of the actor who implemented the change. Leveraging audit events provides better security and other benefits.

  • Audit your system regularly to monitor user and administrator access, as well as other activities that could tip you off to unsafe practices or security breaches.
  • Keep an eye on activities within Splunk Enterprise, such as searches or configuration changes. You can use this information for compliance reporting, troubleshooting, and attribution during incidence response.
  • Audit events are especially useful in distributed Splunk Enterprise configurations for detecting configuration and access control changes across many Splunk Enterprise instances. To learn more, see Audit Splunk Enterprise activity.
  • Use the file system-based monitoring available out of the box on most Splunk-supported operating systems. For more information about monitoring, see Monitor Files and Directories in the Getting Data In Manual.
PREVIOUS
About securing Splunk software
  NEXT
Install Splunk Enterprise securely

This documentation applies to the following versions of Splunk® Enterprise: 7.3.0, 7.3.1


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

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.

0 out of 1000 Characters