> 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-cloud-posture-management/cloud-inventory-and-environment/asset-ownership.md).

# Asset ownership

Asset ownership adds an Owners field to asset records in the Cortex Cloud asset inventory, derived automatically from ownership tags.

## Asset ownership

Asset ownership brings owner data from cloud tags and your ServiceNow configuration management database (CMDB) into the asset inventory. It adds an **Owners** field to asset records, derived automatically from ownership tags such as **owner** and **owned\_by**. Use asset owners to identify who is responsible for an asset and speed up issue assignment and remediation.

Asset ownership is a structured, multi-value property on every asset record in the asset inventory:

* **Owners field:** Each asset can have zero, one, or more owners. Owners are stored as a list of names.
* **Automatic derivation:** Out-of-the-box, Cortex Cloud reads supported ownership tags on the asset, such as an **owner** cloud tag, and adds the tag values to the **Owners** field.
* **Multiple sources:** Owners can come from more than one source. Owners from all sources are merged into one list on the asset.

Asset ownership appears in:

* **Asset inventory table:** The **Owners** column shows the first owner of each asset. If an asset has more than one owner, the column shows the number of additional owners, for example +2. Hover over the number to see the other owners. You can filter the table by one or more owners.
* **Asset details panel:** The **Owner** field (or **Owners**, if there is more than one) appears at the top of the general details section. The field appears only when the asset has at least one owner.

### How owners are derived from tags

Cortex Cloud reads the tags on each asset when it ingests or updates the asset, derives owners from these tag keys, and combines the results from all of them:

| **Tag key**            | **Source**                  | **Example tag**                   | **Resulting owner** |
| ---------------------- | --------------------------- | --------------------------------- | ------------------- |
| owner                  | Cloud tag                   | owner: <jane@example.com>         | <jane@example.com>  |
| owned\_by              | Cloud tag                   | owned\_by: Platform Team          | Platform Team       |
| ServiceNow:owned\_by   | ServiceNow CMDB integration | ServiceNow:owned\_by: Alice Smith | Alice Smith         |
| ServiceNow:managed\_by | ServiceNow CMDB integration | ServiceNow:managed\_by: Bob Jones | Bob Jones           |

These rules apply to ownership tags:

* **Case-sensitive keys:** Tag keys must match exactly. Owners are not derived from keys such as **Owner** or **OWNED\_BY**.
* **Multiple owners in one tag:** Tag values are split at each comma and a separate owner is created for each part. Leading and trailing spaces are removed and empty parts are ignored.
* **Any value:** Tag values are not validated. An owner can be a person's name, a team name, or an email address.
* **No duplicates:** Each owner is listed one time, even if the same name appears in more than one tag or data source. Owner names are case-sensitive, so **Alice** and **alice** are two different owners.
* **Tag removal:** When a data source reports the asset without its ownership tags, owners that came from that source are removed. Owners from other sources stay on the asset.

For example, an asset with the tags **owner: alice, bob** and **owned\_by: bob, carol** has three owners: **alice, bob, and carol**.

### Find assets by owner

Filter the asset inventory by owner to list every asset that belongs to a specific person or team, or to find assets that don't have an owner.

1. Select **Inventory > Assets > All Assets**.
2. (Optional) If the **Owners** column isn't displayed, add it:
3. Click the customize columns icon, which is to the right of **Display** on the table toolbar.
4. In the **Search** field, enter **Owners**, and then select the **Owners** checkbox.
5. In the filter row, click the add filter icon, and then select **Owners**.
6. Click the **Enter Owners** list, and then select the checkbox for each owner that you want to filter by. To narrow the list, enter part of the owner name or email address.
7. (Optional) To include assets that don't have an owner, select **Include empty values**. To show only assets without an owner, select **Include empty values** and don't select any owners.
8. Click outside the filter to close it and apply the filter.

<br>


---

# 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-cloud-posture-management/cloud-inventory-and-environment/asset-ownership.md?ask=<question>&goal=<user_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.
