> 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-xsiam/insights-and-tips-cortex-xsiam/investigation-and-case-management/categorize-cases-and-assets.md).

# Categorize cases and assets

Categorize Cortex XSIAM cases and assets to organize investigations, prioritize response, and improve tracking.

Cortex XSIAM gives you several ways to categorize work. Each has a different purpose.

| Mechanism                  | Use it to                                                                   | Notes                                                                                                |
| -------------------------- | --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Case and issue domains** | Separate response areas, such as Security, Posture, Health, Hunting, and IT | Every case and issue has one domain. You can create custom domains for workflows such as compliance. |
| **Custom case fields**     | Add business classifications, such as business unit, impact, or use case    | Add fields to layouts and to the cases table, and filter and report on them                          |
| **Asset groups**           | Group assets by shared attributes (dynamic) or by selection (static)        | Used for filtering, enrichment, and scope-based access                                               |
| **Endpoint tags**          | Label endpoints, for example by site or role                                | Filter endpoints and target policies and actions                                                     |
| **Indicator tags**         | Label threat intelligence indicators                                        | Appended across sources                                                                              |

### Domains

Issues get a domain automatically, and their case inherits it. Use built-in domains where you can: custom domains may not work with all content, and smart grouping and SmartScore aren't supported for them. A domain can't be changed after it's assigned. See [Case and issue domains](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/overview-of-cases/case-and-issue-domains.md) and [Create a case domain](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/customize-cases-and-issues/create-a-case-domain.md).

### Custom fields

See [Create custom case fields](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/customize-cases-and-issues/customize-case-fields-and-layouts/case-fields/create-custom-case-fields.md).

### Assets and endpoints

See [Asset groups](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/detect-investigate-and-respond-to-threats/asset-management/asset-groups.md) and [Track your endpoint tags](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/protect-your-endpoints/endpoint-security/install-and-manage-endpoints/manage-endpoint-protection/manage-endpoint-tags/track-your-endpoint-tags.md).


---

# 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-xsiam/insights-and-tips-cortex-xsiam/investigation-and-case-management/categorize-cases-and-assets.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.
