> 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-xsoar-8-on-prem/8.7/onboard-cortex-xsoar/cortex-xsoar-installation/system-requirements/hardware-requirements.md).

# Hardware requirements

The Cortex XSOAR tenant has specific minimum VM hardware requirements depending on the scale.

{% hint style="info" %}

### Important

A hypervisor host running VMs must have enough hardware resources to support all Cortex XSOAR VMs you plan to run on.

Each VM (node) in a cluster must have the same resources. For example, a 3 VM cluster planned to run on a host must have at least 3 times the listed specs for memory, CPU cores, and storage. Leave additional space for overhead virtualization operations.

To fully leverage High Availability, deploy each VM on a different hypervisor. This ensures that the other VMs continue to operate if one hypervisor fails.
{% endhint %}

The following requirements apply for a single node (standalone), or for each node in a cluster.

| Component                                                                                                                                                                                                                                                                                                                                                                                                                           | Small scale                                                                  | Medium scale                                                                                  | Large scale                                                                                   |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| CPU per VM                                                                                                                                                                                                                                                                                                                                                                                                                          | 16 CPU cores                                                                 | 32 CPU cores                                                                                  | 48 CPU cores                                                                                  |
| Memory per VM                                                                                                                                                                                                                                                                                                                                                                                                                       | 64 GB RAM                                                                    | 128 GB RAM                                                                                    | 192 GB RAM                                                                                    |
| Storage per VM                                                                                                                                                                                                                                                                                                                                                                                                                      | 256 GB boot disk plus a separate 775 GB data disk. These disks must be SSDs. | 256 GB boot disk plus a separate 1.3 TB data disk (1 TB = 1024 GB). These disks must be SSDs. | 256 GB boot disk plus a separate 1.8 TB data disk (1 TB = 1024 GB). These disks must be SSDs. |
| <p>Performance benchmark running the Phishing playbook</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>The performance benchmark indicates how many playbook runs per hour can be supported.</p><p>The benchmark values provided are for a single node running the Phishing playbook. This value can vary according to playbook size and complexity.</p></div> | Up to 200 playbook runs per hour                                             | 200 - 400 playbook runs per hour                                                              | Up to 650 playbook runs per hour                                                              |

\*1 TB = 1024 GB


---

# 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-xsoar-8-on-prem/8.7/onboard-cortex-xsoar/cortex-xsoar-installation/system-requirements/hardware-requirements.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.