Manage investigations in Splunk Enterprise Security
As an Enterprise Security administrator, you can manage access to security investigations, and support analysts by troubleshooting problems with their action history.
For more information about the analyst investigation workflow, see Investigations in Splunk Enterprise Security in Use Splunk Enterprise Security.
Manage access to investigations
Users with the ess_admin role can create, view, and manage investigations by default. Users with the ess_analyst role can create and edit investigations. Make changes to capabilities with the Permissions dashboard.
- To allow other users to create or edit an investigation, add the Manage Your Investigations capability to their role. Users can only make changes on investigations on which they are a collaborator.
- To allow other users to manage, view, and delete all investigations, add the Manage All Investigations capability to their role.
See Configure users and and roles in the Installation and Upgrade Manual.
You can manage who can make changes to an investigation by setting write permissions for collaborators on a specific investigation. By default, all collaborators have write permissions for the investigations to which they are added, but other collaborators on the timeline can change those permissions to read-only. See Make changes to the collaborators on an investigation in Use Splunk Enterprise Security.
After a user creates an investigation, any user with the Manage All Investigations capability can view the investigation, but only the collaborators on the investigation can edit the investigation. You cannot view the investigation KV Store collections as lookups. Only users with the admin role can view or modify the KV store collections using the KV Store API endpoint. For details about using the KV Store API endpoint, see KV Store endpoint descriptions in the Splunk Enterprise REST API Reference Manual.
Data sources for investigations
stores investigation information in several KV Store collections. The investigations on the Investigations page, items added to the investigation, attachments added to notes on the investigation, and artifacts added to the investigation workbench each have their own collection. See Investigations in the Dashboard requirements matrix for Splunk Enterprise Security.
Investigation details from investigations created in versions earlier than 4.6.0 of Splunk Enterprise Security are stored in two KV Store collections,
investigative_canvas_entries. Those collections are preserved in version 4.6.0 but the contents are added to the new investigation KV Store collections. So to restore, you may need to restore
Troubleshoot investigation action history items
When an analyst selects a type of action history to add to an investigation, one of five searches run over the selected time range.
- Dashboard Views - Action History
- Search Tracking - Action History
- Per-Panel Filtering - Action History
- Notable Suppression - Action History
- Notable Status - Action History
View the searches by navigating to Configure > Content > Content Management and using the filters on the page. If you change these saved searches, action history items might fail to appear in your action history. To exclude a search from your action history, use the Action History Search Tracking Whitelist lookup. See Create and manage lookups in Splunk Enterprise Security.
Expand tokens in notable events using the expandtoken command
Administer and customize the investigation workbench
This documentation applies to the following versions of Splunk® Enterprise Security: 5.2.0, 5.2.1, 5.2.2, 5.3.0, 5.3.1, 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.1, 6.2.0, 6.3.0 Cloud only, 6.4.0, 6.4.1, 6.5.0 Cloud only, 6.5.1 Cloud only, 6.6.0, 6.6.2