Set up a Private Remote Repository - Administrator Guide - 8 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR Administrator Guide

Cortex XSOAR
Creation date
Last date published
Administrator Guide

Set up the private content repository feature.

Before you begin, verify that you have network connectivity from Cortex XSOAR to the private remote repository. All communication goes through Cortex XSOAR, so it must have access to the remote repository. If direct access from Cortex XSOAR is not enabled you can use engines with access to the repository.

The following are typical scenarios for setting up a private remote repository for the production and one or more development tenants.

New Development Tenant and New or Existing Production Tenant

In this scenario, the production tenant is first activated as a standalone (by default), and the private remote repository is then enabled in the production tenant. Once enabled, the first development tenant becomes the push tenant and the production tenant and any additional tenants become pull tenants.

  1. Activate any additional development tenants by repeating Step 2.

  2. Enable the private remote repository in each additional development tenant by repeating Step 4. They will automatically be set to pull.

Existing Development and Production Tenants

In this scenario, the production and development tenants were managed in parallel with different sets of content. Since they were already activated in Cortex Gateway, their content repository settings can only be changed within the tenants.


The first tenant that is enabled pushes its content to the remote repository first. For example, these instructions describe enabling the production tenant first, so the remote repository will initially contain production tenant content. You can enable a development tenant first if you want the remote repository to initially contain the content from the development tenant.