> 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/configure-cortex-xsiam/engines/engine-requirements.md).

# Engine requirements

Review Cortex XSIAM engine hardware, operating system, network, and required URLs.

You can install engines on all Linux environments. Docker/Podman needs to be installed before installing an engine. If you are using the shell installer for an engine, Docker/Podman is installed automatically.

{% hint style="info" %}
The Cron package is required to install engines on a Linux machine.
{% endhint %}

### **Engine hardware requirements**

If your hard drive is partitioned, we recommend a minimum of 50 GB for the `/var` partition.

| Component        | Dev Environment Minimum | Production Minimum |
| ---------------- | ----------------------- | ------------------ |
| CPU              | 8 CPU cores             | 16 CPU cores       |
| CPU architecture | x86\_64 only            | x86\_64 only       |
| Memory           | 16 GB RAM               | 32 GB RAM          |
| Storage          | 100 GB                  | 100 GB             |

### **Operating system requirements**

You can deploy a Cortex XSIAM engine on the following operating systems:

| Operating System | Supported Versions                                       |
| ---------------- | -------------------------------------------------------- |
| Ubuntu           | 18.04, 20.04, 22.04, 24.04, 26.x                         |
| RHEL             | <p>8.x, 9.x, 10.x</p><p>Includes all minor versions.</p> |
| Oracle Linux     | 7.x, 8.9, 9.3, 9.4, 10.1                                 |
| Amazon Linux     | 2, Amazon Linux 2023                                     |
| Rocky Linux      | 9.5, 9.6                                                 |

{% hint style="info" %}
CentOS 8.x reached End of Life (EOL) on December 31, 2021, and is no longer supported as an operating system.

CentOS 7.x reached End of Life (EOL) on June 30, 2024, and is no longer supported as an operating system.
{% endhint %}

### **Engine required URLs**

You need to allow the following in the URLs for Cortex XSIAM engines to operate properly. The URLs are needed to pull container images from public Docker registries.

The endpoint URL is: `wss://api-<tenant domain>.xdr.<region>.paloaltonetworks.com/xsoar/d1ws`. For example, `wss://api-my-tenant.xdr.us.paloaltonetworks.com/xsoar/d1ws`

{% hint style="info" %}
If you have configured a range of **Approved IP Ranges** under **Allowed Sessions** on the **Security Settings** page, the engine must communicate through one of the approved IPs.
{% endhint %}

| FUNCTION            | SERVICE                                                                                                                                                                                                                                                                                                                                                                                                           | PORT                       | DIRECTION |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------- | --------- |
| Integrations        |                                                                                                                                                                                                                                                                                                                                                                                                                   | Integration-specific ports | Outbound  |
| Engine connectivity | HTTPS                                                                                                                                                                                                                                                                                                                                                                                                             | 443 (configurable)         | Outbound  |
| Docker              | <ul><li><https://registry-1.docker.io></li><li><https://registry.fedoraproject.org></li><li><https://registry.access.redhat.com></li><li><https://docker.io></li><li><https://registry.docker.io></li><li><p><https://auth.docker.io></p><p>This URL may change at Docker’s discretion.</p></li><li><p><https://production.cloudflare.docker.com></p><p>This URL may change at Docker’s discretion.</p></li></ul> | 443                        | Outbound  |


---

# 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/configure-cortex-xsiam/engines/engine-requirements.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.