If you are experiencing a high number of false or benign positives by trusted infrastructure, you can suppress alerts and create suppression rules by various attributes.
Suppress an alert and create a new suppression rule
Create custom rules to control when alerts are suppressed, or resolved. You can control the context for when an alert is suppressed by specifying the alert title, Indicator of compromise, and the conditions. After specifying the context, you'll be able to configure the action and scope on the alert.
Select the alert you'd like to suppress. This brings up the Alert management pane.
Select Create a suppression rule.
You can create a suppression condition using these attributes. An AND operator is applied between each condition, so suppression occurs only if all conditions are met.
File SHA1
File name - wildcard supported
Folder path - wildcard supported
IP address
URL - wildcard supported
Command line - wildcard supported
Select the Triggering IOC.
Specify the action and scope on the alert.
You can automatically resolve an alert or hide it from the portal. Alerts that are automatically resolved will appear in the resolved section of the alerts queue, alert page, and device timeline and will appear as resolved across Defender for Endpoint APIs.
Alerts that are marked as hidden will be suppressed from the entire system, both on the device's associated alerts and from the dashboard and will not be streamed across Defender for Endpoint APIs.
Enter a rule name and a comment.
Click Save.
View the list of suppression rules
In the navigation pane, select Settings > Alert suppression.
The list of suppression rules shows all the rules that users in your organization have created.