Overview of how remote repositories work and how to configure a remote repository in Cortex XSOAR for a multi-tenant deployment.
In Cortex XSOAR you can use a content management system with a built-in or private content repository (Git-based, including GitHub, GitLab, and Bitbucket) to develop and test content. In Cortex Gateway, you activate a development tenant from the main tenant, which manages content. All content from your main tenant (production tenant) is copied to the development tenant. When the content is ready, you can push the content to the Main Tenant (production tenant).
Note
Although you can have multiple development tenants, only one development tenant can push to the production tenant.
Development tenants can only be activated from the main tenant. They are not available for child tenants. Child tenants receive content from the main tenant and have no connection to a development tenant.
In your main tenant, you pull the content as you would all other content updates, and push content to your child tenants using selective propagation. For more information, see Content management in multi-tenant.
All content is managed by the development tenant, including custom content and content updates from Marketplace. Marketplace is managed only by the development tenant.
Before you begin
If you are changing your remote repository settings, back up existing content to your local computer by navigating to → → → → and click Export all custom content.
You must have Instance Administrator or Account Admin permission.
Activate your development tenant. For more information, see step 8 in Activate Cortex XSOAR (Main Tenant).
Set up the remote repository
You can set up one of the following repositories:
Built-in remote repository
You need to activate the development tenant in Cortex Gateway and enable the built-in repository in the production tenant.
When you activate a tenant and enable the content repository in Cortex Gateway, Cortex XSOAR by default uses the built-in repository. The built-in remote repository requires fewer configurations than using a private remote repository and cannot be accessed directly. If you want to use a private remote repository, you need to configure it when you enable the remote repository in the tenant.
For a simple one-branch deployment, we recommend using the built-in repository. If you want to use multiple branches, or if you need access to the content repository outside the Cortex XSOAR platform (for example to implement some scanners) you must use a private repository.
For more information, see Set up a built-in remote repository.
Private repository
You need to activate the development tenant in Cortex Gateway and enable the built-in repository in the production and development tenants.
If you want to use a private remote repository with one or more branches, you need to enable the remote repository in each tenant and then set up all branches in the remote repository configuration page in Cortex XSOAR.
For more information, see Set up a private remote repository.
If the content repository option is disabled for the production or development tenant, the tenant becomes standalone and does not push or pull content.
Activation may take some time. You should receive notification by email that the production or development tenant has completed the activation process.
Once the activation completes, you can only change content repository settings within the tenant.