Integrating SIEM + XDR: Azure Sentinel and Azure Defender bi-directional incident sync

Published Jul 26 2021 08:26 AM 6,926 Views
Microsoft

To help defend against today’s evolving threats, SecOps teams need sophisticated tooling that provides both breadth of visibility across the entire enterprise and the depth needed to investigate threats.  At Microsoft, we have a unique vision for the future of threat protection. While other vendors offer only a SIEM or XDR, Microsoft’s perspective is that SecOps can benefit from both. A SIEM delivers visibility into the full kill chain across the entire organization, including third party data, while XDR delivers deeper insights with contextual alerts for multi-cloud and multi-platform resources to reduce false alerts. 

At Microsoft Ignite 2021 in March, we announced an important step in bringing you the most integrated SIEM and XDR on the market with the release of incident sharing between Microsoft 365 Defender and Azure Sentinel.  Today, we are continuing the journey by announcing the public preview of incident sharing for Azure Defender and Azure Sentinel.  Now, Microsoft delivers the only integrated SIEM and XDR with incident sharing across the full set of components.

Using this new capability, customers can use Azure Sentinel as their single pane of glass for incident triage, leverage Microsoft 365 Defender or Azure Defender for incident investigation and remediation, and stay seamlessly in-sync across all three products. This new capability helps reduce the overall time you spend on responding to incidents – giving you more time to focus on what’s important.

 

How does it work?

Azure Defender & Sentinel bi-directional status sync will automatically sync alerts and incidents statuses between the products:

  • Closing or updating incidents in Azure Sentinel containing Azure Defender alerts will automatically close/update the status of the alert in the Azure Defender portal.
  • Alerts closed in the Azure Defender will be reflected as closed in Sentinel, but the status of the incident containing them will remain unchanged.

 

How to enable it?

  1. In Azure Sentinel, navigate to the data connectors tab and open the Azure Defender data connector.
  2. You can configure on which subscriptions you would like the bi-directional sync to take effect by changing the drop down in the “Bi-directional sync (Preview)” column to “Enabled”.
    1. Notice – enabling bi-directional sync required contributor permission in the selected subscription.
  3. To enable bi-directional sync on several subscriptions at once, mark their check boxes and select the “Enable bi-directional sync” button on the bar above the list.

 

ScottWoodgate_0-1627312328936.png

 

We are excited about these new capabilities and will continue our mission to help you protect your companies.  Stay tuned for more SIEM and XDR integration!

 

Further reading

2 Comments
Senior Member

Great news for such a very important integration.

 

The question here is: "Does the bi-directional sync between ASC-Sentinel affect all ASC alert types?"
After testing, we have noticed that we are not able to get all the ASC alerts dismissed after closing the corresponding Azure Sentinel Incidents. For example, we observed that some ASC alerts related to "Non-Azure resources" (e.g alerts related with Azure-Arc enabled servers) were not closing (status not changed to "Dismissed") after closing an Azure Sentinel Incident.

 

Can you confirm the above issue or it something that happens due to the feature is currently in PREVIEW mode?

 

Thank you very much.

Greg

Microsoft

Hi Greg,

Thanks for your feedback.

 

The feature should work for all alerts. Would appreciate if you can open support ticket with the exact information of the issue you encountered and we will work to resolve it.

 

Thank,

Tal Rosler,

Product Manager - Azure Defender

