> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/search-and-investigate/asset-queries.md).

# Asset Queries

Use asset queries to search for all your cloud assets based on comprehensive security findings and vulnerabilities.

In simple mode, you can search for assets based on asset attributes and security contexts from across Prisma Cloud in one place, create custom policies for risky assets, and understand your cloud environments better. By default, Prisma Cloud System Administrator has Asset search permission.

The `asset where` queries display results only for cloud accounts that you have onboarded to Prisma Cloud. Due to this, the number of vulnerabilities displayed on selecting [Dashboard > Vulnerabilities](/content-collections/dashboards/dashboards-vulnerabilities.md) differs from that displayed on Investigate. If you have non-onboarded cloud accounts—such as those that are included in Account Groups with an Account ID reference or you had previously onboarded on **Compute > Cloud Accounts** using account credentials, or have cloud accounts where you have deployed Defenders but the account itself is not being monitored on Prisma Cloud—the `asset where` queries will not include the assets in the search results. If you want to view these assets, you must [add the cloud account](https://github.com/PaloAltoNetworks/pc-docs-md/tree/main/enterprise-edition/content-collections/connect/connect-cloud-accounts/connect-cloud-accounts.md) on Prisma Cloud.

<figure><img src="/files/d7KNZ7ycf49YgeoAyOsC" alt="asset simple search 1"><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/content-collections/search-and-investigate/asset-queries.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
