> 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-posture-management/cortex-cloud-data-sources-and-connectors/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-docker-hub-registry.md). # Connect Docker Hub registry The Docker Hub registry data source allows you to connect your public or private Docker Hub account to scan and secure container images against vulnerabilities, malware, and exposed secrets. ### How to connect Docker Hub registry Follow the wizard to connect your Docker Hub registry with Cortex Cloud. 1. Navigate to **Settings** → **Data Sources & Integrations** and click **+ Add New**. 2. On the **Add Data Sources or Integrations** page, search for **Docker Hub**, then hover over it and click **Add**. 3. The **Instance Name** is automatically populated. You can change it to a more meaningful name. 4. Choose the **Scan Mode**, and then follow the steps for that mode to configure the connection.
Cloud Scan Security scanning is performed in the Cortex Cloud environment when you select this mode. 1. Select the appropriate **Cloud Provider** and **Region** for the Cortex Cloud environment to use for registry scanning. As a best practice, choose the region closest to your registry deployment to achieve the best scanning throughput and potentially reduce cloud costs. 2. (Optional) Enable **Allow access by IPs** to specify a static IP address for the scanner to use. Make sure the static IP is allowed through your firewall so the scanner can access the registry during the scanning process. 3. Choose the relevant **Repository Access** for scanning: 1. **Authenticated access**: Discover and scan private and public repositories within the given account. 1. Under **Authentication Method**, enter your private Docker Hub account credentials (**Username** and **Password**) for authentication. 2. **Public access only**: Discover and scan images within a specific public repository. 1. Enter your public Docker Hub **Repository Name**. To specify an official Docker Hub repository, enter `library/`, followed by the short string used to designate the repo. For example, to scan the images in the official Alpine Linux repository, enter `library/alpine`. 2. Under **Authentication Method**, enter your public Docker Hub account user credentials (**Username** and **Password**) for authentication. 4. Select **Next**.
Scan with Outpost Security scanning is performed on infrastructure deployed to a cloud account that you own. This mode requires additional cloud provider permissions and may incur extra costs. {% hint style="warning" %} #### Prerequisite Ensure an [Outpost](/cortex-cloud-posture-management/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/outpost-onboarding.md) is connected to your tenant. {% endhint %} 1. Choose a **Cloud Provider** to initialize registry scanning.

Note

If you choose Azure as the Cloud Provider, you must also select the Tenant Id. The Tenant Id is required to approve Cortex as an enterprise application in your Azure tenant.

