Microsoft Defender for Cloud data security
To help customers prevent, detect, and respond to threats, Microsoft Defender for Cloud collects and processes security-related data, including configuration information, metadata, event logs, and more. Microsoft adheres to strict compliance and security guidelines—from coding to operating a service.
This article explains how data is managed and safeguarded in Defender for Cloud.
Defender for Cloud analyzes data from the following sources to provide visibility into your security state, identify vulnerabilities and recommend mitigations, and detect active threats:
- Azure services: Uses information about the configuration of Azure services you have deployed by communicating with that service’s resource provider.
- Network traffic: Uses sampled network traffic metadata from Microsoft’s infrastructure, such as source/destination IP/port, packet size, and network protocol.
- Partner solutions: Uses security alerts from integrated partner solutions, such as firewalls and antimalware solutions.
- Your machines: Uses configuration details and information about security events, such as Windows event and audit logs, and syslog messages from your machines.
When you enable Defender for Storage Malware Scanning, it might share metadata, including metadata classified as customer data (e.g. SHA-256 hash), with Microsoft Defender for Endpoint.
Data is kept logically separate on each component throughout the service. All data is tagged per organization. This tagging persists throughout the data lifecycle, and it's enforced at each layer of the service.
To provide security recommendations and investigate potential security threats, Microsoft personnel might access information collected or analyzed by Azure services, including process creation events, and other artifacts, which might unintentionally include customer data or personal data from your machines.
We adhere to the Microsoft Online Services Data Protection Addendum, which states that Microsoft won't use Customer Data or derive information from it for any advertising or similar commercial purposes. We only use Customer Data as needed to provide you with Azure services, including purposes compatible with providing those services. You retain all rights to Customer Data.
Microsoft uses patterns and threat intelligence seen across multiple tenants to enhance our prevention and detection capabilities; we do so in accordance with the privacy commitments described in our Privacy Statement.
Manage data collection from machines
When you enable Defender for Cloud in Azure, data collection is turned on for each of your Azure subscriptions. You can also enable data collection for your subscriptions in Defender for Cloud. When data collection is enabled, Defender for Cloud provisions the Log Analytics agent on all existing supported Azure virtual machines and any new ones that are created.
The Log Analytics agent scans for various security-related configurations and events it into Event Tracing for Windows (ETW) traces. In addition, the operating system raises event log events during the course of running the machine. Examples of such data are: operating system type and version, operating system logs (Windows event logs), running processes, machine name, IP addresses, logged in user, and tenant ID. The Log Analytics agent reads event log entries and ETW traces and copies them to your workspace(s) for analysis. The Log Analytics agent also enables process creation events and command line auditing.
If you aren't using Microsoft Defender for Cloud's enhanced security features, you can also disable data collection from virtual machines in the Security Policy. Data Collection is required for subscriptions that are protected by enhanced security features. VM disk snapshots and artifact collection will still be enabled even if data collection has been disabled.
You can specify the workspace and region where data collected from your machines is stored. The default is to store data collected from your machines in the nearest workspace as shown in the following table:
|VM Geo||Workspace Geo|
|United States, Brazil, South Africa||United States|
|Europe (excluding United Kingdom)||Europe|
|United Kingdom||United Kingdom|
|Asia (excluding India, Japan, Korea, China)||Asia Pacific|
Microsoft Defender for Storage stores artifacts regionally according to the location of the related Azure resource. Learn more in Overview of Microsoft Defender for Storage.
Customers can access Defender for Cloud related data from the following data streams:
|Azure Activity log||All security alerts, approved Defender for Cloud just-in-time access requests, and all alerts generated by adaptive application controls.|
|Azure Monitor logs||All security alerts.|
|Azure Resource Graph||Security alerts, security recommendations, vulnerability assessment results, secure score information, status of compliance checks, and more.|
|Microsoft Defender for Cloud REST API||Security alerts, security recommendations, and more.|
If there are no Defender plans enabled on the subscription, data will be removed from Azure Resource Graph after 30 days of inactivity in the Microsoft Defender for Cloud portal. After interaction with artifacts in the portal related to the subscription, the data should be visible again within 24 hours.
Defender for Cloud and Microsoft Defender 365 Defender integration
When you enable any of Defender for Cloud's paid plans you automatically gain all of the benefits of Microsoft Defender XDR. Information from Defender for Cloud will be shared with Microsoft Defender XDR. This data may contain customer data and will be stored according to Microsoft 365 data handling guidelines.
In this document, you learned how data is managed and safeguarded in Microsoft Defender for Cloud.
To learn more about Microsoft Defender for Cloud, see What is Microsoft Defender for Cloud?.