%3CLINGO-SUB%20id%3D%22lingo-sub-2587343%22%20slang%3D%22en-US%22%3EIntegrating%20SIEM%20%2B%20XDR%3A%20Azure%20Sentinel%20and%20Azure%20Defender%20bi-directional%20incident%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2587343%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20help%20defend%20%3CSPAN%3Eagainst%20today%E2%80%99s%20evolving%20%3C%2FSPAN%3Ethreats%3CSPAN%3E%2C%3C%2FSPAN%3E%20SecOps%20team%3CSPAN%3Es%3C%2FSPAN%3E%20need%20%3CSPAN%3Esophisticated%20%3C%2FSPAN%3Etooling%20that%3CSPAN%3E%20provides%20both%20breadth%3C%2FSPAN%3E%3CSPAN%3E%20of%20visibility%20across%20the%20entire%20enterprise%3C%2FSPAN%3E%3CSPAN%3E%20and%3C%2FSPAN%3E%3CSPAN%3E%20the%3C%2FSPAN%3E%3CSPAN%3E%20depth%3C%2FSPAN%3E%3CSPAN%3E%20needed%20to%20investigate%20threats%3C%2FSPAN%3E%3CSPAN%3E.%3C%2FSPAN%3E%26nbsp%3B%20%3CSPAN%3EAt%20Microsoft%2C%20we%20have%20a%20unique%20vision%20for%20the%20future%20of%20threat%20protection.%20%3C%2FSPAN%3EWhile%20other%20vendors%20offer%20only%20a%20SIEM%20%3CSPAN%3Eor%20%3C%2FSPAN%3EXDR%2C%20Microsoft%3CSPAN%3E%E2%80%99s%3C%2FSPAN%3E%20perspective%20is%20that%20SecOps%20can%20benefit%20from%20both.%20A%20SIEM%20delivers%20visibility%20into%20the%20full%20kill%20chain%3CSPAN%3E%20across%20the%20entire%20organization%2C%3C%2FSPAN%3E%20including%20third%20party%20data%3CSPAN%3E%2C%20%3C%2FSPAN%3E%3CSPAN%3Ewhile%20%3C%2FSPAN%3EXDR%20delivers%20%3CSPAN%3Edeeper%20%3C%2FSPAN%3Einsights%3CSPAN%3E%20with%20%3C%2FSPAN%3Econtextual%20alerts%20for%20multi-cloud%20and%20multi-platform%20resources%20to%20reduce%20false%20alerts.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAt%20%3C%2FSPAN%3E%3CSPAN%3EMicrosoft%20Ignite%202021%20i%3C%2FSPAN%3E%3CSPAN%3En%3C%2FSPAN%3E%3CSPAN%3E%20March%3C%2FSPAN%3E%3CSPAN%3E%2C%3C%2FSPAN%3E%20we%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fazure-sentinel%2Fmicrosoft-ignite-2021-what-s-new-in-azure-sentinel%2Fba-p%2F2175225%22%20target%3D%22_blank%22%3Eannounced%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%3E%20an%20important%20step%20in%20bringing%20you%20the%20most%20integrated%20SIEM%20and%20XDR%20on%20the%20market%20with%20the%20release%20of%3C%2FSPAN%3E%20incident%20sharing%20%3CSPAN%3Ebetween%20%3C%2FSPAN%3EMicrosoft%20365%20Defender%20and%20Azure%20Sentinel.%26nbsp%3B%20Today%3CSPAN%3E%2C%3C%2FSPAN%3E%20we%20are%20%3CSPAN%3Econtinuing%20the%20journey%20%3C%2FSPAN%3E%3CSPAN%3Eby%20%3C%2FSPAN%3Eannouncing%20the%20public%20preview%20of%20incident%20sharing%20for%20Azure%20Defender%20and%20Azure%20Sentinel.%26nbsp%3B%20%3CSPAN%3ENow%2C%20%3C%2FSPAN%3EMicrosoft%20delivers%20the%20only%20integrated%20SIEM%20and%20XDR%20with%20incident%20sharing%20across%20the%20full%20set%20of%20components.%3C%2FP%3E%0A%3CP%3EUsing%20this%20new%20capability%2C%20customers%20can%20use%20Azure%20Sentinel%20as%20their%20single%20pane%20of%20glass%20for%20incident%20triage%2C%20leverage%20Microsoft%20365%20Defender%20or%20Azure%20Defender%20for%20incident%20investigation%20and%20remediation%3CSPAN%3E%2C%3C%2FSPAN%3E%20and%20%3CSPAN%3E%20stay%20seamlessly%20in-sync%20across%20all%20three%20products%3C%2FSPAN%3E.%20This%20%3CSPAN%3Enew%20capability%20%3C%2FSPAN%3Ehelps%20reduce%20the%20overall%20time%20you%20spend%20on%20responding%20to%20incidents%20%E2%80%93%20giving%20you%20more%20time%20to%20focus%20on%20what%E2%80%99s%20important.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-1390104980%22%20id%3D%22toc-hId-1390104980%22%20id%3D%22toc-hId-1390104980%22%20id%3D%22toc-hId-1390104980%22%20id%3D%22toc-hId-1390104980%22%20id%3D%22toc-hId-1390104980%22%3EHow%20does%20it%20work%3F%3C%2FH1%3E%0A%3CP%3EAzure%20Defender%20%26amp%3B%20Sentinel%20bi-directional%20status%20sync%20will%20automatically%20sync%20alerts%20and%20incidents%20statuses%20between%20the%20products%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EClosing%20or%20updating%20incidents%20in%20Azure%20Sentinel%20containing%20Azure%20Defender%20alerts%20will%20automatically%20close%2Fupdate%20the%20status%20of%20the%20alert%20in%20the%20Azure%20Defender%20portal.%3C%2FLI%3E%0A%3CLI%3EAlerts%20closed%20in%20the%20Azure%20Defender%20will%20be%20reflected%20as%20closed%20in%20Sentinel%2C%20but%20the%20status%20of%20the%20incident%20containing%20them%20will%20remain%20unchanged.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId--417349483%22%20id%3D%22toc-hId--417349483%22%20id%3D%22toc-hId--417349483%22%20id%3D%22toc-hId--417349483%22%20id%3D%22toc-hId--417349483%22%20id%3D%22toc-hId--417349483%22%3EHow%20to%20enable%20it%3F%3C%2FH1%3E%0A%3COL%3E%0A%3CLI%3EIn%20Azure%20Sentinel%2C%20navigate%20to%20the%20data%20connectors%20tab%20and%20open%20the%20Azure%20Defender%20data%20connector.%3C%2FLI%3E%0A%3CLI%3EYou%20can%20configure%20on%20which%20subscriptions%20you%20would%20like%20the%20bi-directional%20sync%20to%20take%20effect%20by%20changing%20the%20drop%20down%20in%20the%20%E2%80%9CBi-directional%20sync%20(Preview)%E2%80%9D%20column%20to%20%E2%80%9CEnabled%E2%80%9D.%3COL%3E%0A%3CLI%3ENotice%20%E2%80%93%20enabling%20bi-directional%20sync%20required%20%3CSTRONG%3Econtributor%3C%2FSTRONG%3E%20permission%20in%20the%20selected%20subscription.%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3C%2FLI%3E%0A%3CLI%3ETo%20enable%20bi-directional%20sync%20on%20several%20subscriptions%20at%20once%2C%20mark%20their%20check%20boxes%20and%20select%20the%20%E2%80%9CEnable%20bi-directional%20sync%E2%80%9D%20button%20on%20the%20bar%20above%20the%20list.%3C%2FLI%3E%0A%3C%2FOL%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%22ScottWoodgate_0-1627312328936.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F298375i60E2615E0E6BD7C6%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22ScottWoodgate_0-1627312328936.png%22%20alt%3D%22ScottWoodgate_0-1627312328936.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20excited%20about%20these%20new%20capabilities%20and%20will%20continue%20our%20mission%20to%20help%20you%20protect%20your%20companies.%26nbsp%3B%20Stay%20tuned%20for%20more%20SIEM%20and%20XDR%20integration!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId-2070163350%22%20id%3D%22toc-hId-2070163350%22%20id%3D%22toc-hId-2070163350%22%20id%3D%22toc-hId-2070163350%22%20id%3D%22toc-hId-2070163350%22%20id%3D%22toc-hId-2070163350%22%3EFurther%20reading%3C%2FH1%3E%0A%3CUL%3E%0A%3CLI%3EOfficial%20Azure%20Sentinel%20documentation%20-%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsentinel%2Fconnect-azure-security-center%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsentinel%2Fconnect-azure-security-center%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsecurity-center%2Fexport-to-siem%23stream-alerts-to-azure-sentinel%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fsecurity-center%2Fexport-to-siem%23stream-alerts-to-azure-sentinel%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2587343%22%20slang%3D%22en-US%22%3E%3CP%3EAzure%20Sentinel%20and%20Azure%20Defender%20now%20share%20the%20concept%20of%20an%20incident.%20This%20new%20capability%20enables%20you%20to%20update%20or%20close%20Azure%20Defender%20incidents%20from%20within%20Azure%20Sentinel%20and%20complements%20a%20similar%20feature%20already%20available%20for%20Microsoft%20365%20Defender%20incidents%20and%20Azure%20Sentinel%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2587343%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Defender%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Sentinel%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHunting%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2593625%22%20slang%3D%22en-US%22%3ERe%3A%20Integrating%20SIEM%20%2B%20XDR%3A%20Azure%20Sentinel%20and%20Azure%20Defender%20bi-directional%20incident%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2593625%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Greg%2C%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20feedback.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20feature%20should%20work%20for%20all%20alerts.%20Would%20appreciate%20if%20you%20can%20open%20support%20ticket%20with%20the%20exact%20information%20of%20the%20issue%20you%20encountered%20and%20we%20will%20work%20to%20resolve%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%2C%3C%2FP%3E%0A%3CP%3ETal%20Rosler%2C%3C%2FP%3E%0A%3CP%3EProduct%20Manager%20-%20Azure%20Defender%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2590482%22%20slang%3D%22en-US%22%3ERe%3A%20Integrating%20SIEM%20%2B%20XDR%3A%20Azure%20Sentinel%20and%20Azure%20Defender%20bi-directional%20incident%20sync%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2590482%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20news%20for%20such%20a%20very%20important%20integration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20question%20here%20is%3A%20%22Does%20the%20bi-directional%20sync%20between%20ASC-Sentinel%20affect%20all%20ASC%20alert%20types%3F%22%3CBR%20%2F%3EAfter%20testing%2C%20we%20have%20noticed%20that%20we%20are%20not%20able%20to%20get%20all%20the%20ASC%20alerts%20dismissed%20after%20closing%20the%20corresponding%20Azure%20Sentinel%20Incidents.%20For%20example%2C%20we%20observed%20that%20some%20ASC%20alerts%20related%20to%20%22Non-Azure%20resources%22%20(e.g%20alerts%20related%20with%20Azure-Arc%20enabled%20servers)%20were%20not%20closing%20(status%20not%20changed%20to%20%22Dismissed%22)%20after%20closing%20an%20Azure%20Sentinel%20Incident.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20confirm%20the%20above%20issue%20or%20it%20something%20that%20happens%20due%20to%20the%20feature%20is%20currently%20in%20PREVIEW%20mode%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20very%20much.%3C%2FP%3E%3CP%3EGreg%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jul 26 2021 10:24 AM
Updated by:
www.000webhost.com