Configure a Remote Repository on the Production Machine - Administrator Guide - 6.10 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR Administrator Guide

Product
Cortex XSOAR
Version
6.10
Creation date
2022-10-13
Last date published
2023-12-06
Category
Administrator Guide

To work with the remote repositories, you must have at least two machines, one for your development environment and the other for your production environment.

Prerequisites

Before configuring the remote repository, review the following list of prerequisites:

  • Verify that the content that you want already exists in the remote repository. You cannot edit content in the production environment. All of the content is fully synchronized with the remote repository.

    Note

    Any content that exists in the production environment, but not on the remote repository, will be deleted

  • When working with remote repositories and upgrading to v6.0, you must make sure to pull your classifiers and mappers from the dev environment before upgrading your production environment.

  1. Add the Content Repository tab to Cortex XSOAR.

    1. Select SettingsABOUTTroubleshootingAdd Server Configuration.

    2. Add the following key and value.

      Key

      Value

      ui.version.control.show.remote

      true

    3. Click Save.

  2. Define the repository.

    1. Navigate to SettingsAdvancedContent Repository.

    2. Click the On/Off slider to enable the remote repositories.

    3. Define the machine as the production environment.

    4. In the Repository URL field, enter the URL. Cortex XSOAR automatically identifies if the URL is for HTTP, HTTPS, or SSH.

      For GitHub users - GitHub provides personal access tokens instead of usernames and passwords. Enter the GitHub token in the password field and leave the username field blank.

      For some repository vendors that use tokens, the token type is entered in the username field and the token is entered in the password field. Verify details with your vendor.

      Note

      If you are using a passphrase, only RSA private keys are supported.

      If your SSH connection uses a port other than port 22 (the default SSH port), you must include the ssh string and port number in the url. In the following example, we use port 20017:

      ssh://git@content.demisto.com:20017/~/my-project.git

    5. Select the active branch from which you pull content.

    6. Click Save.

      In the Discard server changes screen, you are presented with content that exists in your production environment, but does not exist on the remote repository. This includes integrations, and their instances and classifiers.

      remote-discard-server.png
    7. Type Discard in the relevant field and click Continue. All of the content that appears in this screen is discarded and permanently deleted.

      Content from the remote repository is installed. This can take several minutes depending on the amount of content in the remote repository and your hardware configuration. In addition, your custom content is automatically backed up to the Cortex XSOAR server any time you change one of the remote repository settings. The backup is located under /var/lib/demisto/backups/content-backup-*.tar.gz.

  3. Pull Content from the Remote Repository

    Once you push content from the development machine to the remote repository, it is available as an update for the production environment.

    1. Check for updates.

    2. Click Install Content.