> 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/detect-investigate-and-respond-to-threats/threat-intel-management/indicator-configuration/exclude-indicators-from-enrichment.md). # Exclude indicators from enrichment Exclude indicators from automated enrichment in Cortex AgentiX. You can disable enrichment for individual indicators or disable enrichment for all indicators fetched by any of the following feeds: * Azure Feed * Office 365 Feed * Cisco WebEx Feed * Cloudflare Feed * Fastly Feed * AWS Feed * Zoom Feed * Public DNS Feed * Google IP Ranges Feed If you disable enrichment for an incoming feed, the indicators are extracted and saved but not enriched by Cortex AgentiX, enabling you to conserve system resources when dealing with known indicators. When an indicator has enrichment excluded, the **Enrich Indicator** button is disabled. If you try to enrich an indicator that is enrichment excluded, an error will occur. Indicators of the following indicator types can have enrichment excluded: * IP * Domain * Email * URL * File **Exclude enrichment for a feed integration** To exclude enrichment for indicators fetched from a feed integration, when configuring an instance of the feed integration, select the **Enrichment Excluded** checkbox. **Exclude enrichment for individual indicators** When creating or editing an indicator of one of the following types: IP, Domain, Email, URL, or File, you have the option to set **Enrichment Excluded** to **Yes** or **No**. The default is **No**. **View list of enrichment excluded indicators** To view the enrichment excluded indicators in the **Indicators** table, add the **Enrichment Excluded** column to the table. --- # 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-agentix/detect-investigate-and-respond-to-threats/threat-intel-management/indicator-configuration/exclude-indicators-from-enrichment.md?ask=&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.