Suppress alerts from Microsoft Defender for Cloud
This page explains how you can use alerts suppression rules to suppress false positives or other unwanted security alerts from Defender for Cloud.
Availability
Aspect | Details |
---|---|
Release state: | General availability (GA) |
Required roles and permissions: | Security admin and Owner can create/delete rules. Security reader and Reader can view rules. |
Clouds: |
What are suppression rules?
The Microsoft Defender plans detect threats in your environment and generate security alerts. When a single alert isn't interesting or relevant, you can manually dismiss it. Suppression rules let you automatically dismiss similar alerts in the future.
Just like when you identify an email as spam, you want to review your suppressed alerts periodically to make sure you're not missing any real threats.
Some examples of how to use suppression rule are:
- Suppress alerts that you've identified as false positives
- Suppress alerts that are being triggered too often to be useful
Create a suppression rule
You can apply suppression rules to management groups or to subscriptions.
- To suppress alerts for a management group, use Azure Policy.
- To suppress alerts for subscriptions, use the Azure portal or the REST API.
Alert types that were never triggered on a subscription or management group before the rule was created won't be suppressed.
To create a rule for a specific alert in the Azure portal:
From Defender for Cloud's security alerts page, select the alert you want to suppress.
From the details pane, select Take action.
In the Suppress similar alerts section of the Take action tab, select Create suppression rule.
In the New suppression rule pane, enter the details of your new rule.
- Entities - The resources that the rule applies to. You can specify a single resource, multiple resources, or resources that contain a partial resource ID. If you don't specify any resources, the rule applies to all resources in the subscription.
- Name - A name for the rule. Rule names must begin with a letter or a number, be between 2 and 50 characters, and contain no symbols other than dashes (-) or underscores (_).
- State - Enabled or disabled.
- Reason - Select one of the built-in reasons or 'other' to specify your own reason in the comment.
- Expiration date - An end date and time for the rule. Rules can run for without any time limit as set in Expiration date.
You select Simulate to see the number of previously received alerts that would have been dismissed if the rule was active.
Save the rule.
You can also select the Suppression rules button in the Security Alerts page and select Create suppression rule to enter the details of your new rule.
Note
For some alerts, suppression rules are not applicable for certain entities. If the rule is not available, a message will display at the end of the Create a suppression rule process.
Edit a suppression rule
To edit a rule you've created from the suppression rules page:
From Defender for Cloud's security alerts page, select Suppression rules at the top of the page.
The suppression rules page opens with all the rules for the selected subscriptions.
To edit a single rule, open the three dots (...) at the end of the rule and select Edit.
Change the details of the rule and select Apply.
To delete a rule, use the same three dots menu and select Remove.
Create and manage suppression rules with the API
You can create, view, or delete alert suppression rules using the Defender for Cloud REST API.
The relevant HTTP methods for suppression rules in the REST API are:
PUT: To create or update a suppression rule in a specified subscription.
GET:
- To list all rules configured for a specified subscription. This method returns an array of the applicable rules.
- To get the details of a specific rule on a specified subscription. This method returns one suppression rule.
- To simulate the impact of a suppression rule still in the design phase. This call identifies which of your existing alerts would have been dismissed if the rule had been active.
DELETE: Deletes an existing rule (but doesn't change the status of alerts already dismissed by it).
For details and usage examples, see the API documentation.
Next step
This article described the suppression rules in Microsoft Defender for Cloud that automatically dismiss unwanted alerts.
Learn more about security alerts generated by Defender for Cloud.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for