2. **Choose Outpost** account to use for this instance. If no **Outposts** are shown, you can **Create a new one**. For more details, see [Outposts](/cortex-cloud-posture-management/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/outpost-onboarding/outpost-creation-workflow.md#phase-2-creating-the-outpost).

Note

If you choose Azure as the cloud provider, only Outposts associated with the selected tenant ID are displayed.

3. Select the **Region** where the registry is hosted. 4. (Optional) Enable **Allow access by IPs** if you want to specify a static IP address for the scanner to use. Make sure the static IP is allowed through your firewall so that the scanner can access the registry during the scanning process. 5. Choose the relevant **Repository Access** for scanning: 1. **Authenticated access**: Discover and scan private and public repositories within the given account. 1. Under **Authentication Method**, enter your private Docker Hub account credentials (**Username** and **Password**) for authentication. 2. **Public access only**: Discover and scan images within a specific public repository. 1. Enter your public Docker Hub **Repository Name**. To specify an official Docker Hub repository, enter `library/`, followed by the short string used to designate the repo. For example, to scan the images in the official Alpine Linux repository, enter `library/alpine`. 2. Under **Authentication Method**, enter your public Docker Hub account user credentials (**Username** and **Password**) for authentication. 6. Select **Next**.
Scan with Broker VM Security scanning in private networks is done using broker VM infrastructure when you select this mode. {% hint style="warning" %} #### Prerequisite * [Set up and configure Broker VM](/cortex-cloud-posture-management/data-management/broker-vm/set-up-and-configure-broker-vm.md) * [Configure High Availability Cluster](/cortex-cloud-posture-management/data-management/broker-vm/broker-vm-high-availability-cluster/configure-high-availability-cluster.md) {% endhint %} 1. Choose a **Scan with Broker VM mode** to initiate registry scanning. You can select either a standalone **Broker VM** or a High Availability (HA) **Cluster**. 2. Select **Applicable Broker VMs**. Choose the appropriate **Broker VM** or **Cluster** from the list configured in your tenant. * The list of Broker VMs displays only VMs that support registry scanning. * The list of high-availability Clusters displays only clusters that contain at least one VM supporting registry scanning. * The registry scanning status for each VM appears in brackets if it was previously activated for that specific VM. If the list does not display any Broker VMs or Clusters, Add New Broker VM or Add New Cluster. For more details, see [Set up and configure Broker VM](/cortex-cloud-posture-management/data-management/broker-vm/set-up-and-configure-broker-vm.md). 3. Choose the relevant **Repository Access** for scanning: 1. **Authenticated access**: Discover and scan private and public repositories within the given account. 1. Under **Authentication Method**, enter your private Docker Hub account credentials (**Username** and **Password**) for authentication. 2. **Public access only**: Discover and scan images within a specific public repository. 1. Enter your public Docker Hub **Repository Name**. To specify an official Docker Hub repository, enter `library/`, followed by the short string used to designate the repo. For example, to scan the images in the official Alpine Linux repository, enter `library/alpine`. 2. Under **Authentication Method**, enter your public Docker Hub account user credentials (**Username** and **Password**) for authentication. 4. Select **Next**.
5. In **Initial Scan Configuration**, set your scanning process to focus on recently added or modified container images and exclude older ones that do not align with your current scanning objectives. This setting helps avoid unnecessary scans. Choose one of the following options: * **All**: Scans all container images, including all versions (tags), in all discovered repositories. * **Latest Tag**: Scans only images tagged '**latest**' in all discovered repositories. * **Days Modified**: Scans container images created or modified in the last few days. You can select a range of up to **90** days for the scan. 6. Select **Save**. When the **Docker Hub** data source is saved, a new data connector is created, and the initial discovery scan begins. The connection process may take up to 15 minutes. 7. To check the connector status and scan results, follow these steps: 1. Navigate to **Settings** → **Data Sources & Integrations**. 2. Find the **Docker Hub** instance from the list of **3rd Party Data Sources** connectors, or use **Search**. 3. In the **Docker Hub** instance row, select **View Details**. The **Docker Hub Instances** page appears. 4. On the **Docker Hub Instances** page, you can filter results by any heading and value. 5. Select an **Instance Name** to open the details pane. The details pane contains the following granular information:
Instance DetailsDescription
StatusShows the status of the connector: Connected, Error, Warning, Disabled, or Pending.
Applet Status on Broker VMShows the status of the Registry Scanner applet on the Broker VM page. This status is visible only when the Scan with Broker VM mode is selected.
RepositoriesShows the number of scanned repositories in the registry.
Scan ModeShows the selected scan mode for the data connector, such as Cloud Scan, Scan with Outpost, or Scan with Broker VM.
Security CapabilitiesShows a breakdown of the security capabilities enabled on the instance and their individual statuses. For example, select Registry Scanning when it shows a warning or error status to see the open errors and issues that contributed to the status.
8. After the scan is complete, you can view the scanned images on the **Container Images Inventory** page. For more details, see [Container Image assets](/cortex-cloud-posture-management/cloud-inventory-and-environment/asset-classes/compute-assets/container-image-assets.md). If you have selected the **Scan with Broker VM** option, then a **Registry Scanner** applet is created on the selected **Broker VM** or **Cluster**. For details, see [Verify Registry Scanner connection](/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/generic-on-premise-data-collectors/broker-vm-data-collector-applets/activate-registry-scanner.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-posture-management/cortex-cloud-data-sources-and-connectors/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/connect-docker-hub-registry.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.