> 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/reference-and-developer-docs/role-based-access-control/threat-management-permissions/threat-intelligence-permissions.md).
# Threat Intelligence permissions
**Threat Intelligence permissions**
Located under **Threat Management** → **Threat Intelligence**, these permissions govern how your organization interacts with indicators (IPs, URLs, Domains, Hashes) and intelligence feeds. It allows you to transform raw data from sources like Unit 42 or AlienVault into actionable security logic.
{% hint style="info" %}
### Notice
The Extended Threat Intelligence feature requires the Cortex XSIAM Premium license or another XSIAM license with the Extended Threat Intelligence (XTI) add-on.
The Threat Intelligence Management (TIM) requires the Threat Intelligence Management (TIM) license.
{% endhint %}
For more information, see [Extended Threat Intelligence](/cortex-xsiam/detect-investigate-and-respond-to-threats/threat-management/extended-threat-intelligence.md) if you are using XTI, or [Threat Intel Management](/cortex-xsiam/detect-investigate-and-respond-to-threats/threat-management/threat-intel-management.md) if you are using TIM.
| Component | Description | Roles Example |
| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| None | In TIM, no access to the Indicators page.
In XTI, no access to the Indicators, Threat Intel Library, or Threat Intel Dashboard pages.
| |
| View | In TIM, users can search the indicator database and view reputation scores.
In XTI, users can search the Threat Intel Library, the Indicator database, and Threat Intel Dashboard.
| SOC Tier-1 analysts: View threat intelligence context for investigations. |
| View/Edit | In TIM, full control to manage indicator rules, manually override reputation scores, and configure intelligence feeds.
In XTI, full control to manage indicators and indicator rules.
| - SOC Tier-2 and 3 Analysts: Enables creating and editing indicators discovered during investigations, adding context to IOCs, and enriching case artifacts with threat intelligence data.
- Threat Hunter: Enables researching threat actors and campaigns, creating indicators from hunting discoveries, enriching IOCs with contextual data, and documenting threat intelligence findings.
- Security Engineer: Enables integrating threat intel into detection rules, testing indicator-based detections, managing IOC feeds for rule development, and validating threat intel data quality.
|
**Required and recommended permissions**
Consider adding the following permissions:
| Permission | Permission level | Reason |
| -------------------------------------------- | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cases & Issues | View | Strongly recommended. Indicator enrichment data appears in case artifacts, and editing indicators from case context requires case access. |
| Detection Rules | View/Edit | Strongly Recommended. Enables creating indicator or IOC rules directly from indicators. |
| Allow/Block List | Checked | Strongly recommended. Add to Block List is a primary action on indicators. |
| EDL | View | Strongly recommended. Add to EDL is a primary action on IP/domain indicators. |
| Query Center | View/Edit | Enables investigating indicator matches via XQL queries. Essential for validating indicator impact before creating rules or blocking. |
| Threat Intel (under Integration Permissions) | View/Edit | Recommended for configuring VirusTotal API keys for indicator enrichment. |
| Exclusion List | View/Edit | Recommended to manage indicator exclusions. Useful for managing false positive indicators. |
| Integrations | View | Recommended. TIM feed integrations are configured under Integrations. Viewing integrations helps understand which threat intel feeds are active and contributing indicators. |
---
# 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-xsiam/reference-and-developer-docs/role-based-access-control/threat-management-permissions/threat-intelligence-permissions.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.