> 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-xdr-5.x/detect-investigate-and-respond-to-threats/asset-management/all-cloud-assets.md). # All cloud assets Learn about the All Cloud Assets page to view and assess your cloud footprint. The **All Cloud Assets** page provides a centralized, normalized view of your infrastructure across multi-cloud environments. It helps you assess your cloud footprint and serves as the foundation for Cloud Security Posture Management (CSPM). Navigate to **Inventory > Assets > All Cloud Assets** to view an aggregated summary of your cloud footprint. The dashboard features interactive widgets summarizing the total number of cloud assets, a breakdown by service such as Amazon EC2, AWS IAM, and AWS Backup, and a breakdown by provider such as AWS, Azure, and GCP. The primary inventory table groups your cloud data by provider. For each provider, it displays high-level aggregates: * Total assets and issues * Number of cloud accounts and services * Number of distinct asset categories, types, and classes **Cloud assets explorer** Clicking into a specific provider opens the Cloud Assets Explorer. This detailed table lists every individual cloud resource, including S3 Buckets, EC2 Instances, IAM Roles, API Gateways, and CloudFormation Stacks. **Cloud asset details** Clicking an individual cloud asset in the explorer opens a detailed side card with tabs for Overview, Configurations, and Compliance. The Configurations tab displays the raw Asset Configuration JSON as ingested from the cloud provider, along with any active Cloud Configuration Issues detected on the asset. The Compliance tab shows an Overall Compliance Score and a breakdown of Controls by Status. --- # 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-xdr-5.x/detect-investigate-and-respond-to-threats/asset-management/all-cloud-assets.md?ask=&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.