> 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/configuration-permissions/threat-intelligence-permission-api-configuration.md).

# Threat Intelligence permission - API configuration

Controls access to the configuration page for external threat intelligence API keys (Virus Total) on Settings → Configurations → Integrations → Threat Intelligence. This configuration enables the enrichment of indicators within the tenant using Virus Total.

| Permission | Description                                                                                | Role Example                                                                                                           |
| ---------- | ------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| None       | The user cannot access or view the Threat Intelligence configuration page.                 | SOC Tier-1 Analyst: Uses TI data but doesn't configure.                                                                |
| View       | Users can see if a VirusTotal API key is configured but cannot add, edit, or test the key. | SOC Tier-2 and 3 Analysts: May need to review TI configurations.                                                       |
| View/Edit  | Full access to add, edit, test, and save VirusTotal API key configurations.                | <ul><li>Threat Hunter: Configure and use TI feeds</li><li>Security Engineer: Configure TI feed integrations.</li></ul> |

#### Required and recommended permissions

Managing threat intelligence effectively requires access to the modules that consume this data. Consider adding the following permissions:

| Permission          | Permission Level | Reason                                                                                                     |
| ------------------- | ---------------- | ---------------------------------------------------------------------------------------------------------- |
| Threat Intelligence | View/Edit        | Strongly recommended to access the Threat Intel module to manage indicators and IOCs that consume TI data. |
| Detection Rules     | View/Edit        | Strongly recommended to manage IOC and BIOC detection rules that leverage threat intelligence feeds.       |
| Integrations        | View             | Recommended to view integration instances that ingest threat intelligence data.                            |
| Credentials         | View             | Recommended to view credentials used by TI feed integrations.                                              |
| Query Center        | View             | Recommended to query threat intelligence data via XQL for hunting and analysis.                            |


---

# 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/configuration-permissions/threat-intelligence-permission-api-configuration.md?ask=<question>&goal=<endgoal>
```

`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.
