> 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-3.x/cortex-xdr-3.x-documentation/detect-threats-and-analyze-data/asset-management/asset-inventory.md).
# Asset Inventory
Cortex XDR provides a central location from which you can view and investigate information relating to assets in your network. Using your defined internal network configurations, Broker VM Network Mapper, Cortex XDR agent, EDR data collected from firewall logs, and logs from third-party vendors, Cortex XDR is able to aggregate and display a list of all the assets located within your network. As soon as Cortex XDR begins receiving network assets, you can view the data in **Assets** → **Asset Inventory**.
The following are some of the main features available on these pages.
* When any row in the table is selected, a side panel on the right with greater details is displayed, where you can view additional data divided by sections. The section heading names and data displayed change depending on the source of the assets.
* Depending on the cell you’ve selected in the table, different right-click pivot menus are available, such as **Open IP View** and **Open in Quick Launcher**.
* You can export the tables and respective asset views to a tab-separated values (TSV) file.
You can toggle between the **Legacy View** and **Advanced View** on the page. The **Legacy View** displays a list of all the assets located within your network according to their IP address., while the
* **Advanced View** (default)—Includes the following features:
* You can view the data in a table format by accessing the pages for **All Assets** and **Specific Assets**, including **On-Prem Assets** and **Cloud Compute Instances**.
* The table columns provide newly structured data with updated filtering capabilities to improve your asset visibility.
* When any row in a table is selected, a side panel on the right with greater details is displayed, where you can view additional data divided by sections. The section heading names and data displayed change depending on the source of the assets.
* Depending on the cell you’ve selected in the table, different right-click pivot menus are available, such as **Open IP View** and **Open in Quick Launcher**.
* You can export the tables and respective asset views to a tab-separated values (TSV) file.
To easily investigate your asset inventory using the Legacy View.
* Select **Assets** → **Asset Inventory**.
* In the **Page layout** notification, toggle to the **Legacy view**.
* Filter and review your assets.
By default, the **Assets** table is filtered according to unmanaged assets over the last 7 days. The following table describes both the default and optional fields in the table, and the network prerequisites required by Cortex XDR to retrieve the data.
| Field | Description | Prerequisites |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| IP address | IP address related to the last asset associated with it. | |
| MAC address | Mac address of the asset. | The asset requires at least one of the following:
- An installed Cortex XDR agent
- A running Cortex XDR collector
- For Mac endpoints, a Global Protect client 9.1 or a later release, configured to send HIP Match logs
- Associated DHCP logs covering this asset are sent to Cortex XDR
|
| MAC address vendor | Vendor name of the Mac address of the asset. | The asset requires at least one of the following:
- An installed Cortex XDR agent
- A running Cortex XDR collector
- For Mac endpoints, a Global Protect client 9.1 or a later release, configured to send HIP Match logs
- Associated DHCP logs covering this asset are sent to Cortex XDR
|
| Host name | Host name of the asset, if available. | The asset requires at least one of the following.
- An installed Cortex XDR agent
- A running Cortex XDR collector
- A Global Protect client 9.1 or a later release, configured to send HIP Match logs
- Associated DHCP logs covering this asset are sent to Cortex XDR
|
| First time seen | Timestamp of when the IP address was first seen in the logs. | |
| Last time seen | Timestamp of when the IP address was last seen in the logs. | |
| Agent Installed | Whether or not the asset has an agent installed. | |
| Agent ID | The ID of the agent installed on the asset. Cortex XDR only displays agents that send EDR data captured in the firewall logs. | |
| Collector running | Whether or not a [Pathfinder Data Collector](/cortex-xdr-3.x/cortex-xdr-3.x-documentation/reference/rbac-permissions/role-permissions-by-components.md#configurations) is currently running on the asset. | |
| Range names | Name of the IP address range allocated to the IP address. | |
| Agent version | The version of the agent installed on the asset. Cortex XDR only displays agents that send EDR data captured in the firewall logs. | |
| Platform | Platform running on the asset. | The asset requires at least one of the following:
- An installed Cortex XDR agent
- A running Cortex XDR collector
- A Global Protect client 9.1 or a later release, configured to send HIP Match logs
|
You can export your filtered results to a TSV file.
---
# 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/cortex-xdr-3.x/cortex-xdr-3.x-documentation/detect-threats-and-analyze-data/asset-management/asset-inventory.md?ask=&goal=
```
`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.