You can manually attach observables when you want to perform threat lookups on
observables that are not attached to a security incident on the initial event trigger. Also,
you might perform this task when you want more information about a related
observable.
Before you begin
Verify the observable is of a type supported by the
integration. The integration performs lookups on the following types of
observables:
- File hashes
- IP addresses
- URLs
Role required: sn_si.analyst
Procedure
-
Navigate to and open a security incident to which you want to attach the
observable.
-
On the open security incident, click the Show IoClink
in Related Links.
-
On the Observables tab, click
New.
The Observable form is displayed.
-
In the Value field, enter an observable (file hash, IP
addresses, or URL).
-
Click the search icon and from the Observable Type
Categories dialog box, click the desired observable type in the
list to populate the field.
-
Click Submit.
The flow launches and checks for the new observable. The execution and completion status is displayed in the work notes section on the security incident record.
-
Navigate to your security incident and review the work notes.
-
At the bottom of the record, click the Show All Related
Lists related link.
-
Click the Threat Lookup Results tab to view the results.
-
In the Observable column, click the blue information
icon next to a given observable for more information and raw data.
-
In the dialog box that is displayed, click Open Record
to view the raw data and more details.
Alternatively, you can also attach an existing observable to the security
incident record.
- Optional:
With the Observables tab selected, click
Edit.
- Optional:
In the Edit Members form that is displayed, move an
existing observable from Collection to
Observables List and click
Save.
You are returned to the security incident.
-
In the far left column, select the observables you want to run the lookup on,
and from the Actions on selected rows... choice list,
select Run threat lookup.
A message is displayed across the top of the record that the request is
being processed. Verify that the lookup has run successfully.
Review the work notes for more
information and how to proceed if you cannot verify that the lookup ran
successfully.