> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-threat-intel-management-guides/6.14/configure-indicators/indicator-extraction/run-indicator-extraction-in-the-cli.md).

# Run Indicator Extraction in the CLI

In the CLI you can run the following commands to extract and enrich indicators:

* extractIndicators
* enrichIndicators
* Reputation commands

**extractIndicators command**

If you want to extract indicators from non-War-Room-entry sources (such as extracting from files), use the **`!extractIndicators`** command from 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)
* Text
* File path

For example, type **`!extractIndicators text="some text 1.1.1.1 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 example, **`!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:

**enrichIndicators command**

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 **`!ip`**), which is based on the indicator type that is found. The data is saved to context and to the indicator.

{% hint style="info" %}

### Note

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.
{% endhint %}

**Reputation commands (such as `!ip`)**

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

You can also click the Enrich indicator button in the indicator layout.

{% hint style="info" %}

### Note

Reputation commands, such as **`!ip`** and **`!domain`**, can only be used after you configure and enable a reputation integration instance, such as Virus Total and Whois.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-threat-intel-management-guides/6.14/configure-indicators/indicator-extraction/run-indicator-extraction-in-the-cli.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.