Splunk® Enterprise

Securing Splunk Enterprise

Audit Splunk activity

When you enable auditing, the Splunk platform sends specific events to the audit index (index=_audit). Interactions with the platform, such as searches, logins and logouts, capability checks, and configuration changes generate audit events.

What is in an audit event?

  • Timestamp:
    • date and time of the event.
  • User information:
    • the user who generated the event.
    • If the event contains no user information, the Splunk platform sets the user to whoever is currently logged in.
  • Additional information:
    • available event details -- what file, success/denial, etc.

Activities that generate audit events

The following activities generate audit events on the Splunk platform:

  • all files in the Splunk Enterprise configuration directory $SPLUNK_HOME/etc/*
  • Starts and stops of the instance.
  • Users logging in and out of the platform.
  • Additions and removals of users.
  • Changing a user's information (password, role, etc).
  • Execution of any capability on the platform.

Audit event storage

The Splunk platform stores audit events locally in the audit index (index=_audit). Audit events appear in the log file: $SPLUNK_HOME/var/log/splunk/audit.log.

If you have configured the Splunk platform as a forwarder in a distributed setting, the platform forwards audit events like any other event.

Configure audit logging

You can now configure audit logging levels like you can any other level on the Splunk platform. The category.AuditLogger category in the $SPLUNK_HOME/etc/log.cfg file controls the level at which the Splunk platform logs audit events. By default, the platform logs events at the DEBUG level. See Enable debug logging in the Troubleshooting Manual for information on how to enable debug logging.

Last modified on 13 May, 2020
Use Splunk Enterprise to audit your system activity   Use audit events to secure Splunk Enterprise

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, 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.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.3.0, 9.3.1


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