> 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-runtime-security/cases-and-issues/analyze-and-resolve-cases/resolve-the-case/resolution-reasons-for-cases-and-issues.md).

# Resolution reasons for cases and issues

Select resolution reasons for cases and issues.

When you resolve a case or issue, you must also specify a resolution reason. The following table describes the resolution reasons for selection.

<table><thead><tr><th width="196">Resolution reason</th><th>Description</th></tr></thead><tbody><tr><td>Resolved - True Positive</td><td><p>The case or issue was correctly identified by Cortex Cloud as a real threat, and the case was successfully handled and resolved.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>Cases and issues resolved as True Positive and False Positive help Cortex Cloud to identify real threats in your environment by comparing future cases and associated issues to the resolved cases. Therefore, the handling and scoring of future cases is affected by these resolutions.</p></div></td></tr><tr><td>Resolved - False Positive</td><td><p>The case or issue is not a real threat.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>Cases and issues resolved as True Positive and False Positive help Cortex Cloud to identify real threats in your environment by comparing future cases and associated issues to the resolved cases. Therefore, the handling and scoring of future cases is affected by these resolutions.</p></div></td></tr><tr><td>Resolved - Security Testing</td><td>The case or issue is related to security testing or simulation activity, such as a BAS, pentest, or red team activity.</td></tr><tr><td>Resolved - Known Issue</td><td>The case or issue is related to an existing issue or an issue that is already being handled.</td></tr><tr><td>Resolved - Duplicate Case</td><td>The case or issue is a duplicate of another case.</td></tr><tr><td>Resolved - Risk Accepted</td><td>The case or issue is related to a known mitigation or impact.</td></tr></tbody></table>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cases-and-issues/analyze-and-resolve-cases/resolve-the-case/resolution-reasons-for-cases-and-issues.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 `build a script that syncs our docs to a CMS` 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.