> 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/cases-and-issues/overview-of-cases/what-are-cases.md).

# What are cases?

Understand how Cortex Cloud groups related security activity into cases.

A case is a defined problem created by connecting related issues into a single story. It shows the impacted assets and key data in one place, helping you focus on the threats that matter most, reduce noise, and resolve the problem efficiently using automation. Each case is unique and requires its own investigation.

Cases comprise the following objects:

* **Issues:** Problems detected in your environment that exceed defined thresholds or surpass your organization's accepted level of risk and threat tolerance.
* **Assets:** Specific entities impacted in a case and how they fit into the case story.
* **Artifacts:** Objects to which behavior or influence can be attributed, such as filenames, processes, domains, and IP addresses.

To see a list of all cases, go to **Cases & Issues** → **Cases**.

While cases are configured to work OOTB, users with specific requirements can customize and tailor their cases.

### **Case creation and issue grouping**

Not all issues are promoted to cases. When a new issue is triggered, it is evaluated to determine if it meets the criteria for case promotion. If the issue qualifies, the system uses case grouping logic to correlate the issue with an existing case; if no match is found, a new case is generated. For more information about how cases are built, see [Case grouping](/cortex-cloud-posture-management/cases-and-issues/case-concepts/case-grouping.md).

{% hint style="warning" %}
Case grouping is supported for Security and Posture domains only.
{% endhint %}

#### Automatic case creation

A case is automatically generated for any issue that falls into these categories:

* It is assigned to the **Security** or **Posture** domain with **Medium** severity or higher.
* It was generated from the **public API** and has **Medium** severity or higher.
* It was created from **correlations** and has **Medium** severity or higher.

While most low-severity issues do not create cases, specific analytic rules can trigger case creation for low-severity issues when action is deemed necessary. Low-severity issues created from correlation rules are not grouped into cases.

#### Manual case creation

You can also manually create cases from the **Cases** page and select issues to link to the case. For more information, see [Create a case.](/cortex-cloud-posture-management/cases-and-issues/analyze-and-resolve-cases/additional-case-actions/create-a-case.md)

At least one issue must be linked to a case. If all issues are unlinked from a case, the case is deleted.


---

# 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/cases-and-issues/overview-of-cases/what-are-cases.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.