%3CLINGO-SUB%20id%3D%22lingo-sub-1562339%22%20slang%3D%22en-US%22%3EWhat's%20new%3A%20Azure%20Sentinel%20and%20Microsoft%20Defender%20ATP%20improved%20alert%20integration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1562339%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20the%20past%20few%20months%2C%20we%20have%20worked%20on%20an%20improved%20integration%20of%20Microsoft%20Defender%20ATP%20alerts%20into%20Azure%20Sentinel.%20After%20an%20initial%20evaluation%20period%2C%20we%20are%20now%20ready%20to%20gradually%20roll%20out%20the%20new%20solution%20to%20all%20customers.%20The%20new%20integration%20will%20%3CSTRONG%3Ereplace%20%3C%2FSTRONG%3Ethe%20current%20integration%20of%20MDATP%20alerts%20which%20is%20now%20in%20public%20preview%20(see%20details%20below).%20%3CSTRONG%3EThe%20changes%20will%20occur%20automatically%20on%20the%203rd%20of%20August%20and%20require%20no%20configuration%20from%20customers.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CSTRONG%3EImproved%20alert%20details%20and%20context%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EThe%20new%20integration%20has%20significant%20advantages%20in%20improved%20details%20and%20context%2C%20which%20are%20meant%20to%20%3CSTRONG%3Efacilitate%20and%20expedite%20triage%20and%20investigation%20of%20Microsoft%20Defender%20ATP%20incidents%20in%20Azure%20Sentinel.%3C%2FSTRONG%3E%20The%20integration%20will%20provide%20a%20more%20detailed%20view%20of%20each%20alert%20and%20is%20designed%20to%20capture%20changes%20on%20alert%20status%20over%20time.%20The%20upgrades%20include%20increased%20visibility%20into%20investigation%20and%20response%20information%20from%20MDATP%20as%20well%20as%20a%20link%20to%20provide%20an%20easy%20pivot%20to%20see%20the%20alert%20in%20the%20source%20portal.%20Finally%2C%20more%20information%20on%20entities%20is%20provided%20in%20a%20more%20concise%20format%20so%20analysts%20can%20have%20a%20broader%20picture%20of%20the%20involved%20entities.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIt%20is%20important%20to%20note%20that%20the%20new%20integration%20%3CSTRONG%3Edoes%20make%20minor%20changes%20to%20the%20structure%20of%20alerts%20from%20Microsoft%20Defender%20ATP%3C%2FSTRONG%3E.%20A%20summary%20of%20the%20changes%20is%20presented%20below%20(table%201)%3CSPAN%3E%2C%3C%2FSPAN%3E%20and%20a%20full%20description%20of%20the%20changes%2C%20together%20with%20a%20sample%20alert%3CSPAN%3E%2C%3C%2FSPAN%3E%20can%20be%20found%20in%20the%20attached%20file.%20Any%20scheduled%20rules%20that%20use%20one%20of%20the%20changed%20fields%20might%20be%20affected.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CSTRONG%3EA%20new%20MDATP%20API%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EThe%20integration%20is%20based%20on%20the%20newly%20released%20MDATP%20Alerts%20API.%20Details%20on%20the%20new%20API%20can%20be%20found%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fthreat-protection%2Fmicrosoft-defender-atp%2Fget-alerts%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CSTRONG%3EImproved%20discoverability%20of%20the%20Sentinel%20integration%20in%20MDATP%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EThe%20Sentinel%20integration%20is%20now%20exposed%20in%20the%20Partner%20application%20section%20in%20Microsoft%20Defender%20ATP.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Ely_Abramovitch_0-1596446387513.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F209914iA7C0B117D8637BC4%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Ely_Abramovitch_0-1596446387513.png%22%20alt%3D%22Ely_Abramovitch_0-1596446387513.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CSTRONG%3EAdditional%20Resources%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EConnecting%20Microsoft%20Defender%20ATP%20alerts%20to%20Sentinel%20-%20-ERR%3AREF-NOT-FOUND-%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsentinel%2Fconnect-microsoft-defender-advanced-threat-protection%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsentinel%2Fconnect-microsoft-defender-advanced-threat-protection%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EMDATP%20API%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fthreat-protection%2Fmicrosoft-defender-atp%2Fget-alerts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fsecurity%2Fthreat-protection%2Fmicrosoft-defender-atp%2Fget-alerts%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CU%3E%3CSTRONG%3ETable%201%20-%20summary%20of%20the%20alert%20schema%20changes%3C%2FSTRONG%3E%3C%2FU%3E%3C%2FP%3E%0A%3CP%3EThis%20table%20details%20the%20changes%20in%20the%20representation%20of%20MDATP%20alerts%20in%20the%20SecurityAlert%20table%20in%20Azure.%20The%20changes%20are%20in%20comparison%20to%20how%20MDATP%20alerts%20are%20now%20represented%20in%20Sentinel.%20Full%20description%20of%20the%20alert%20can%20be%20found%20in%20the%20attached%20file.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CTABLE%20width%3D%22756%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22331%22%3E%3CP%3E%3CSTRONG%3EDescription%20of%20Change%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22425%22%3E%3CP%3E%3CSTRONG%3ESample%20Alert%20Data%3C%2FSTRONG%3E%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22331%22%3E%3CP%3E%3CSTRONG%3EAdded%3C%2FSTRONG%3E%3A%20ExtendedProperties%20field.%20This%20field%20is%20an%20object%20containing%20the%20following%20details%20from%20MDATP%3A%3CBR%20%2F%3E%3CBR%20%2F%3E-%20MDATP%20category%3CBR%20%2F%3E-%20Investigation%20ID%3CBR%20%2F%3E-%20Investigation%20state%3CBR%20%2F%3E-%20Incident%20ID%3CBR%20%2F%3E-%20Detection%20source%3CBR%20%2F%3E-%20Assigned%20to%3CBR%20%2F%3E-%20Determination%3CBR%20%2F%3E-%20Classification%3CBR%20%2F%3E-%20Action%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22425%22%3E%3CP%3E%7B%3CBR%20%2F%3E%22MicrosoftDefenderAtp.Category%22%3A%20%22SuspiciousActivity%22%2C%3CBR%20%2F%3E%22MicrosoftDefenderAtp.InvestigationId%22%3A%20%2210505%22%2C%3CBR%20%2F%3E%22MicrosoftDefenderAtp.InvestigationState%22%3A%20%22Running%22%2C%3CBR%20%2F%3E%22LastUpdated%22%3A%20%2205%2F25%2F2020%2008%3A09%3A17%22%2C%3CBR%20%2F%3E%22IncidentId%22%3A%20%22135722%22%2C%3CBR%20%2F%3E%22DetectionSource%22%3A%20%22CustomerTI%22%2C%3CBR%20%2F%3E%22AssignedTo%22%3A%20null%2C%3CBR%20%2F%3E%22Determination%22%3A%20null%2C%3CBR%20%2F%3E%22Classification%22%3A%20null%2C%3CBR%20%2F%3E%22Action%22%3A%20%22zavidor%20was%20here%22%3CBR%20%2F%3E%7D%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22331%22%3E%3CP%3E%3CSTRONG%3EReplaced%3C%2FSTRONG%3E%3A%20ExtendedLinks%20field%20%E2%80%93%20The%20new%20AlertLink%20column%20displays%20a%20link%20to%20the%20MDATP%20portal%20for%20each%20alert.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22425%22%3E%3CP%20data-unlink%3D%22true%22%3Ehttps%3A%2F%2Fsecuritycenter.microsoft.com%2Falert%2F%3CBR%20%2F%3E%3CBR%20%2F%3Eda637259909307309588_-1180694960%26nbsp%3B%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22331%22%3E%3CP%3E%3CSTRONG%3ERepurposed%3C%2FSTRONG%3E%3A%20AlertType%20field%20%E2%80%93%20shows%20the%20detection%20source%20(instead%20of%20a%20GUID%20of%20the%20alert%20in%20MDATP)%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22425%22%3E%3CP%3EBefore%3A%20360fdb3b-18a9-471b-9ad0-ad80a4cbcb00%3CBR%20%2F%3EAfter%3A%20CustomerTI%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22331%22%3E%3CP%3E%3CSTRONG%3EExpanded%3C%2FSTRONG%3E%3A%20Entity%20field%20%E2%80%93%20More%20information%20on%20entities%20is%20surfaced.%3CBR%20%2F%3EFor%20example%2C%20the%20host%20entity%20now%20holds%20the%20following%20details%3A%3CBR%20%2F%3E-%20HostName%3CBR%20%2F%3E-%20OSFamily%3CBR%20%2F%3E-%20OSVersion%3CBR%20%2F%3E-%20Type%3CBR%20%2F%3E-%20MdatpDeviceId%3CBR%20%2F%3E-%20FQDN%3CBR%20%2F%3E-%20AadDeviceId%3CBR%20%2F%3E-%20RiskScore%3CBR%20%2F%3E-%20HealthStatus%3CBR%20%2F%3E-%20LastSeen%3CBR%20%2F%3E-%20LastExternalIpAddress%3CBR%20%2F%3E-%20LastIpAddress%3C%2FP%3E%0A%3C%2FTD%3E%0A%3CTD%20width%3D%22425%22%3E%3CP%3E%7B%3CBR%20%2F%3E%22%24id%22%3A%20%223%22%2C%3CBR%20%2F%3E%22HostName%22%3A%20%22real-e2etest-re%22%2C%3CBR%20%2F%3E%22OSFamily%22%3A%20%22Windows%22%2C%3CBR%20%2F%3E%22OSVersion%22%3A%20%221809%22%2C%3CBR%20%2F%3E%22Type%22%3A%20%22host%22%2C%3CBR%20%2F%3E%22MdatpDeviceId%22%3A%20%22e84e634c8c5c2ca10db696cac544ea9ec41e784c%22%2C%3CBR%20%2F%3E%22FQDN%22%3A%20%22real-e2etest-re%22%2C%3CBR%20%2F%3E%22AadDeviceId%22%3A%20null%2C%3CBR%20%2F%3E%22RiskScore%22%3A%20%22Medium%22%2C%3CBR%20%2F%3E%22HealthStatus%22%3A%20%22ActiveDefault%22%2C%3CBR%20%2F%3E%22LastSeen%22%3A%20%222020-05-%3CBR%20%2F%3E25T08%3A06%3A28.5181093Z%22%2C%3CBR%20%2F%3E%22LastExternalIpAddress%22%3A%3CBR%20%2F%3E%2220.185.104.143%22%2C%3CBR%20%2F%3E%22LastIpAddress%22%3A%20%22172.17.53.241%22%3CBR%20%2F%3E%7D%2C%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1562339%22%20slang%3D%22en-US%22%3E%3CP%3EImproved%20alert%20integration%20with%20Microsoft%20Defender%20ATP%20to%26nbsp%3Bfacilitate%20and%20expedite%20triage%20and%20investigation%20of%20MDATP%20incidents%20in%20Azure%20Sentinel.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1562339%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Sentinel%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EDetection%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWhat's%20New%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

