Splunk® SOAR (On-premises)

Use Splunk SOAR (On-premises)

The classic playbook editor will be deprecated in early 2025. Convert your classic playbooks to modern mode.
After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:

Mark files and events as evidence in

When you discover information that's critical to your conclusions, you can mark it as evidence in your investigation. Evidence can include files, artifacts, action results, events, and notes. Tagging evidence helps to separate general information from information that's directly related to diagnosing an incident. All evidence appears on the Evidence tab within an investigation.

Mark a file as evidence

Perform the following steps to mark a file as evidence:

  1. Navigate to a container in .
  2. Click Analyst to change the container to analyst view.
  3. Click the Files tab.
  4. Click the This image shows the more icon. more icon for the file.
  5. Select Mark as Evidence.
  6. Click Confirm.

Mark an event as evidence

To mark an event as evidence, select Mark as Evidence when adding the event to a case. For more information about adding events to cases, see Add objects to a case in . The following screenshot illustrates how to mark an event as evidence.

This screen image shows a sample dialog window when marking an event as evidence. There is a Mark as Evidence checkbox that is highlighted in the image.

When you add an event to an existing case, it copies all the data from the existing event into the case you're adding it to while also maintaining the original event data. The information on the Evidence tab is a copy of the original event, not the actual event.

Last modified on 07 March, 2023
Add files to an event in   View recommended playbooks, actions, and mission experts for resolving an event

This documentation applies to the following versions of Splunk® SOAR (On-premises): 5.1.0, 5.2.1, 5.3.1, 5.3.2, 5.3.3, 5.3.4, 5.3.5, 5.3.6, 5.4.0, 5.5.0, 6.0.0, 6.0.1, 6.0.2, 6.1.0, 6.1.1, 6.2.0, 6.2.1, 6.2.2, 6.3.0


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