> 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/onboard-and-configure-cortex-xpanse/step-5-begin-asset-validation-and-asset-enrichment.md). # Step 5: Begin asset validation and asset enrichment As soon as you have access to Cortex Xpanse, you can begin asset validation and enrichment. Asset validation is the process of reviewing the assets in your inventory to verify that those assets belong to your organization. Asset validation ensures that your organization doesn't spend time and resources fixing issues on assets that are not under your control. Asset enrichment is the process of tagging assets so you can identify and filter those assets based on department, geographical location, or any other category that would be useful to your organization. Asset validation and asset enrichment are not one-time activities; these are on-going activities that you will perform periodically to ensure your inventory is accurate and easily managed. #### Before you begin Review the following information before you perform asset validation and enrichment. | Prerequisite | See topic | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | | Learn about the types of assets in your Cortex Xpanse inventory, and how they are organized. | [Inventory](/cortex-xpanse/inventory.md) | | Familiarize yourself with the asset attribution evidence that is provided for each asset in Xpanse. Asset attribution evidence explains why Cortex Xpanse believes an asset belongs to your organization. | [Asset Attribution](/cortex-xpanse/inventory/asset-attribution.md) | | Learn about inventory tagging in Cortex Xpanse, including the types of tags, how to add and remove tags, and how to automate tagging using inventory tag rules. | [Inventory Tagging](/cortex-xpanse/inventory/asset-tagging.md) | #### Validate Xpanse-discovered assets Cortex Xpanse places assets into two categories based on discovery method: * **Provided**: These assets were provided by the customer and added to the asset map by the Cortex Xpanse team. * **Xpanse discovered**: These assets were discovered by Xpanse. Xpanse assets are reviewed and maintained quarterly. Ideally you'll validate all assets in your inventory, but we suggest you begin by validating the Xpanse-discovered assets. Assets that were discovered by Xpanse are tagged **xpanse discovered** so you can identify them. 1. In Expander, navigate to **Inventory** → **\**. 2. Filter the list of assets. 1. Open the filter by clicking on the filter icon ![filter-icon.png](/files/4RY4Q2YIfz7NPlxVWk5H) on the top right side of the screen. 2. In the filter, select the field **Tags** and the value **xpanse discovered** or **provided** (or any other tag you would like to filter on). Be sure to select the **IPR:** tag if you are filtering Owned Responsive IPs or IP Ranges, and select the **AT:** tag for any other asset types. ![filter-validate.png](/files/n02W0Mhlmi9su524gdZo) 3. Click anywhere outside the filter to activate the filter and see the results. 3. View the asset attribution evidence for an asset by clicking on the row to display the asset details. Asset attribution evidence and other asset details will help you determine whether the asset is yours. ![asset-attribution-evidence.png](/files/5T753rikeIQVsLwLXcch) 4. If you find assets that don't belong to your organization, submit a request to your Customer Success team to remove them from your inventory. You can send them a spreadsheet or txt file that lists the assets, or you can tag the assets (with a label such as "remove") and request Customer Success to remove all assets with that label. ## Begin tagging assets Asset enrichment refers to adding contextual information to assets, typically in the form of tags. Tags are labels that you assign to an asset or group of assets. You can create tags yourself in Expander, which ensures that your approach to tagging meets the unique requirements of your organization. Tags can be geographical locations, names of business units, departments, or teams, or any other useful category. Tags help you organize and manage the assets in your inventory. The tags on assets are also applied automatically to corresponding services, websites, alerts, and incidents, providing valuable context when triaging identified risks in your attack surface. You can apply and remove tags individually or in bulk in Expander or using the [Cortex Xpanse APIs](https://docs-cortex.paloaltonetworks.com/r/Cortex-Xpanse-REST-API/Cortex-Xpanse-API-Overview). You can also create inventory tag rules that apply tags to all assets that meet specific rule criteria. See [Inventory Tagging](https://app.gitbook.com/s/02CCMTnqc4fWJkdEuCs8/asset-tagging) for details about how tags work, how to apply them, and how to automate tagging with inventory tag rules. Like asset validation, asset enrichment is an ongoing activity that you begin during onboarding and continue as your attack surface changes and as you discover different ways of organizing and categorizing your assets. --- # 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-xpanse/onboard-and-configure-cortex-xpanse/step-5-begin-asset-validation-and-asset-enrichment.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.