> 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-xpanse/inventory.md). # Inventory Access a comprehensive inventory of all the assets Cortex Xpanse has attributed to your organization. Asset identification is foundational for information security. In the **Inventory**, Cortex Xpanse provides a comprehensive inventory of all the discoverable assets for your organization. The Inventory is organized into a tab for **Unified Inventory** and a tab for each asset types. Each tab in the **Inventory** presents a table view of the relevant assets with key information about each asset. Asset table views support extensive search, filtering, and sorting capabilities, enabling you to more efficiently identify, prioritize, and remediate security issues. View additional details about any asset by clicking on the row for that asset in list view. The asset details will open in a separate pane to the right of the list view. Perform specific actions on assets (such as adding or removing asset tags) by right-clicking on the asset in the list view and selecting from the available options. ## Add or remove assets To add or remove assets from your asset map, see [Upload or remove assets](#add-or-remove-assets). ## Monitor assets for acquisitions Xpanse can generally include acquisition assets. Work with your Customer Success team to explore this option. --- # 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-xpanse/inventory.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.