> 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/registry-scanning/configure-registry-scanning-for-cloud-accounts/modify-the-container-registry-scanning-scope.md).

# Modify the container registry scanning scope

Modify the Cortex Cloud container registry scanning scope for cloud accounts and registries.

Using the **Modify Scanning Scope** option, you can define conditions to automatically exclude selected scopes from scanning. These conditions can be based on the registry, repository, or tag. After you set the scope, the exclusion conditions are automatically applied to newly discovered images in the account.To modify the scanning scope, do the following:

1. Navigate to **Settings** → **Data Sources**.
2. In the **Cloud Provider** section, locate the provider where your assets are stored and click **View Details**.
3. On the **Cloud Instances** page, click the instance name for which you want to modify the scope.
4. Under the **Accounts** section, select the account, right-click, and choose **Edit**.
5. Under the **Registry Scanning Scope**, enable **Modify Scanning Scope**.
6. From the list of images, select the image you want to modify.
7. Alternatively, you can also filter for a specific image by clicking the **Filter** icon and selecting **Registry**, **Repository**, or **Tags** option and then adding the desired value to refine your search.The search results are applied automatically, even if you do not select **Save**.
8. Click **Save** to confirm your modifications.

This ensures that the specified scanning scope is customized based on your needs.


---

# 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-runtime-security/registry-scanning/configure-registry-scanning-for-cloud-accounts/modify-the-container-registry-scanning-scope.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.