In the past few months, we have worked on an improved integration of Microsoft Defender ATP alerts into Azure Sentinel. After an initial evaluation period, we are now ready to gradually roll out the new solution to all customers. The new integration will replace the current integration of MDATP alerts which is now in public preview (see details below). The changes will occur automatically on the 3rd of August and require no configuration from customers.

 

Improved alert details and context

The new integration has significant advantages in improved details and context, which are meant to facilitate and expedite triage and investigation of Microsoft Defender ATP incidents in Azure Sentinel. The integration will provide a more detailed view of each alert and is designed to capture changes on alert status over time. The upgrades include increased visibility into investigation and response information from MDATP as well as a link to provide an easy pivot to see the alert in the source portal. Finally, more information on entities is provided in a more concise format so analysts can have a broader picture of the involved entities.

 

It is important to note that the new integration does make minor changes to the structure of alerts from Microsoft Defender ATP. A summary of the changes is presented below (table 1), and a full description of the changes, together with a sample alert, can be found in the attached file. Any scheduled rules that use one of the changed fields might be affected.

 

A new MDATP API

The integration is based on the newly released MDATP Alerts API. Details on the new API can be found here.

 

Improved discoverability of the Sentinel integration in MDATP

The Sentinel integration is now exposed in the Partner application section in Microsoft Defender ATP.

 

