> 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/long-running-http-integrations-configuration.md).

# Long-running HTTP Integrations configuration

Manage access to Cortex XSIAM long-running HTTP integration configuration.

Governs the backend service that hosts and serves dynamic content to external security devices, such as Palo Alto Networks firewalls. It allows administrators to enable or disable the EDL service and manage its global settings. Access this through Settings → Configurations → Integrations → External Dynamic List Integration.

This permission is used by administrators to set up and maintain the EDL service infrastructure.

EDL (under Investigation & Response permissions): Used by analysts to add or remove specific IP addresses and domains to lists during active investigations.

| Permission | Description                                                                                                | Role Example                                                                                                            |
| ---------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| None       | The External Dynamic List Integration page is hidden.                                                      | <ul><li>SOC Tier-1 and 2 Analysts: No configuration needed.</li></ul>                                                   |
| View       | Users can view existing EDL configurations and service status, but cannot make changes.                    | <ul><li>SOC Tier-3 Analyst: Understand EDL configurations.</li></ul>                                                    |
| View/Edit  | Full control over the EDL service, including enabling/disabling the service and modifying global settings. | <ul><li>Threat Hunter: Understand data flows.</li><li>Security Engineer: Develop and manage API integrations.</li></ul> |

Required and recommended permissions

As the EDL service is used for response actions, consider these dependencies:

| Permission                                    | Permission Level                                        | Reason                                                                                                                                                  |
| --------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| EDL                                           | View or View/Edit                                       | Strongly recommended to use EDL as a response action. Add IPs/domains to EDL from Action Center, Causality View, Issue View, XQL queries, and playbook. |
| Threat Intelligence (under Threat Management) | View                                                    | Strongly recommended to view threat indicators that populate EDL content.                                                                               |
| Playbooks                                     | Enabled plus Edit Public Playbooks and Create Playbooks | Recommended to view/manage playbooks that trigger EDL actions.                                                                                          |
| Integrations                                  | View                                                    | Recommended to view integration instances that consume EDL data.                                                                                        |
| Broker Service                                | View                                                    | Recommended if EDL is served through a Broker VM.                                                                                                       |


---

# 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/reference-and-developer-docs/role-based-access-control/configuration-permissions/long-running-http-integrations-configuration.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.