> 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-xsiam/insights-and-tips-cortex-xsiam/detection-engineering-and-threat-intelligence/threat-intel-management.md).

# Threat intel management

Learn how to manage threat intelligence feeds, indicators, verdicts, and sharing in Cortex XSIAM.

Threat Intel Management (TIM) aggregates indicators from feeds, enrichment, and your own investigations.

### Feeds

* **Sources:** Palo Alto Networks threat intelligence, plus commercial and open-source feeds from the Marketplace.
* **Formats:** Feed integrations support common standards and formats, including STIX/TAXII, JSON, CSV, and MISP. The supported format depends on the feed integration.
* **Ingestion:** Configure feeds in the UI, or push indicators with the API.
* **Fetch interval:** Set the **Feed Fetch Interval** for each feed integration instance.

See [Configure Threat Intelligence feed integrations](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/threat-management/threat-intel-management/indicator-configuration/configure-threat-intelligence-feed-integrations.md).

### Verdicts and source reliability

Each indicator has one verdict (Unknown, Benign, Suspicious, or Malicious), so the same indicator from several feeds isn't duplicated.

* The source with the highest **source reliability** determines the verdict. Manual verdicts rank highest, then reputation scripts, then third-party enrichment, then feeds (A to F).
* If equally reliable sources disagree, the more severe verdict is used.
* For other fields, the most reliable source wins. If reliability is tied, the most recent value wins. Tags and multi-select values are appended.

See [Indicator verdict](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/threat-management/threat-intel-management/indicator-investigation/indicator-verdict.md).

### Expiration

Set the **Indicator Expiration Method** for each feed instance: by indicator type, after a time interval, never, or when the indicator is removed from the feed. Expired indicators are kept for historical context but no longer treated as active. See [Indicator configuration](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/threat-management/threat-intel-management/indicator-configuration.md).

### Relationships and sharing

Indicators can be linked by relationships (for example, a file that communicates with a domain), so you can pivot across related intelligence. Indicator fields include TLP, tags, and expiration, which you can use to control how indicators are shared and pushed to enforcement points such as firewalls.

{% hint style="info" %}
Use the Threat Intel agent to analyze threat reports, extract indicators and CVEs, and check asset exposure.
{% endhint %}


---

# 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-xsiam/insights-and-tips-cortex-xsiam/detection-engineering-and-threat-intelligence/threat-intel-management.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.
