Use reputation commands, extractindicators command or
the enrichIndicators command in the CLI.
In the CLI you can run the following commands to extract
and enrich indicators:
If you want to extract indicators from non-War-Room-entry
sources (such as extracting from files), use the
the CLI. The command does not create indicators but extracts them
only. Use the command to do the following:
Validate regex: Test a specific string to see if the
relevant indicators are extracted correctly, such as a URL.
In a playbook or automation. The command extracts indicators
in a playbook or automation non-war-room-source, and potentially
also creates and enriches them (if required).
You can extract from the following:
A specified entry (an entry ID)
Investigation (Investigation ID)
For example, type
!extractIndicators text="some text 220.127.116.11 something" Auto extract=inline
The entry text contains the text of the indicators, which is
extracted and enriched.
You can also extract indicators by adding the auto-extract parameter
with the script and the mode for which you are setting it up. For
!ReadFile entryId=826@101 auto-extract=inline
Usually, when using the CLI, you want to disable indicator extraction.
For example, if you return internal/private data to the War Room,
and you do not want it to be extracted and enriched in third party
services, add auto-extract=none to your CLI command.
You can enrich indicators by doing the following:
The enrichIndicators command is usually used when you want to
batch enrich indicators. This command works on existing indicators
only (it does not create them on its own). When running the command,
the relevant enrichment command is triggered (such as
which is based on the indicator type that is found. The data is
saved to context and to the indicator.
Triggering enrichment on a substantial amount of indicators
can take time (since it's activating all enrichment integrations
per indicator) and can result in performance degradation.
Reputation commands (such as
This command can work on existing and non-existing indicators.
If extraction is on, the data is saved both to the indicator and
the incident's context. If not, then just to the context because
the mapping flow is always triggered in enrichment commands. The
default configuration is set to none in playbook tasks for extraction.
The indicator does not need to exist to run the reputation command,
as the command uses a third party threat intel integration, such
as AutoFocus, IPinfo etc.
You can also click the Enrich indicator button in the indicator layout.