> 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/detect-investigate-and-respond-to-threats/asset-management/asset-configurations/application-criteria.md).

# Application criteria

Configure application criteria for asset management in Cortex XSIAM.

You can define and group assets into applications using two primary methods:

* **New Application:** **Manually build an application** by selecting starting assets from either the **code side** (VCS repositories) or the **run side** (cloud providers, Kubernetes clusters, or VPCs). Cortex XSIAM automatically identifies and adds related assets based on their connections.
* **New Criteria:** Automatically create and maintain applications in bulk by defining dynamic rules. You can base these criteria on **Cloud tags** (such as AWS tags grouping assets within a single provider), or **VCS entities** (automatically generating applications based on your code hierarchy, such as GitHub organizations or repositories).

Go to **Inventory** → **Assets** → **Configurations** → **Application Criteria** to add a new application or new criteria.

For more information, see: [Defining Business Applications](/application-security/application-security-posture-management-aspm/applications/defining-business-applications.md).

For information on defining applications, see [Defining Business Applications](/cortex-xsiam/detect-investigate-and-respond-to-threats/asset-management/asset-classes/application-assets.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/detect-investigate-and-respond-to-threats/asset-management/asset-configurations/application-criteria.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.