> 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/agentless-disk-scanning/ads-use-cases.md).

# ADS use cases

Learn how organizations use Agentless disk scanning to set compliance baselines, secure VM images and find security risks in unmanaged cloud resources.

ADS is suitable for the following scenarios:

* **Compliance baselines for a new cloud footprint**: When you onboard new cloud accounts, use ADS to assess compliance across your VMs and set a compliance baseline.
* **Auto-scaling environments**: In auto-scaling groups, VMs are created and removed often. Use ADS to keep scanning the VMs in these groups without deploying an agent to each new VM.
* **VM image scanning before deployment**: Use ADS to check that your golden images and base VM images are free of vulnerabilities, malware and exposed secrets before you use them to create production VMs.
* **Orphaned and dormant resources**: Use ADS to find security risks in VMs that are still provisioned but that no one actively manages or monitors, including stopped VMs.


---

# 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-xsiam/cloud-security/agentless-disk-scanning/ads-use-cases.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.
