> 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-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/customize-your-playbook/extract-indicators.md). # Extract Indicators In Cortex AgentiX, the indicator extraction feature extracts indicators from issue fields and enriches them using commands and scripts. For more information about indicator extraction, see [Extract and enrich an indicator](/cortex-agentix/detect-investigate-and-respond-to-threats/threat-intel-management/indicator-investigation/extract-and-enrich-an-indicator.md). How to set up indicator extraction in a playbook task 1. Select the playbook where you want to add indicator extraction, and click Edit. 2. In the playbook, click a task to open the Task Details pane. 3. Click the Advanced tab. 4. For Indicator Extraction mode, select the mode you want to use (default is none). 5. Click OK. The following scenario shows how indicator extraction is used in the Process Email - Generic v2 playbook to extract and enrich a very specific group of indicators. This playbook parses the headers in the original email used in a phishing attack. It is important to parse the original email used in the phishing attack and not the email that was forwarded to ensure that you only extract the email headers from the malicious email and not the one your organization uses to report phishing attacks. 1. Navigate to the Playbooks page and search for the Process Email - Generic v2 playbook. 2. Click ![three-dots.png](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABoAAAAeCAYAAAAy2w7YAAAACXBIWXMAABJ0AAASdAHeZh94AAAAB3RJTUUH6QMfDSo09EJ2PQAAAIBJREFUSIntlCEOwCAMRf8WNMfpNXrWmt4IhwFNYI5NTKxmWUaf+qLJS5ufbmOMgRfY35C4yEUuOhEREBGICCJiEgXLcCkFvfeZLZg2CiHc5idsa/86L8OVxcugqmBmMDNU1SQyHTrnjJTSzBa+WYbWGmqtAIAYo0m2eOtc9G/RAX7QRNu0LuROAAAAAElFTkSuQmCC) and select either Duplicate (create a copy of the playbook to edit) or Edit Playbook (detach the playbook). 3. Open the Add original email details to context task, and for the Script drop down, change the script from Set to ParseEmailFilesV2. Under the Outputs tab, you can see all of the different data that the task extracts. ![xsiam-playbook-extract-indicators.png](https://docs-cortex.paloaltonetworks.com/api/khub/maps/2iKvnhFnGXeKYHSA2AFcVw/resources/0Q_Bvv5BK2yiNrLZBpctQA-2iKvnhFnGXeKYHSA2AFcVw/content?v=dc11295d912709ed\&Ft-Calling-App=ft/turnkey-portal) 4. Click the Advanced tab and set Indicator Extraction mode to **`Inline`**. This ensures all the outputs are processed before the playbook moves ahead to the next task. 5. Open the Display email information in layout - Email.Headers task. This task receives the data from the saved attachment tasks and sets the various data points to context. 6. Click the Advanced tab and set Indicator Extraction mode to **`None`** , because the indicators were already extracted earlier in the Extract email artifacts and attachments task and there is no need to extract them again. ### **Indicator extraction modes** Indicator extraction supports the following modes: * **None:** Indicators are not extracted automatically. Use this option when you do not want to further evaluate the indicators. * **Inline:** Indicators are extracted within the context that indicator extraction runs (synchronously). The findings are added to the context data. For example, if indicator extraction for a playbook task is inline, extraction occurs before the next playbook tasks run. This configuration may delay playbook execution (issue creation). While indicator creation is asynchronous, indicator extraction and enrichment are run synchronously. Data is placed into the issue context and is available via the context for subsequent tasks. * **Out of band:** Indicators are extracted in parallel (asynchronously) to other actions. The extracted data will be available within the issue, however, it is not available for immediate use in task inputs or outputs because the information is not available in real-time.

When using out of band, the extracted indicators do not appear in the context. If you want the extracted indicators to appear select inline.

* If system-wide indicator extraction is enabled, indicators are extracted according to the following rules: * Issue creation - inline * Issue field change - inline * Tasks - none, can be overridden on a per task basis * CLI - out of band, but can be overridden on a per-command basis ### **Troubleshoot indicator extraction** If indicators are not extracted, check whether the indicator mode is set to none. Even if you select the relevant issue fields and the indicators to extract, if the mode is set to none, indicators do not extract.
--- # 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-agentix/configure-cortex-agentix/automations/playbooks/build-your-playbook/customize-your-playbook/extract-indicators.md?ask=&goal= ``` `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.