Splunk® Enterprise

Securing Splunk Enterprise

Acrobat logo Download manual as PDF


Splunk Enterprise version 7.2 is no longer supported as of April 30, 2021. See the Splunk Software Support Policy for details. For information about upgrading to a supported version, see How to upgrade Splunk Enterprise.
Acrobat logo Download topic as PDF

Use access control to secure Splunk data

Role-based access control (RBAC) provides flexible and effective tools that you can use to protect data on the Splunk platform.

The Splunk platform masks data to the user much like the way a relational database manages RBAC. In some cases, total segmentation of data might be necessary. In other cases, controlling the searches and results at the presentation layer, which is something you can do with many Splunk apps, might meet your security needs.

Consider the following use cases when you decide how to set up your Splunk platform configuration and whether role-based access fits your needs or not. For example:

  • When intentionally or unintentionally exposing sensitive data to the wrong user might incur legal ramifications, consider creating indexes specifically for privileged and non-privileged accounts and assigning the indexes to roles that you create for each level of access.
  • When there are security concerns, but not so much legal risks, you can restrict access using apps. For example, you can create an app with static dashboards and assign roles with lower clearance to those dashboards. This limits the type of information that the user that holds the role may access.
  • Field encryption, search exclusions, and field aliasing to redacted data are also great ways to tighten up a limited search case.
  • For extremely sensitive data, where even allowing access to a Splunk platform instance that might have sensitive data incurs legal risk, consider procuring more than one Splunk platform instance, and then configuring each instance with the data for the appropriate audience.
Last modified on 25 July, 2021
PREVIOUS
Manage out-of-sync passwords in a search head cluster
  NEXT
About user authentication

This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 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.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.5, 8.0.10, 7.2.1, 7.0.1, 8.0.4, 8.0.9, 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.1.0, 9.1.1, 9.1.2, 9.1.3, 9.2.0, 8.0.6, 8.0.7, 8.0.8


Was this documentation topic helpful?


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