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

# Configure registry scanning for third party integrations

Learn how to configure Cortex XSIAM 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-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/docker/connect-docker-hub-registry.md)
* [Docker V2 compliant registries](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/docker/connect-docker-v2-compliant-container-registry.md)
* [GitLab Container Registry](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/gitlab/connect-gitlab-container-registry.md)
* [Harbor Registry](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/harbor/connect-harbor-registry.md)
* [JFrog Container Registry](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/jfrog/connect-jfrog-container-registry.md)
* [OpenShift container registry](/kubernetes-security/onboard-the-kubernetes-connector/openshift-container-registry.md).
* [Sonatype Nexus Repository Manager](/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/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 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-xsiam/cloud-security/container-registry-scanning/configure-registry-scanning-for-third-party-integrations.md?ask=<question>&goal=<endgoal>
```

`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.