> 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-advantages.md).

# ADS advantages

Learn about the advantages of Agentless disk scanning compared with agent-based security for cloud workloads.

ADS provides the following advantages:

* **No impact on workloads**: ADS runs outside your VMs. Scans don't use CPU, memory or disk resources on your VMs, so ADS is safe for performance-sensitive workloads.
* **Coverage where agents can't run**: ADS scans VMs where you can't or aren't allowed to install an agent, such as legacy systems, isolated environments, third-party VMs and short-lived development and test VMs.
* **Simple, fast rollout**: ADS is part of the cloud account onboarding process. After you onboard a cloud account, ADS scans the supported VMs in the account without any further deployment.
* **Scalability**: ADS scales with your cloud. When new VMs are added to an onboarded cloud account, ADS includes them in its scans automatically.
* **No agent maintenance**: Because ADS has no agent, you avoid agent conflicts, agent updates and agent lifecycle management.


---

# 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-advantages.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.
