> 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-5.x/protect-your-endpoints/install-and-manage-endpoints/set-up-endpoint-protection/set-up-endpoint-profiles-and-exception-rules/set-up-exception-profiles-and-rules/issue-exclusions.md).

# Issue exclusions

The **Settings** → **Exception Configuration** → **Issue Exclusions** page displays the issue exclusion rules in Cortex XDR.

An Issue Exclusion is a rule that contains a set of issue match criteria for issues that you want to suppress in Cortex XDR. You can add an Issue Exclusion rule from scratch, or base the exclusion on issues that you investigate in a case. After you create an exclusion rule, Cortex XDR excludes the issues that match the criteria from cases and search query results, and no longer saves any of the matching issues that are generated in the future. If you select to apply the policy to historic results as well as future alerts, Cortex XDR displays the historic alerts as unavailable.

{% hint style="info" %}

### Note

* The agent continues to generate excluded issues on the endpoint, but they are not saved or displayed in Cortex XDR. Configuration of an issue exclusion does not remove or delete any of the logs that would have triggered the issue notification.
* You can also set up issue exceptions by creating global endpoint policy exceptions. For more information, see [Add a global endpoint policy exception](/cortex-xdr-5.x/protect-your-endpoints/install-and-manage-endpoints/set-up-endpoint-protection/set-up-endpoint-profiles-and-exception-rules/set-up-exception-profiles-and-rules/add-a-legacy-exception-rule-for-endpoints/add-a-global-endpoint-policy-exception.md).
* Cortex XDR supports exclusion of up to 100,000 issues.
  {% endhint %}

The following table describes both the default fields and additional optional fields that you can add to the issue exclusions table, and lists the fields in alphabetical order.

| Field                                         | Description                                                                                                                                                                         |
| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ![check-box.png](/files/Upt7U3rsKjThFSPTpFpI) | Checkbox to select one or more issue exclusions on which you want to perform actions.                                                                                               |
| Backward Scan Status                          | Exclusion policy status for historic data, either enabled if you want to apply the policy to previous issues, or disabled if you don’t want to apply the policy to previous issues. |
| Comment                                       | Administrator-provided comment that describes the purpose or reason for the exclusion policy.                                                                                       |
| Description                                   | Text summary of the policy that displays the match criteria.                                                                                                                        |
| Modification Date                             | Date and time when the exclusion policy was created or modified.                                                                                                                    |
| Name                                          | Descriptive name provided to identify the exclusion policy.                                                                                                                         |
| Policy ID                                     | Unique ID assigned to the exclusion policy.                                                                                                                                         |
| Status                                        | Exclusion policy status, either enabled or disabled.                                                                                                                                |
| User                                          | User that last modified the exclusion policy.                                                                                                                                       |
| User Email                                    | The administrative user's email address.                                                                                                                                            |


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-5.x/protect-your-endpoints/install-and-manage-endpoints/set-up-endpoint-protection/set-up-endpoint-profiles-and-exception-rules/set-up-exception-profiles-and-rules/issue-exclusions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.