> 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/endpoint-security/install-and-manage-endpoints/set-up-endpoint-protection/set-up-endpoint-profiles-and-exception-rules/set-up-exception-profiles-and-rules/alert-exclusions/add-an-alert-exclusion-rule.md).

# Add an alert exclusion rule

Through the process of triaging alerts or resolving an incident, you may determine whether a specific alert does not indicate a threat. If you do not want Cortex XDR to display alerts that match certain criteria, you can create an alert exclusion rule.

After you create an exclusion rule, Cortex XDR hides any future alerts that match the criteria, and excludes the alerts from incidents and search query results. If you choose to apply the rule to historic results as well as future alerts, the app identifies any historic alerts as grayed out.

{% hint style="info" %}

### Note

If an incident contains only alerts with exclusions, Cortex XDR changes the incident status to **Resolved - False Positive** and sends an email notification to the incident assignee (if set).
{% endhint %}

There are two ways to create an exclusion rule. You can define the exclusion criteria when you investigate an incident or you can create an alert exclusion from scratch.

{% hint style="info" %}

### Note

You can also set up alert exceptions by creating global endpoint policy exceptions. For more information, see [Add a global endpoint policy exception](/cortex-xdr-3.x/cortex-xdr-3.x-documentation/endpoint-security/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/add-a-global-endpoint-policy-exception.md).
{% endhint %}

Alert exclusions support Scope-Based Access Control (SBAC). For more information, see [Manage user scope](/cortex-xdr-3.x/cortex-xdr-3.x-documentation/onboard-and-configure-cortex-xdr/post-deployment-steps/manage-user-roles-and-access-management/manage-user-scope.md).

The following parameters are considered when editing a rule:

* If **Scoped Server Access** is enabled and set to restrictive mode, you can edit a rule if you are scoped to all tags in the rule.
* If **Scoped Server Access** is enabled and set to permissive mode, you can edit a rule if you are scoped to at least one tag listed in the rule.
* If a rule was added when set to restrictive mode, and then changed to permissive (or vice versa), you will only have view permissions.

<details>

<summary>Build an alert exclusion policy from alerts in an incident</summary>

If after reviewing the incident details, you want to suppress one or more alerts from appearing in the future, create an exclusion policy based on the alerts in the incident. When you create an incident from the incident view, you can define the criteria based on the alerts in the incident. If desired, you can also create an Alert Exclusion Policy from scratch.

1. In **Incident Response** → **Incidents**, from the Incident view, click the menu icon and, select **Create Exclusion**.
2. Enter a rule name to identify your alert exclusion.
3. Enter a description that specifies the reason or purpose of the alert exclusion rule.
4. Use the alert filters to add any match criteria for the alert exclusion policy.

   You can also right-click a specific value in the alert to add it as match criteria. The app refreshes to show you which alerts in the incident would be excluded. To see all matching alerts including those not related to the incident, clear the option to **Show only alerts** in the named incident.
5. **Create** the exclusion policy and confirm the action.

   If you later need to make changes, you can view, modify, or delete the exclusion policy from the **Settings** → **Exception Configuration** → **Alert Exclusions** page.

</details>

<details>

<summary>Build an alert exclusion rule from scratch</summary>

Build your own alert exclusion rule.

1. Select **Settings** → **Exception Configuration** → **Alert Exclusions**.
2. Select **+ Add an Alert Exclusion Rule**.
3. Specify a rule name to identify the exclusion rule.
4. Describe the reason or purpose of the rule.
5. Define the exclusion criteria.

   * Use the filters at the top of the table to build your exclusion criteria.
   * Use existing alert values to populate your exclusion criteria. To do so, right-click the column value on which you want to base your rule and select **Add alerts with \<value> to configuration**.

   As you define the criteria, the app filters the results to display matches.
6. Review the results.

   The alerts in the table will be excluded from appearing in the app after the rule is created and optionally, any existing alert matches will be grayed out.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><h3>Caution</h3><p>This action is irreversible. All historically excluded alerts will remain excluded if you disable or delete the rule.</p></div>
7. **Create** the alert exception rule.

</details>


---

# 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-3.x/cortex-xdr-3.x-documentation/endpoint-security/install-and-manage-endpoints/set-up-endpoint-protection/set-up-endpoint-profiles-and-exception-rules/set-up-exception-profiles-and-rules/alert-exclusions/add-an-alert-exclusion-rule.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.