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
By default, when you activate the Cortex XSOAR tenant, it is a standalone tenant. To set up the remote repository, you need to enable the content repository in the production tenant (as a pull tenant) and activate the development tenant.
Note
It doesn't matter if you activate a new development tenant in Cortex Gateway before enabling the content repository 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.
Perform the following procedures in the order listed below.
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.
Note
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.
Perform the following procedures in the order listed below.