> 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-posture-management/agentless-disk-scanning/run-an-on-demand-scan.md).

# Run an on-demand scan

Run an on-demand Agentless disk scan of a single VM to get current findings without waiting for the next scheduled scan.

Run an on-demand scan to get current findings for a VM, for example after you patch a vulnerability or create a new VM.

### Prerequisites

Before you run an on-demand scan, make sure that you have the following:

* A VM in a cloud account with ADS turned on.
* A VM that ADS supports and that is inside the scan scope.

### How to run an on-demand scan

To run an on-demand ADS scan, do the following:

1. Select **Inventory → All Assets**.
2. Search for **VM Instances**.
3. Select the VM.
4. In the header of the asset card, open the action menu (**⋮**).
5. Click **Rescan**.

ADS scans the VM. After the scan finishes, the asset details show the new scan time and the updated findings.

<br>


---

# 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-posture-management/agentless-disk-scanning/run-an-on-demand-scan.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.
