> 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-8-on-prem/8.11/investigate-and-respond-to-threats/incidents-and-indicators-investigation/manage-indicators.md). # Manage indicators After you start ingesting indicators into Cortex XSOAR, you can start your investigation, including extracting indicators, creating indicators, adding indicators to an incident, and exporting indicators. The **Indicators** page displays a list of indicators added to Cortex XSOAR, where you can perform the following indicator actions: | Action | Description | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Create an indicator |

Indicators are added to the Indicators table from incoming incidents, feed integrations, or manually creating a new indicator.

When creating an indicator, in the Verdict field, you can either select a verdict or leave it blank to calculate it by clicking Save & Enrich, which updates the indicator from enrichment sources. After you select an indicator type, you can add any custom field data.

| | Create an incident | Create an incident from the selected indicator and populate relevant incident fields with indicator data. | | Edit | Edit a single indicator or select multiple indicators to perform a bulk edit. | | Delete and Exclude |

Delete and exclude one or more indicators from all indicator types or a subset of indicator types. For more information, see Delete and exclude indicators.

If you select the Do not add to exclusion list checkbox, the selected indicators are only deleted.

| | Export CSV |

Export the selected indicators to a CSV file. By default, the CSV file is generated in UTF8 format.

You need administrator permission to change server configurations including the format. To change the format, see Export incidents and indicators to CSV using the UTF8-BOM format.

| | Export STIX | Export the selected indicators to a STIX file. | | Upload a STIX file | To upload a STIX file, click the upload button (top right of the page) and add the indicators from the file. | {% hint style="info" %} ### Note By default, when editing a list or text values in an incident/indicator, the changes are not saved until you confirm your changes (clicking the checkmark icon in the value field). These icons are designed to give you additional security when updating fields in incidents and indicators. You can change this default behavior by updating the server configuration. You need administrator permission to update server configurations. For more information, see [Configure inline value fields](/cortex-xsoar-8-on-prem/8.11/configure-cortex-xsoar/incident-configuration/configure-inline-value-fields.md). {% endhint %} You can also undertake various actions on the indicator, such as: | Action | Description | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Enrich an indicator | You can view detailed information about the indicator (WHOIS information for example), using third-party integrations such as VirusTotal and IPinfo. For more information, see [Extract and enrich an indicator](/cortex-xsoar-8-on-prem/8.11/investigate-and-respond-to-threats/threat-intel-management/indicator-investigation/extract-and-enrich-an-indicator.md). | | Expire an indicator | You may want to expire an indicator to filter out less relevant alerts, allowing analysts to focus on active threats. For more information, see [Expire an indicator](/cortex-xsoar-8-on-prem/8.11/investigate-and-respond-to-threats/threat-intel-management/indicator-investigation/expire-an-indicator.md). | | View indicator relationships | Relationships enable you to enhance investigations with information about indicators and how they might be connected to other incidents or indicators. You can't create, edit, or delete relationships unless you have a TIM license. For more information, see [View indicator relationships in an investigation](/cortex-xsoar-8-on-prem/8.11/investigate-and-respond-to-threats/incidents-and-indicators-investigation/manage-indicators/view-indicator-relationships-in-an-investigation.md). | --- # 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-8-on-prem/8.11/investigate-and-respond-to-threats/incidents-and-indicators-investigation/manage-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.