Alerts and incidents in Microsoft Defender XDR
Microsoft Defender for Cloud is now integrated with Microsoft Defender XDR. This integration allows security teams to access Defender for Cloud alerts and incidents within the Microsoft Defender Portal. This integration provides richer context to investigations that span cloud resources, devices, and identities.
The partnership with Microsoft Defender XDR allows security teams to get the complete picture of an attack, including suspicious and malicious events that happen in their cloud environment. Security teams can accomplish this goal through immediate correlations of alerts and incidents.
Microsoft Defender XDR offers a comprehensive solution that combines protection, detection, investigation, and response capabilities. The solution protects against attacks on devices, email, collaboration, identity, and cloud apps. Our detection and investigation capabilities are now extended to cloud entities, offering security operations teams a single pane of glass to significantly improve their operational efficiency.
Incidents and alerts are now part of Microsoft Defender XDR's public API. This integration allows exporting of security alerts data to any system using a single API. As Microsoft Defender for Cloud, we're committed to providing our users with the best possible security solutions, and this integration is a significant step towards achieving that goal.
Investigation experience in Microsoft Defender XDR
The following table describes the detection and investigation experience in Microsoft Defender XDR with Defender for Cloud alerts.
|All Defender for Cloud incidents are integrated to Microsoft Defender XDR.
- Searching for cloud resource assets in the incident queue is supported.
- The attack story graph shows cloud resource.
- The assets tab in an incident page shows the cloud resource.
- Each virtual machine has its own entity page containing all related alerts and activity.
There are no duplications of incidents from other Defender workloads.
|All Defender for Cloud alerts, including multicloud, internal and external providers’ alerts, are integrated to Microsoft Defender XDR. Defenders for Cloud alerts show on the Microsoft Defender XDR alert queue.
Microsoft Defender XDR
cloud resource asset shows up in the Asset tab of an alert. Resources are clearly identified as an Azure, Amazon, or a Google Cloud resource.
Defenders for Cloud alerts are automatically be associated with a tenant.
There are no duplications of alerts from other Defender workloads.
|Alert and incident correlation
|Alerts and incidents are automatically correlated, providing robust context to security operations teams to understand the complete attack story in their cloud environment.
|Accurate matching of virtual entities to device entities to ensure precision and effective threat detection.
|Defender for Cloud alerts and incidents are now included in Microsoft Defender XDR’s public API, allowing customers to export their security alerts data into other systems using one API.
Learn more about handling alerts in Microsoft Defender XDR.
Microsoft Sentinel customers can benefit from the Defender for Cloud integration with Microsoft 365 Defender in their workspaces using the Microsoft 365 Defender incidents and alerts connector.
First you need to enabled incident integration in your Microsoft 365 Defender connector.
Then, enable the
Tenant-based Microsoft Defender for Cloud (Preview) connector to synchronize your subscriptions with your tenant-based Defender for Cloud incidents to stream through the Microsoft 365 Defender incidents connector.
The connector is available through the Microsoft Defender for Cloud solution, version 3.0.0, in the Content Hub. If you have an earlier version of this solution, you can upgrade it in the Content Hub.
If you have the legacy subscription-based Microsoft Defender for Cloud alerts connector enabled (which is displayed as
Subscription-based Microsoft Defender for Cloud (Legacy)), we recommend you disconnect the connector in order to prevent duplicating alerts in your logs.
We recommend you disable analytic rules that are enabled (either scheduled or through Microsoft creation rules), from creating incidents from your Defender for Cloud alerts.
You can use automation rules to close incidents immediately and prevent specific types of Defender for Cloud alerts from becoming incidents. You can also use the built-in tuning capabilities in the Microsoft 365 Defender portal to prevent alerts from becoming incidents.
Customers who integrated their Microsoft 365 Defender incidents into Sentinel and want to keep their subscription-based settings and avoid tenant-based syncing can opt out of syncing incidents and alerts through the Microsoft 365 Defender connector.