> 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/upgrade-to-cortex-xdr-5/new-unified-asset-inventory-and-cloud-data-sources.md).

# New unified Asset Inventory and cloud data sources

The new Asset Inventory provides a comprehensive view of all assets across your environment, ensuring complete visibility, control, and protection. With coverage that extends across multi-cloud and hybrid environments, including cloud providers and enterprise deployments, the Asset Inventory delivers end-to-end visibility across your entire enterprise ecosystem. In addition, cloud resources are now integrated into the inventory through dedicated cloud provider integrations, ensuring complete visibility and improved coverage of your cloud assets.

By consolidating all asset types into a single, unified view, the Asset Inventory makes it easy to find and investigate assets, regardless of their original data source. From network assets, identities, and applications to data entities, code resources, pipelines, AI models, and more, all assets are now accessible through a single standardized interface.

Security teams can quickly investigate assets related to security findings, issues, and cases—accessing configurations, access data, and security highlights directly from the asset card. Built on a unified data model, the Asset Inventory enables straightforward filtering and investigation across different domains and use cases with ease and simplicity. In addition, Asset Inventory data is now available for querying with Cortex Query Language (XQL), enabling more in-depth investigation and reporting.

Read more: [Asset management](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/asset-management.md)

#### Important changes to the Asset Inventory and cloud data sources

The Legacy Inventory and related cloud data sources (such as, Prisma Cloud and Cloud Inventory) are now deprecated. Previously installed instances will continue to operate and ingest alert and asset data; however, you cannot modify configurations or connect new instances on deprecated data sources.

To ensure full visibility across all your cloud assets, we recommend taking the following steps:

1. Replace the deprecated data sources **Cloud Inventory** and **Prisma Cloud** with the new cloud data sources, see [Ingest cloud assets](/cortex-xdr-5.x/configure-cortex-xdr/cortex-xdr-data-sources/cloud-service-provider-csp-onboarding.md).
2. After connecting the new cloud data sources, asset data is automatically ingested and displayed in the new Asset Inventory. We recommend transitioning to the new inventory as soon as possible to ensure accurate and up-to-date asset visibility and management.

To access the Legacy Inventory, click the **Show legacy** toggle in the new Asset Inventory. This toggle is only visible if one or more deprecated data sources were connected before the upgrade.


---

# 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://cortex-docs.paloaltonetworks.com/upgrade-to-cortex-xdr-5/new-unified-asset-inventory-and-cloud-data-sources.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.