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.
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).
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.
Alert Exclusions support SBAC (scoped based access control). 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.
Build an Alert Exclusion Policy from Alerts in an Incident
You can create an exclusion rule based on the alerts in the incident.
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.
In→ , from the Incident view, click the three dots menu and, select .
Enter a Rule Name to identify your alert exclusion.
Enter a Description that specifies the reason or purpose of the alert exclusion rule.
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.
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→ → page.
Build an Alert Exclusion Rule from Scratch
Build your own alert exclusion rule.
Select→ → .
Select + Add an Alert Exclusion Rule.
Specify a Rule Name to identify the exclusion rule.
Describe the reason or purpose of the rule.
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.
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.
This action is irreversible. All historically excluded alerts will remain excluded if you disable or delete the rule.
Create the alert exception rule.