Splunk® Enterprise

Securing Splunk Enterprise

Download manual as PDF

Splunk Enterprise version 6.x is no longer supported as of October 23, 2019. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
Download topic as PDF

Ways you can secure Splunk Enterprise

This manual documents some of the many ways to secure your Splunk configuration and describes how to do the following:

  • Set up user authentication to create users and manage user access by assigning roles.
  • Use SSL to secure communications for your Splunk configuration.
  • Use auditing to secure your data.
  • Harden your Splunk instances to reduce vulnerability and risk.

User authentication and role-based access control

Set up users and use roles to control access. Splunk Enterprise allows you to configure users in three ways:

Once you've configured users you can assign roles that determine and control capabilities and access levels. For more information about roles and capabilities, read "About role-based user access."

Encryption and authentication with SSL

Splunk Enterprise comes with a set of default certificates and keys that, when enabled, provide encryption and data compression. You can also use your own certificates and keys to secure communications between your browser and Splunk Web as well as data sent from forwarders to a receiver, such as an indexer.

Under certain conditions, you can also secure communications in distributed search environments, configuration data sent to clients by a deployment server, and communications from Splunk Web to splunkd.

For more information about securing Splunk communications with SSL, see "About securing Splunk with SSL" in this manual.


Splunk Enterprise includes audit features to allow you to track the reliability of your data. Monitor activities within Splunk Enterprise (such as searches or configuration changes) with audit events, cryptographically sign audit events events with audit event signing, and block sign any data entering your Splunk index with IT data signing.

  • Monitoring
    You can use monitoring to index all .conf files using a white list as a best practice, and for user attribution of changes, you can 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.
  • Audit events
    Watch your Splunk instance by monitoring audit events. Audit events are generated whenever anyone accesses any of your Splunk instances -- including any searches, configuration changes or administrative activities. Each audit event contains information that shows you what changed where and when and who implemented the change. Audit events are especially useful in distributed Splunk configurations for detecting configuration and access control changes across many Splunk Servers.
    To learn more, see "Audit Splunk Enterprise activity" in this manual.
  • Audit event signing
    If you have an Enterprise license, you can configure audit events to be cryptographically signed. Audit event signing adds a sequential number (for detecting gaps in data to reveal tampering), and appends an encrypted hash signature to each audit event. Configure auditing by setting stanzas in audit.conf, and inputs.conf.
    To learn more, see "Cyrptographically sign audit events" in this manual.
  • Archive signing
    You can use archive signing to sign your Splunk data when it gets archived (rolled from cold to frozen). An archive signature is a hash signature of all the data in the archived bucket. Archive signing lets you verify integrity when you restore an archive.
    To learn more, see "About archive signing" in this manual.
  • Event hashing
    Event hashing provides a lightweight way to detect if events have been tampered with between index time and search time. Event hashing is only recommended if you are unable to run the Splunk IT data block signing capabilities.
    To learn more, see "Configure event hashing" in this manual.
About securing Splunk Software

This documentation applies to the following versions of Splunk® Enterprise: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.0.8, 6.0.9, 6.0.10, 6.0.11, 6.0.12, 6.0.13, 6.0.14, 6.0.15, 6.1, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12, 6.1.13, 6.1.14

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