Install Cortex XSOAR with Bolt Database

Install Cortex XSOAR 6.14 on a single server with the Bolt 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 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

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

By default, Cortex XSOAR is installed in the /root folder, but you can Move Data Folders to Another Location on the Server, if necessary.

Asset	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 (dependent 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.
• 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.

  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.
• You have the following roles assigned:

  Role	Details
  CSP role	The Super User role is assigned to your Customer Support Portal account. The user who creates the account receives this role.
  Cortex role	You must have the Account Admin role. The first Customer Support Portal Super User to access Cortex Gateway receives Account Admin permissions automatically.

  Log in to Cortex Gateway after creating the account. Download the image file and license. Repeat these tasks for each tenant.

  You need a license, or a sales-provided evaluation license, assigned to your Customer Support Portal account to download Cortex XSOAR images from Cortex Gateway.
• Your installation meets the system requirements.
• You have root access.
• Docker is installed automatically unless you are installing on Oracle Linux, which requires manual installation.

Install Cortex XSOAR with Bolt Database

1

Download the installation package and license

1. Log in to Cortex Gateway.
2. Locate the activation card for your license. By default, the Production-Standalone license is selected. You can also select Dev. If you want to use a production and a development tenant with a private remote repository, select Dev. If you don't select it now, you can install a development tenant later.
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. Then select Download.

In Google Chrome, to download the image and license files together, you may need to set Settings → Privacy and security → Site settings → Additional permissions → Automatic downloads to Sites can ask to automatically download multiple files.

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

Copy the download link button from your browser's Downloads section to get the offline-installation token.

1. (Optional) If you are deploying Cortex XSOAR using a signed installer (GPG), you need to import the GPG public key provided with the signed installer. Open a ticket with Palo Alto Networks support to get the public key (see here). For example, you can use the rpm --import public.key command to import the public key into the local GPG keyring. Note that each operating system has specific requirements.
2. (Optional) If you are deploying Cortex XSOAR using a signed installer (GPG) you might need to manually install the makeself package by running the yum install makeself command.

2

Make the server package executable

Run the following command to make the package executable. Replace demisto.sh with your installer filename if needed.

chmod +x demisto.sh

3

Run the installer

1. Execute the .sh file by running the following command:

   sudo ./demisto.sh

   Add Installer Flags as required.
2. Accept the EULA and add the information when prompted.
3. The Server HTTPS port (default is 443)
4. If you are using Elasticsearch, enter the Elasticsearch details, such as the URL, timeout, etc.
5. Type the Admin username (default is admin).
6. Type the password (default is admin).

4

Verify the installation

(Optional) After the installation has completed, do the following:

1. Confirm that the Cortex XSOAR server status is active by running the systemctl status demisto command.

   If the server is not active, run the systemctl start demisto command to start the server.
2. Confirm that the Docker service status is active by running the systemctl status docker command.
3. In a web browser, go to the https://serverURL:port to verify that Cortex XSOAR was successfully installed.

   When you open Cortex XSOAR for the first time, add the license.

5

Add the license

After the installation is complete, activate the license.

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

Troubleshoot Cortex XSOAR installation

In some cases, due to moving previous installation files, the installation can fail, and the following error message is displayed:

mv: cannot stat '/var/lib/dpkg/info/demistoserver.postrm': No such file or directory
Failed to execute: 'mv': exit status 1

There are two options to resolve this issue:

• Make a note of the path to the demistoserver.postrm file. Rerun the installation using this path for the -- -prev-uninstall-script flag. Example: -- -prev-uninstall-script="/path/to/demistoserver.postrm"
• Rerun the installation with the flag -- -use-prev-uninstall-script=true. Note that if you use this flag and have previously created a special ID & group for demisto users, the demisto user and group are deleted and recreated during installation.