> 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/data-security-documentation/onboard-and-configure/post-onboarding/how-to-configure-the-scanning-settings-for-supported-services.md).

# How to configure the scanning settings for supported services

1. In the lower left area, click Settings → Data Sources & Integrations.
2. On the Data Sources & Integrations page, click a cloud service provider or other data source and then click the View Details link.
3. On the Cloud Instances screen, click an instance name link. A screen displaying the instance name opens.
4. At the bottom of the screen, under Accounts (AWS), Subscriptions (Azure), or Projects (GCP), right-click an item in the list and then in the context menu, select Edit.
5. In the screen that opens, under Data assets classification options, you can do the following:
   * Select or deselect managed services, which are native cloud services that are managed directly by your cloud provider, such as AWS, Azure, or GCP.
   * Select or deselect self-managed assets, which are databases that you run on your cloud virtual machines.
   * Configure a cadence indicating how often a scan should be performed.

     If you do not select a scanning cadence, the default setting is applied. For more information, contact your [Customer Support team](https://support.paloaltonetworks.com/Support/Index).
6. Click Save.

   For more information about supported assets in Cortex Data Security, see [Supported assets in Cortex Data Security](/data-security-documentation/data-security/supported-assets-in-cortex-data-security.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 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/data-security-documentation/onboard-and-configure/post-onboarding/how-to-configure-the-scanning-settings-for-supported-services.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.