> 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/configure-threat-intelligence-integrations.md).

# Configure threat intelligence integrations

Configure threat intelligence integrations to ingest and enrich XTI indicators.

indicators. This downloads and installs content packs including threat intelligence feeds such as MITRE ATT\&CK, AlienVault, AWS, and enrichment sources such as VirusTotal and Whois.

Each threat intelligence integration may have unique parameters. Read the documentation for specific integration for more details.

### Parameters applied for data feeds

When configuring a data feed for ingesting new indicators, XTI consumes the following core parameters to govern data flow and trust levels:

* Tags
* TLP (Traffic Light Protocol)
* Feed Fetch Interval
* Source Reliability
* Indicator Reputation
* Bypass Exclusion List

{% hint style="info" %}
The Feed Expiration Policy parameter is currently not supported; instead it defaults to the system expiration policy for the specific indicator type. You can manually override this system default if needed.
{% endhint %}

### Parameters applied for enrichment integrations

When configuring an integration for indicator enrichment, only the Source Reliability parameter is applied. The remaining enrichment settings—such as returning errors, using legacy context, and not using the CLI by default—are currently not consumed by XTI, and are applied by Cortex as usual.

### How to add a threat intelligence integration

To configure a new threat intelligence integration:

1. Navigate to **Settings → Configurations → Threat Intelligence → Data Sources & Integrations**. This page lists all the integrations that can be used with XTI.
2. Click **+ Add New**.
3. Select an integration and configure it by entering the required parameters. Each integration may have parameters unique to that integration. Read the documentation for specific integrations for more details.

**Related links**

Each threat intelligence integration may have unique parameters. Read the documentation for specific integration for more details. For example, if you are integrating Virus Total, see [Virus Total](https://xsoar.pan.dev/docs/reference/integrations/virus-total-api-v3) integration documentation. For a list of the most commonly occurring parameters, see *Configure Threat Intelligence feed integrations*.


---

# 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/configure-threat-intelligence-integrations.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.