> 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-6-multi-tenant-guides/6.15/onboard-multi-tenant/multi-tenant-deployment-installation/install-cortex-xsoar-for-a-multi-tenant-deployment.md).

# Install Cortex XSOAR for a Multi-Tenant Deployment

Install Cortex XSOAR 6.15 for a multi-tenant deployment using the BoltDB database.

In a standard Cortex XSOAR deployment, the app server and database server are installed on the same machine.

If you are deploying a signed installer:

* You need to import the public key into the operating system. Open a [ticket](https://support.paloaltonetworks.com/Support/Index) with Palo Alto Networks support to get the public key. It is valid for six months.
* If you are using engines or hosts in a multi-tenant environment, you need to install **`makeself`**.

### Cortex XSOAR installation file structure

This is the file and folder structure in a standard Cortex XSOAR installation.

By default, the .sh file is in `/home/<user-name>`. The .sh file installs the `demistoserver_xxxxx.amd64.deb` file in the `/usr/local/demisto` folder. You can [change the default folder](/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/manage-data/move-data-folders-to-another-location-on-the-server.md), if necessary.

The following files and folders are created during the multi-tenant installation.

| File/Folder   | Path                                                                           |
| ------------- | ------------------------------------------------------------------------------ |
| Binaries      | `/usr/local/demisto`                                                           |
| Data          | `/var/lib/demisto`                                                             |
| Logs          | `/var/log/demisto`                                                             |
| Configuration | `/etc/demisto.conf` (not created if defaults are selected during installation) |
| Reports       | `/tmp/demisto_install.log`                                                     |
| Install log   | `/tmp/demisto_install.log`                                                     |

If you want to create different mounts for the `/var/lib/demisto`, `/var/lib/docker`, and `/tmp` partitions, it is recommended to allocate the following space to each partition (depending on the expected amount of data and the size of your incidents and indicators).

* `/var/lib/demisto`: 200 GB (development), 1000 GB (production)

  If using Elasticsearch, see [Elasticsearch System Requirements](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/elasticsearch/elasticsearch-setup/elasticsearch-system-requirements.md).
* If using Docker: `/var/lib/docker`: 70 GB (development), 150 GB (production)
* If using Podman: `/home`:70 GB (development), 150 GB (production)
* `/tmp`: 10 GB (development and production)

### Prerequisites for installing Cortex XSOAR

Verify the following information and requirements before you install Cortex XSOAR.

* A Customer Support Portal (CSP) account.

  Set up your CSP account. For more information, see [How to Create Your CSP User Account](https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClNVCA0).

  When you create a CSP account, you can set up two-factor authentication (2FA) to log into the CSP by using an Email, Okta Verify, or Google Authenticator (non-FedRAMP accounts). For more information, see [How to Enable a Third Party IdP](https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000sZ8mCAE).
* Have the following roles assigned:

  | Role        | Details                                                                                                                                                                                                                                                               |
  | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | CSP role    | The Super User role is assigned to your CSP account. The user who creates the CSP account is granted the Super User role.                                                                                                                                             |
  | Cortex role | <p>You must have the Account Admin role.</p><p>If you are the first user to access Cortex Gateway with the CSP Super User role, you are automatically granted Account Admin permissions for the Cortex Gateway. You can also add Account Admin users as required.</p> |

After creating the CSP account, log in to the Cortex Gateway to download the relevant image file and license. Downloading an image file from Cortex Gateway ensures you have the latest pre-configured software package for easy deployment and updates.

If you have multiple or development tenants, you must repeat these tasks for each tenant.

{% hint style="info" %}
To download the Cortex XSOAR images from Cortex Gateway, you need a license (or evaluation license through sales) assigned to your CSP account.
{% endhint %}

* Review the [System Requirements](/xsoar-6-administrator-guide/6.15/onboard-cortex-xsoar/single-server-deployment/system-requirements.md).
* Have root access.

### Install Cortex XSOAR for a multi-tenant deployment

{% stepper %}
{% step %}

#### Download the installation package and license

1. Log in to [Cortex Gateway](https://cortex-gateway.paloaltonetworks.com/accounts).
2. Locate the activation card for your license.
3. Select **Download On Prem**.
4. Select **Next**.
5. Under **Choose Download Option**, select **Installer**.
6. Select the checkbox to agree to the license terms and conditions.
7. Select **Download**.

Two files download: the `demistoserver-xxxxx.sh` installer file and a zipped JSON license file.

{% hint style="info" %}
In Google Chrome, configure **Settings** → **Privacy and security** → **Site settings** → **Additional permissions** → **Automatic downloads** to allow sites to request multiple downloads.
{% endhint %}

8. If you deploy Cortex XSOAR with a signed installer (GPG), import the GPG public key provided with the installer. Open a ticket with Palo Alto Networks support to get the public key.
9. If you deploy Cortex XSOAR with a signed installer (GPG), install `makeself` if required. For example, run `yum install makeself`.
   {% endstep %}

{% step %}

#### Make the server package executable

Run the following command:

`chmod +x demisto.sh`
{% endstep %}

{% step %}

#### Run the installer

1. Run the following command:

   `./demisto.sh -- -multi-tenant`\
   Add the [installer flags](/cortex-xsoar-6-multi-tenant-guides/6.15/onboard-multi-tenant/multi-tenant-deployment-installation/install-cortex-xsoar-for-a-multi-tenant-deployment/installer-flags.md), as required.
2. Accept the EULA and provide the requested information.
3. Enter the server HTTPS port. The default port is `443`.
4. Enter the admin username. The default username is `admin`.
5. Enter the admin password.
   {% endstep %}

{% step %}

#### Verify the installation

1. Confirm that the Cortex XSOAR server is active:

   `systemctl status demisto`

   If the server is not active, run `systemctl start demisto`.
2. Confirm that Docker is active:

   `systemctl status docker`
3. Open `https://<serverURL>:<port>` in a web browser.

The Cortex XSOAR sign-in page appears.
{% endstep %}

{% step %}

#### Add the license

1. Log in to the Cortex XSOAR server.
2. Upload the license file that you downloaded from Cortex Gateway.

For more information, see Add a license.
{% endstep %}
{% endstepper %}


---

# 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-xsoar-6-multi-tenant-guides/6.15/onboard-multi-tenant/multi-tenant-deployment-installation/install-cortex-xsoar-for-a-multi-tenant-deployment.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.