> 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/supported-container-registry-integrations.md).

# Supported container registry integrations

Learn about supported container registry integrations in Cortex XSIAM

Container Registry scanning supports both managed cloud registries and third-party registry integrations, allowing you to monitor container images across various environments.

**Managed Cloud Registries**

The container registry scanner automatically detects and scans container registries and images within your onboarded cloud accounts. Supported registries include:

* Amazon Elastic Container Registry (ECR)
* Azure Container Registry (ACR)
* Google Artifact Registry (GAR)
* Oracle Cloud Infrastructure (OCI) Artifact Registry

For more details, see [configure registry scanning for cloud accounts](/cortex-xsiam/cloud-security/container-registry-scanning/configure-registry-scanning-for-cloud-accounts.md).

**Third-Party Integrations**

The container registry scanner supports agentless scanning of container images by direct integration with various third-party registries, independent of the cloud account onboarding process. These integrations include a streamlined, user-friendly connector configuration experience for the following:

* [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)
* [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)

Cortex XSIAM also scans images in the Red Hat OpenShift integrated container registry. Because this registry runs inside your cluster, scans are performed in-cluster through the Kubernetes connector. For more details, see [OpenShift container registry](/kubernetes-security/onboard-the-kubernetes-connector/openshift-container-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/supported-container-registry-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.