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 the Cortex Gateway, you set up a development tenant from the Main Tenant, which manages content. When the content is ready, you can push the content to the Main Tenant (production tenant).
Note
You can enable this feature only on the Main Tenant. It is not available for child tenants.
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 the Marketplace. The Marketplace is managed only on the development tenant.
In the Cortex Gateway, you need to create a Cortex XSOAR development tenant from your Cortex XSOAR Main Tenant. All content from your Main Tenant (production tenant) is copied to the development tenant. You can use a built-in or private remote repository
Considerations
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.
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.
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.
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.
Set up the remote repository
To set up a built-in remote repository, see Set up a built-in remote repository.
To set up a private repository, see Set up a private remote repository.
To learn more about remote repositories, requirements, and configuration, see Content management in Cortex XSOAR.
Note
The development tenant cannot be converted to a production tenant. If you turn off the feature in the production tenant, the development tenant becomes inactive.