> 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-runtime-security/cortex-cloud-data-sources-and-connectors/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/configure-registry-scanning-for-cloud-accounts.md). # Configure registry scanning for cloud accounts Configuring registry scanning ensures that only verified and compliant images are deployed across your cloud environments. You can configure container registry scanning during the onboarding process for managed registries such as Amazon Elastic Container Registry (ECR), Azure Container Registry (ACR), Google Artifact Registry (GAR), and Oracle Cloud Infrastructure (OCI) Artifact Registry. If an account is already onboarded, you can modify its configuration to enable registry scanning as an **Additional Security Capability** to scan images for vulnerabilities, malware, and secrets. {% hint style="warning" %} ### Prerequisite: Ensure that you have performed all the steps till **Additional Security Capabilities** as listed in the onboarding wizard for the required CSP: * [Onboard Amazon Web Services](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/amazon-web-services-cloud-onboarding/how-to-onboard-amazon-web-services.md#configure-advanced-settings-optional) * [Onboard Google Cloud Platform](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/google-cloud-platform-cloud-onboarding/how-to-onboard-google-cloud-platform.md#configure-advanced-settings-optional) * [Onboard Microsoft Azure](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/microsoft-azure-cloud-onboarding/how-to-onboard-microsoft-azure.md#configure-advanced-settings-optional) * [Onboard Oracle Cloud Infrastructure](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/oracle-cloud-infrastructure-cloud-onboarding/how-to-onboard-oracle-cloud-infrastructure.md#configure-advanced-settings-optional) {% endhint %} To configure registry scanning, do the following: 1. Under **Additional Security Capabilities**, select **Registry Scanning**, then click **Edit Preferences**. ![enable-container-registry-scanning.png](/files/GIOeElUsE12gP0lG9flF) 2. 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 Tags**: 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. 3. When **Upload unknown files to WildFire** is enabled, eligible files detected during registry image scans are uploaded to WildFire for detonation analysis. This option expands malware detection by allowing WildFire to analyze new samples found in your registry images. When a detonation result returns a malicious verdict, the system re-evaluates the relevant registry image and creates a malware finding.

Notes

4. Select **Save**. After you configure your container registries, the system automatically starts a new scan. The connection process can take up to 15 minutes. To check the status of the data connector and view the registry scan results, go to the **Cloud Instances** page and select the relevant **Instance Name** from the list. 5. **Next Steps**. * After the scan completes, you can view the scanned images in the **Container Image** page. For more details, see [Container Image assets](/cortex-cloud-runtime-security/asset-managment/asset-classes/compute-assets/container-image-assets.md). * You can also modify your cloud instances to manage them effectively. For more details, see [Manage Cloud Instances](/cortex-cloud-runtime-security/onboard-and-configure/deployment-steps-and-checklist/cloud-service-provider-csp-onboarding/manage-cloud-instances.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-runtime-security/cortex-cloud-data-sources-and-connectors/cloud-posture-and-runtime-security-data-sources/container-registry-scanning/configure-registry-scanning-for-cloud-accounts.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.