Splunk® Enterprise Security

Administer Splunk Enterprise Security

The documentation for Splunk Enterprise Security versions 8.0 and higher have been rearchitected from previous versions, causing some links to have redirect errors. For documentation on version 8.0, see Splunk Enterprise Security documentation homepage.
This documentation does not apply to the most recent version of Splunk® Enterprise Security. For documentation on the most recent version, go to the latest release.

Administering Splunk Enterprise Security

Splunk Enterprise Security administrators are responsible for configuring, maintaining, auditing, and customizing an instance of Splunk Enterprise Security. If you are not administering Splunk Enterprise Security, see Use Splunk Enterprise Security for an introduction to using this app as a security analyst.

Use the links below to learn more about administrative tasks in Splunk Enterprise Security.

Manage and support analyst workflows

To turn on and customize the workflows for analysts in your organization, see:

Enrich data for Enterprise Security

Enrich Splunk Enterprise Security with data about the assets and identities in your environment and with additional data about known threats.

Manage and customize configurations

To perform ongoing configuration in Splunk Enterprise Security, see:


You can find additional configuration information in the Install and Upgrade Manual.

Create, manage, and export content

To create new content or manage and customize existing content, see:


To share custom content with other ES instances, see Export content from Splunk Enterprise Security as an app.

Troubleshoot dashboards

Configure users and roles

Configure user roles and capabilities to provide granular, role-based access control for your organization. See Configure users and roles.

Support for blacklist and denylist attributes

The term Blacklist is replaced by the term denylist in the Splunk Enterprise Security UI. However, for older configurations, Splunk Enterprise Security might include blacklist attributes. If blacklist attributes exist in your .conf files, you might have to update the deprecated blacklist attributes to denylist attributes.

Otherwise, you might see an error message: "Deprecated asset or identity values are found in your .conf files. Update to denylist attributes."

Last modified on 01 April, 2024
  Managing Incident Review in Splunk Enterprise Security

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


Was this topic useful?







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