Ely_Abramovitch_0-1596446387513.png

 

Additional Resources

Connecting Microsoft Defender ATP alerts to Sentinel - https://docs.microsoft.com/en-us/azure/sentinel/connect-microsoft-defender-advanced-threat-protectio...

MDATP API - https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/get-alert...

 

Table 1 - summary of the alert schema changes

This table details the changes in the representation of MDATP alerts in the SecurityAlert table in Azure. The changes are in comparison to how MDATP alerts are now represented in Sentinel. Full description of the alert can be found in the attached file.

 

Description of Change

Sample Alert Data

Added: ExtendedProperties field. This field is an object containing the following details from MDATP:

- MDATP category
- Investigation ID
- Investigation state
- Incident ID
- Detection source
- Assigned to
- Determination
- Classification
- Action

{
"MicrosoftDefenderAtp.Category": "SuspiciousActivity",
"MicrosoftDefenderAtp.InvestigationId": "10505",
"MicrosoftDefenderAtp.InvestigationState": "Running",
"LastUpdated": "05/25/2020 08:09:17",
"IncidentId": "135722",
"DetectionSource": "CustomerTI",
"AssignedTo": null,
"Determination": null,
"Classification": null,
"Action": "zavidor was here"
}

Replaced: ExtendedLinks field – The new AlertLink column displays a link to the MDATP portal for each alert.

https://securitycenter.microsoft.com/alert/
da637259909307309588_-1180694960 

Repurposed: AlertType field – shows the detection source (instead of a GUID of the alert in MDATP)

Before: 360fdb3b-18a9-471b-9ad0-ad80a4cbcb00
After: CustomerTI

Expanded: Entity field – More information on entities is surfaced.
For example, the host entity now holds the following details:
- HostName
- OSFamily
- OSVersion
- Type
- MdatpDeviceId
- FQDN
- AadDeviceId
- RiskScore
- HealthStatus
- LastSeen
- LastExternalIpAddress
- LastIpAddress

{
"$id": "3",
"HostName": "real-e2etest-re",
"OSFamily": "Windows",
"OSVersion": "1809",
"Type": "host",
"MdatpDeviceId": "e84e634c8c5c2ca10db696cac544ea9ec41e784c",
"FQDN": "real-e2etest-re",
"AadDeviceId": null,
"RiskScore": "Medium",
"HealthStatus": "ActiveDefault",
"LastSeen": "2020-05-
25T08:06:28.5181093Z",
"LastExternalIpAddress":
"20.185.104.143",
"LastIpAddress": "172.17.53.241"
},