Splunk® Enterprise Security

Use 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.

Take action on a notable on Incident Review in Splunk Enterprise Security

From Incident Review, you can suppress or share a notable event, add an event or multiple events to an investigation, analyze the risk that an asset or identity poses to your environment, or investigate a field in more detail on another dashboard.

Run an adaptive response action

Based on the details in a notable event, you may want to run a response action to gather more information, take an action in another system, send information to another system, modify a risk score, or something else.

Prerequisite
Some custom adaptive response actions use the credential store to connect to a third-party system or app. To run these actions successfully, you must have the list_storage_passwords capability.

Steps

  1. From a notable event, select the arrow to expand the Actions column.
  2. Click Run Adaptive Response Actions.
  3. Click Add New Response Action and select an adaptive response action from the list. You can use the category filter or search to reduce the number of actions that you can select.
  4. Fill out the form fields for the response action. Use the field name to specify a field, rather than the name that shows on Incident Review.
    For example, type "src" instead of "Source" to specify the source field for an action.
  5. Click Run.

You can check the status of the response action in the notable event details. View the original field names of fields displayed on Incident Review on the Incident Review - Event Attributes panel of the Incident Review Settings dashboard.

Adblock extensions in your browser can cause response actions to fail. Add the host name of your Splunk Enterprise Security host to the site whitelist for the adblock extension.

See Included adaptive response actions with for more about the different adaptive response actions included with .

Share or bookmark a notable event

You can share a notable event with another analyst using a short ID or a link.

  1. From the event actions, click Share Notable Event.
    Enterprise Security creates a short ID for the notable event and displays a link that you can copy to share with an analyst. You can also save the link as a bookmark by dragging the bookmark icon to the bookmarks toolbar in your web browser.

You cannot share a notable event from the Search dashboard.

Analyze risk of an asset or identity

You can analyze the risk that an asset or identity poses to your environment in the Incident Review dashboard.

  1. Open the event details.
  2. Review the risk score next to asset or identity fields such as src or host.
  3. Click the risk score to open the Risk Analysis dashboard filtered on the asset or identity.

Not all assets and identities display a risk score. Risk scores that display for an asset or identity in Incident Review may not match the risk score on the Risk Analysis dashboard for that risk object. For more information, see How risk scores display in Incident Review in Administer Splunk Enterprise Security.

Add a notable event to an investigation

Investigate notable events that could be a part of a security incident by adding them to an investigation.

Add a notable event to an existing investigation

  1. Add one or more notable events to an investigation.
    1. Add a single notable event by selecting Add Event to Investigation from the Event Actions.
    2. Add multiple notable events by selecting the check boxes next to the notable events and click Add Selected to Investigation.
  2. Select an investigation to add the notable events to. If you selected an investigation in the investigation bar, that investigation is selected by default.
  3. Click Save.
  4. After the event or events are successfully added to the investigation, click Close.

Add a notable event to a new investigation

  1. Select one or several notable events and click Add Selected to Investigation.
  2. Click Create Investigation to start a new investigation.
  3. Type a title for the investigation.
  4. (Optional) Change the default status.
  5. (Optional) Type a description.
  6. Click Save to save the investigation and add the notable event or notable events to the investigation. Clicking Cancel does not add the selected notable events, but the new investigation is still created. You can click Start Investigation to add the notable events to the investigation and open the investigation.
  7. After the event or events are successfully added to the investigation, click Close or click Open <Investigation name> to open the investigation.

See Investigations in Splunk Enterprise Security for more.

After you add a notable event to an investigation, you can filter by notable events on that investigation on the Incident Review dashboard using the Associations filter, or view the investigation in the notable event details.

When adding a sequenced event to an investigation, the contributing notable events will be added instead. For more information about creating sequenced events, see Create sequence templates in Splunk Enterprise Security.

Get notified about incoming related notable events

While you are investigating an event, you can get notified about incoming notable events that are related to the investigation via the investigation toolbar. The investigation toolbar is available on all ES dashboards. Settings enabled for an investigation in one dashboard are carried over to that investigation in other dashboards automatically.

Enable the related notable event livefeed.

  1. Click the bell icon on the investigation toolbar at the bottom-right side of the Incident Review page, the Investigation Workbench, or any ES dashboard.
  2. Toggle the switch to enable notification for the livefeed.
  3. Click Close.

While you are investigating, you will get a visual notification if any related notable events occur. The bell icon color will change to orange within five minutes of the occurrence.

Acknowledge the livefeed notification or add notable events to the investigation.

  1. Hover over the orange bell icon on the investigation bar at the bottom-right side of the Incident Review page or the Investigation Workbench. This tells you how many notable events are available.
  2. Click the orange bell icon.
  3. The related notable event livefeed window appears, containing events from the last 48 hours.
  4. (Optional) Click + to add a notable event to the investigation.
  5. Click Mark All as Seen to clear the livefeed when you no longer want to see the related events. This will also reset the notification, so that these no longer count against the notification number mentioned in step 1.
  6. Click Close.

Investigate a field in more detail

Take action on a specific field, such as host, src, src_ip, dest, or dest_ip. Different actions are available to take depending on the field you select.

  • Tag fields by selecting Edit tags.
  • Investigate an asset by selecting Asset Investigator to open the Asset Investigator dashboard filtered on the asset.
  • Search for access-related events for a specific destination IP address by selecting Access Search (as destination).
  • Investigate a domain by selecting Domain Dossier.
  • Find other notable events with matching malware signatures by selecting Notable Event Search.
  • Use the embedded workbench to get more context about specific field values.

Example of using the embedded workbench

The embedded workbench provides a simplified drill-down experience, reduces the number of open tabs, and makes it easier to determine notable event trends.

Using the source field as an example, consider a value where you want more context about an asset. From the Enterprise Security menu bar, perform the following steps:

  1. Go to Incident Review.
  2. From a notable event that contains a Source (src) value:
  3. Click the source field actions menu.
  4. Scroll down to the menu items that start with "workbench" and select one such as Workbench - Authentication (src).
  5. View source analysis related to investigated assets or identities. The data source is the Authentication data model. Results include events that contain artifacts in the src, dest, user, user_id, user_role, src_user, src_user_id, src_user_role, or vendor_account fields.

Suppress a notable event

Hide notable events from the Incident Review dashboard by suppressing them. Creating a notable event suppression does not change the counts of notable events on the posture or auditing dashboards. See Create and manage notable event suppressions for more details.

  1. Select a notable event on the Incident Review dashboard.
  2. From the Actions menu, select Suppress Notable Events.
  3. Type a Suppression Name.
    For example, Excessive_Failed_Logins.
    IR-suppression-set-4-2-0.png
  4. (Optional) Provide a reason for the suppression using the Description field.
  5. (Optional) Set a date range. After the time limit ends, the suppression filter expires and stops hiding events.
  6. Review the Selected Fields to validate the fields that you want to suppress notable events from. For example, the src field
  7. (Optional) Click change to modify the notable event fields used for the suppression.
    IR-suppression-fields-4-2-0.png
  8. Save changes.

This example notable event suppression hides all notable events created after June 10, 2016 that contain a src=_jdbc_ field from Incident Review.

You cannot suppress notable events from the Search dashboard.

Last modified on 22 November, 2021
Investigate a notable on Incident Review in Splunk Enterprise Security   Included adaptive response actions with

This documentation applies to the following versions of Splunk® Enterprise Security: 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


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