> 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/registry-scanning/configure-registry-scanning-for-third-party-integrations.md).

# Configure registry scanning for third party integrations

Learn how to configure Cortex Cloud to scan container registries in third-party integrations

The container registry scanner supports agentless scanning of container images through direct integration with third-party registries. This integration is independent of the cloud account onboarding process.

{% hint style="warning" %}
**Limitation:** Registry scanning supports container images up to **80 GB** in size. Successful scanning of images larger than 80 GB is not guaranteed.
{% endhint %}

To add a container registry connector:

1. Go to **Settings > Data Sources & Integrations**.
2. Click **+ Add New**. The **Add Data Sources or Integrations** page opens.
3. In the search bar, enter the name of the data source, or click **Show More** and select **Container Registries**.
4. Select the connector you want to add.

For information about creating and managing container registry connectors, see:

* [Docker Hub](/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/docker/connect-docker-hub-registry.md)
* [Docker V2 compliant registries](broken://pages/WKdnoMzEXfgQOyssr0DU)
* [GitLab Container Registry](/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/gitlab/connect-gitlab-container-registry.md)
* [Harbor Registry](/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/harbor/connect-harbor-registry.md)
* [JFrog Container Registry](/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/jfrog/connect-jfrog-container-registry.md)
* ​[OpenShift container registry](/kubernetes-security/onboard-the-kubernetes-connector/openshift-container-registry.md)
* [Sonatype Nexus Repository Manager](/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/sonatype-nexus/connect-sonatype-nexus-registry.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/registry-scanning/configure-registry-scanning-for-third-party-integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.