> 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-xdr/detect-investigate-and-respond-to-threats/threat-management/extended-threat-intelligence/xti-indicators/exclude-xti-indicators-from-enrichment.md).

# Exclude XTI indicators from enrichment

Configure exclusion lists to prevent XTI indicators from enrichment.

You can exclude XTI indicators from enrichment by adding them to an exclusion list. Indicators listed in exclusion rules may be extracted/discovered from issues, but will not be enriched by any intel sources, including Unit 42.

From the **Exclusion List** page available from **Settings → Configurations → Threat Intelligence**, you can view the list of excluded indicators, add an indicator to the exclusion list, or define indicator values to be excluded using a regular expression (regex) or CIDR.

{% hint style="info" %}
If you are using Threat Intelligence Management (TIM), you can also navigate to **Settings → Configurations → Object Setup → Indicators → Exclusion List** to configure exclusion lists for XTI indicators. The exclusion lists configured on this page apply to TIM and XTI indicators.
{% endhint %}

To add a new indicator to an exclusion list:

1. Navigate to **Settings → Configurations → Threat Intelligence → Exclusion List**.
2. Click on **New excluded indicator**.
3. Provide the following information:
   1. **Value**: Add the indicator value. For example, “demisto.com” for a domain. Ensure you are using the correct syntax when defining the values for your exclusion lists.
   2. (Optional) **Use Regex**: Select whether to use Regex. A regular expression allows you to match character patterns in a string. The following example would identify "[www.demisto.com](http://www.demisto.com)": *\[A-Za-z0-9!@#$%\\.&]\*demisto\[A-Za-z0-9!@#$%\\.&]\** 

      Classless inter-domain routing (CIDR) enables you to define a range of IP addresses. For example, the IPv4 block 192.168.100.0/22 represents the 1024 IPv4 addresses from 192.168.100.0 to 192.168.103.255.
   3. (Optional) **Reason**: Add a reason as to why you are excluding the indicator.
   4. (Optional) **Select Indicator Type**: Choose every XTI indicator type to be excluded. The dropdown menu includes all indicator types supported across XTI and TIM. For XTI, select any combination of the following: **Domain, File SHA-256, IP, URL**.
4. Click on **Exclude it** to save the excluded indicator.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xdr/detect-investigate-and-respond-to-threats/threat-management/extended-threat-intelligence/xti-indicators/exclude-xti-indicators-from-enrichment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.