> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/generic-on-premise-data-collectors/broker-vm-data-collector-applets/activate-registry-scanner.md). # Activate Registry Scanner The Broker VM provides a Registry Scanner applet that scans and secures your container image registries. It supports Docker V2 or JFrog self-hosted registries located on-premises or in private cloud networks. {% hint style="info" %} **Note** * You cannot activate the Registry Scanner directly on a new or existing Broker VM. You can only activate or deactivate existing Registry Scanner applets. To activate or deactivate existing applets, see Step 4 under Verify Registry Scanner connection section. {% endhint %} ### Verify Registry Scanner connection After the registry scanner is initialized, perform the following steps to verify that the **Registry Scanner** applet is connected to the **Broker VM**: {% hint style="warning" %} **Prerequisite** * To initialize registry scanning on your Broker VM, you must first add the necessary data connectors. For details, see: * [Connect Docker Hub registry](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-docker-hub-registry.md) * [Connect Docker V2 compliant container registry](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-docker-v2-compliant-container-registry.md) * [Connect GitLab container registry](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-gitlab-container-registry.md) * [Connect Harbor registry](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-harbor-registry.md) * [Connect JFrog container registry](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-jfrog-container-registry.md) * [Connect Sonatype Nexus registry](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-sonatype-nexus-registry.md) * When sizing your Broker VM, consider the following recommendations: * **Disk Size:** Calculate the required disk space by multiplying the average container image size in your environment by 10. This factor accounts for simultaneous operations with a buffer. For example, If your average image size is 500 MB, allocate at least 5 GB of disk space (500 MB \* 10 = 5000 MB = 5 GB). * **CPU:** Allocate a minimum of 8 CPU cores. * **Memory:** Allocate a minimum of 16 GB of RAM. {% endhint %} 1. Go to **Settings** → **Configurations** → **Data Broker** → **Broker VMs**. 2. On either the **Brokers** or **Clusters tab**, find the Broker VM. 3. In the **APPS** column for the **Broker VM**, verify that the **Registry Scanner** app appears. 4. Select the **Registry Scanner** app to open a window displaying the following information: * **Connection**: Shows the app's current connection status. You can also **Deactivate** the app.To reactivate the **Registry Scanner** app, do one of the following: * On the **Brokers** tab, locate the Broker VM, select **+Add** in the **APPS** column, and then choose **Registry Scanner**. * On the **Clusters** tab, locate the Broker VM, select **+Add** in the **APPS** column, and then choose **Registry Scanner**. If the **Registry Scanner** app is not listed in the drop-down menu when you click **+Add**, it means that the registry scanning was not configured for that **Broker VM**. You must first add the data connectors. * **Resources**: Shows the percentage of **CPU**, **Memory**, and **Disk** resources used by the app.
5. To manage the Registry Scanner applet, see: * [Manage a Docker Hub connector](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-docker-hub-registry/manage-a-docker-hub-connector.md) * [Manage a Docker V2 connector](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-docker-v2-compliant-container-registry/manage-a-docker-v2-connector.md) * [Manage a Gitlab Container Registry connector](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-gitlab-container-registry/manage-a-gitlab-container-registry-connector.md) * [Manage a Harbor connector](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-harbor-registry/manage-a-harbor-connector.md) * [Manage a JFrog connector](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-jfrog-container-registry/manage-a-jfrog-connector.md) * [Manage a Sonatype connector](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-sonatype-nexus-registry/manage-a-sonatype-connector.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/generic-on-premise-data-collectors/broker-vm-data-collector-applets/activate-registry-scanner.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.