> 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-5.x/reference-and-developer-docs/role-based-access-control/investigation-and-response-permissions/response-permissions-1/edl-permissions.md).

# EDL permissions

Configure permissions for external dynamic lists.

EDL (External Dynamic List) enables security teams to:

* Add IP Addresses and Domains to Dynamic Lists - Create lists of malicious or suspicious IPs/domains
* Integrate with Palo Alto Networks Firewalls - EDL lists are automatically synced and enforceable on PANW firewalls.
* Block Malicious Traffic - Firewalls can use EDL to block traffic to/from listed entities
* Centralized Threat Response - Manage blocklists from a single location across your security infrastructure

For more information, see [Manage external dynamic lists](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/response-actions/manage-external-dynamic-lists.md).

{% hint style="info" %}

### Note

This permission is for analysts to use as a response action during case investigation. The Long Running HTTP Integrations configuration (under **Configurations**) is for administrators to set up and manage the EDL service infrastructure. For configuration details, see [Manage external dynamic lists](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/response-actions/manage-external-dynamic-lists.md).
{% endhint %}

| Permission | Description                                                                                                                                                    | Roles Example                                            |
| :--------: | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
|    None    | Nothing related to EDL, such as viewing EDL lists, adding entities to EDL, and accessing the EDL configuration.                                                |                                                          |
|  View/Edit | Add new IPs and domains to EDL entries in Action Center, Causality View, Issue View, XQL Queries, Threat Intel, and playbooks. Also removing entries from EDL. | All SOC Analysts, Threat Hunters, and Security Engineers |

**Required and recommended permissions**

Consider adding the following permissions:

| Permission     | Permission Level | Reason                                                                                                                                       |
| -------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Action Center  | View             | EDL is accessed through the Action Center. Required.                                                                                         |
| Cases & Issues | View             | Add to EDL/Remove from EDL appears in Case View and Causality View. Required.                                                                |
| Query Center   | View             | Add to the EDL context menu appears in the XQL Investigation results. Strongly recommended.                                                  |
| Threat Intel   | View             | Add to EDL appears in the IOC Rules context menu. Threat Intel view permission is needed to access the IOC Rules page. Strongly recommended. |


---

# 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-5.x/reference-and-developer-docs/role-based-access-control/investigation-and-response-permissions/response-permissions-1/edl-permissions.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.