> 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/registry-scanning.md). # Registry scanning Learn about Registry scanning capability in Cortex Cloud Registry scanning identifies security and compliance risks in container images before you deploy them to runtime environments. It is a foundational component of Cloud Workload Protection (CWP) and container supply chain security. A container registry stores and distributes container images. Cortex Cloud supports scanning images in managed cloud registries and third-party registry providers. For more information, see Supported container registry integrations. After you configure registry scanning, Cortex Cloud automatically scans images for the following: * **Vulnerabilities:** Vulnerabilities in operating system packages, such as Debian, RHEL, and Alpine, and application dependencies, such as Python, Node.js, Java, and Go. * **Malware:** Malware in container images, including binaries and scripts, using WildFire threat intelligence. * **Exposed secrets:** API keys, private keys, credentials, tokens, and other secrets embedded in image layers. * **Software bill of materials (SBOM):** Packages, libraries, binaries, and licenses identified across image layers. * **Compliance violations:** Image configuration and base image issues evaluated against CIS benchmarks, organizational compliance policies, and security best practices. --- # 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/registry-scanning.md?ask=&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.