> 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/reference-and-developer-docs/role-based-access-control/exceptions-configuration-permissions/issue-exclusions-permissions.md).

# Issue Exclusions permissions

Configure Issue Exclusions permissions in Cortex XSIAM.

Issue Exclusions permissions control access to the following:

* Access to the **Issue Exception & Exclusion** page or the standalone **Issue Exclusion** page.
* Viewing, creating, and managing issue exclusion rules on the **Issue Exception & Exclusion** page or the standalone **Issue Exclusion** page
* Creating issue exclusions when resolving issues via the **Issues** or **Cases** pages.
* Excluding individual or bulk issues when working with cases and issues via the **Issues** or **Cases** pages.

### Access the **Issue Exception & Exclusion** page

Depending on your RBAC permissions, access to the **Issue Exception & Exclusion** page varies. This is a combined page that lists Exclusion Rules and Exception Rules. Users require both sets of permissions to see this page. 

<table><thead><tr><th width="247">Page</th><th>Required permissions</th></tr></thead><tbody><tr><td>Combined <strong>Issue Exception &#x26; Exclusion</strong></td><td><p></p><ul><li>View or View/Edit permissions for <strong>Issue Exclusions.</strong></li><li>View or View/Edit permissions for <strong>Exception Management Admin.</strong></li></ul></td></tr><tr><td>Standalone <strong>Issue Exclusions</strong></td><td><p></p><ul><li>View or View/Edit permissions for <strong>Issue Exclusions.</strong></li><li>No permissions for <strong>Exception Management Admin.</strong></li></ul></td></tr></tbody></table>

{% hint style="info" %}
Users with only **Exception Management Admin** cannot access the page.
{% endhint %}

#### &#x20;Navigate to the **Issue Exception & Exclusion** page

The navigation path depends on your RBAC permissions and tenant configuration. Take one of the following paths:

* **Settings** → **Issue Exception & Exclusion**
* **Settings** → **Exception Management** → **Issue Exception & Exclusion**
* **Settings** → **Exception Configurations**

On this page you can see the following tabs:

* **Exclusion Rules:** Defines conditions (based on issue attributes, such as severity, source, category, etc.) that automatically suppress the creation or surfacing of matching issues. This is the primary mechanism for tuning out false positives and reducing issue noise.
* **Exception Rules:** Defines conditions under which issues are flagged as exceptions that may require approval before being acted upon, rather than being silently suppressed.

### Issue Exclusion permission levels

<table><thead><tr><th width="105">Permission</th><th width="354">Description</th><th>Roles Example</th></tr></thead><tbody><tr><td>None</td><td><p></p><ul><li>No access to the <strong>Issue Exception &#x26; Exclusion</strong> or <strong>Issue Exclusions</strong> page.</li><li>No access to issue exclusion actions anywhere in Cortex XSIAM.</li></ul></td><td>SOC Tier-1 Analyst: Should escalate false positives rather than create exclusions.</td></tr><tr><td>View</td><td><p></p><ul><li>Read-only access to the <strong>Issue Exception &#x26; Exclusion</strong> or <strong>Issue Exclusions</strong> page. </li><li>Users can browse the <strong>Exclusion Rules</strong> tab, view rule details (name, description, indicator conditions, BIOC indicators, status, modification time), search and filter rules, and export data.</li><li>No access to create new rules, edit existing rules, delete rules, or enable/disable rules on either tab.</li><li>No access to issue exclusion actions during case resolution or in the issues and cases pages.</li></ul></td><td>SOC Tier-2 Analyst and Threat Hunter: Should reference existing exclusions during investigations or understand filtered activity.</td></tr><tr><td>View/Edit</td><td><p></p><ul><li>Read and write access to the <strong>Issue Exception &#x26; Exclusion</strong> or <strong>Issue Exclusions</strong> page. </li><li>Users can create, edit, delete, enable, import, and duplicate exclusion rules.</li><li>Users can create issue exclusion during case resolution. </li><li>Users can exclude single or bulk issues via the <strong>Issues</strong> and <strong>Cases</strong> pages.</li></ul></td><td><ul><li>SOC Tier-3 Analyst: Create exclusions for validated false positives.</li><li>Security Engineer: Manage exclusion rules as part of tuning.</li></ul></td></tr></tbody></table>

**Required and recommended permissions**

Consider adding the following permissions:

<table><thead><tr><th width="145.99993896484375">Permission</th><th width="126">Permission Level</th><th>Reason</th></tr></thead><tbody><tr><td>Cases &#x26; Issues</td><td>View or View/Edit</td><td><ul><li><strong>View:</strong> Exclusion rules are based on issue attributes. Without issue visibility, users cannot understand the context of what is being excluded.</li><li><strong>View/Edit:</strong> Users manage issues and create exclusions directly from issue context menus or during resolution. Analysts typically create issue exclusions directly when investigating an issue. To right-click and exclude an issue, the user must have View/Edit permissions. Strongly recommended.</li></ul></td></tr><tr><td>Exception Management Admin</td><td>View or View/Edit</td><td><ul><li><strong>View:</strong> Users have access to the Combined <strong>Issue Exception &#x26; Exclusion page</strong> and can browse exclusion rules but cannot see details of the rules.</li><li><strong>View/Edit:</strong> Users have access to the Combined <strong>Issue Exception &#x26; Exclusion page</strong> and can browse, manage and create exception rules.</li></ul><p>Users who manage exclusion rules typically also need to manage exception rules to complete the exception management workflow. Strongly recommended.</p></td></tr><tr><td>Detection Rules</td><td>View</td><td>Recommended to view related IOC/BIOC detection rules to understand what triggers the issues being excluded.</td></tr><tr><td>Agent Profiles</td><td>View</td><td>Recommended to view endpoint profiles for scoping exclusions to specific endpoint groups.</td></tr><tr><td>Global Exceptions</td><td>View</td><td>Strongly recommended to view global exception policies to understand the full exclusion landscape and avoid conflicts.</td></tr><tr><td>Query Center</td><td>View</td><td>Recommended to run XQL queries to validate exclusion impact and verify suppressed issues.</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 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/reference-and-developer-docs/role-based-access-control/exceptions-configuration-permissions/issue-exclusions-permissions.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.