> 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-xdr-3.x/cortex-xdr-3.x-documentation/investigate-and-respond-to-incidents/incident-handling/manage-incidents/resolution-reasons-for-incidents-and-alerts.md). # Resolution reasons for incidents and alerts Describes the resolution reasons for incidents and alerts. When you resolve an incident or alert you must also specify a resolution reason. The following table describes the resolution reasons available for selection. | Resolution reason | Description | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Resolved - True Positive |

The incident was correctly identified by Cortex XDR as a real threat, and the incident was successfully handled and resolved.

Note

Incidents resolved as True Positive and False Positive help Cortex XDR to identify real threats in your environment by comparing future incidents and associated alerts to the resolved incidents. Therefore, the handling and scoring of future incidents is affected by these resolutions.

| | Resolved - False Positive |

The incident is not a real threat.

Note

Incidents resolved as True Positive and False Positive help Cortex XDR to identify real threats in your environment by comparing future incidents and associated alerts to the resolved incidents. Therefore, the handling and scoring of future incidents is affected by these resolutions.

| | Resolved - Security Testing | The incident is related to security testing or simulation activity such as a BAS, pentest, or red team activity. | | Resolved - Known Issue | The incident is related to an existing issue or an issue that is already being handled. | | Resolved - Duplicate Incident | The incident is a duplicate of another incident. | --- # 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-xdr-3.x/cortex-xdr-3.x-documentation/investigate-and-respond-to-incidents/incident-handling/manage-incidents/resolution-reasons-for-incidents-and-alerts.md?ask=&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.