Making the SecOps Team More Efficient - Focused Email Actions

Published Jul 19 2021 08:30 AM 2,597 Views
Microsoft

This post was authored by @johnengels, a Senior Program Manager from the Microsoft Defender for Office 365 team.

 

This blog is part one of a multi-part series focused on the new and improved incident response capabilities within Microsoft Defender for Office 365.

 

Security operations (SecOps) teams frequently need to investigate security alerts associated with emails and online interaction.  Critical to this is ensuring that malicious emails associated with a likely attack are fully removed from all mailboxes – plus verifying no users or mailboxes have been compromised through interaction with any delivered emails.  These days, the attack methods used by malicious actors, along with the high volume of email they send out, ensures that SecOps team are always busy with this task.

 

Earlier in May 2021, we announced that Microsoft is positioned as a leader in The Forrester Wave™: Email Security, Q2 2021, receiving the highest possible score in the incident response category. This represents the latest validation of our relentless effort, strategy, and focus on offering our customers industry-leading protection against threats orchestrated over email and collaboration tools – and of course industry-leading incident response capabilities.

 

 

Microsoft Defender for Office 365 is now rolling out three email investigation improvements that will drive additional SecOps efficiencies. The following changes will directly reduce the volume and prioritize the most malicious automated investigations for SecOps approval:

  • Email actions are created only when malicious emails’ latest delivery location is in a cloud mailbox
  • Pending email actions are updated based on the latest delivery location
  • Investigations prioritize the most malicious threats for action

 

Email actions are created only when malicious emails’ latest delivery location is in a cloud mailbox

Previously automated investigations in Defender for Office 365 leveraged ‘original delivery information’ to identify emails that needed cleanup.  This provided a view of emails that were initially visible to end users with recommendations on emails that should be removed.  With this change, we are now pivoting the investigation email clustering analysis to the ‘latest delivery location’ information.  As a result, investigations for things like Zero-hour auto purge (ZAP) or user submissions will show malicious emails that are still present in inbox or junk folders at the time of the investigation still in need of removal.  The email location information for emails and email clusters will clearly show the latest delivery location and number of emails ‘in mailbox’, ‘not in mailbox’ (i.e. blocked or remediated), and ‘on-premise/external’ (inaccessible to Defender for Office 365’s remediation).  Most importantly, to reduce SecOps work, the email analysis will now only trigger pending email actions when the emails are considered malicious and at least one email still in a cloud ‘mailbox’.

 

The latest delivery location and action changes that are currently rolling out apply to both the original emails that triggered the alerts as well as identified email clusters for similar emails and malicious URLs and files.  The net effect of these changes is that you’ll see more current location information with fewer email actions required, particularly for ZAP alert investigations.  After this change, if you see pending email actions for ZAP investigations, you should review and approve those actions to remove any residual email threats that remain.

 

Figure 1: Investigation email cluster has no items still in the mailbox, therefore the threat has been prevented and has no pending actionFigure 1: Investigation email cluster has no items still in the mailbox, therefore the threat has been prevented and has no pending action

 

 

Pending actions are updated based on the latest delivery location

The Defender for Office 365 team is also improving investigations to re-analyze the email status after the investigation has completed.  Until an investigation’s actions are approved or rejected, the investigation will periodically re-evaluate the investigation’s email findings and actions against the latest delivery locations then update the remediation status. This updates the investigation’s findings and the pending actions based on the latest remediations from ZAP, manual admin actions, as well as other approved automated investigations actions.  If all malicious emails with pending actions have been removed from the mailboxes, the actions will cancel, with the incident and action center showing the emails as remediated (with updated location information).  If all the investigation’s email actions have been completed by other remediations, then the investigation will change to ‘remediated’, and the original alerts will close.

 

Investigations prioritize the most malicious threats for action

Investigations are also being updated to surface to SecOps personnel the most relevant threats, helping ensure they are given sufficient attention and that actions are driving critical containment activities. 

  • First, the investigation’s email analysis is changing to use the latest Defender for Office 365 threat categories: malware, high-confidence phishing, normal phishing, and spam.  This provides security teams with the ability to focus on the most critical malicious threats included in the investigation (high confidence, e.g. a credential theft URL) vs. items that are simply suspicious.  It also ensures that comparing investigations to threat explorer or advanced hunting data provides more consistent results in terms of threat types.
  • A second improvement is that investigations only create recommended actions for emails and email clusters determined to be the most critical threats: malware, high-confidence phishing, malicious URLs and malicious files.  This further reduces SecOps workloads –by focusing valuable time and actions on malicious emails.

 

Figure 2: This email cluster evidence has an action because it’s malicious high-confidence phishing, with emails remaining in the mailbox.Figure 2: This email cluster evidence has an action because it’s malicious high-confidence phishing, with emails remaining in the mailbox.

 

 

 

Figure 3: In cases where email clusters only have suspicious items like the spam and normal phish cluster in the example above, the automated investigation will no longer queue a pending action.  Only malicious items in mailboxes get actions.Figure 3: In cases where email clusters only have suspicious items like the spam and normal phish cluster in the example above, the automated investigation will no longer queue a pending action.  Only malicious items in mailboxes get actions.

 

 


Coming up in Part 2...

In this blog, we talked about the new email analysis improvements in Defender for Office 365 investigations and how they will improve SecOps efficiencies.  The new threat types, latest delivery locations, and updates after investigation completion ensure that SecOps teams get clearer threat data, more accurate and recent location information, plus fewer and more focused actions. In the next blog post, we will hear from some of our closest partners leveraging these capabilities in Microsoft Defender for Office 365 to help efficiently and effectively detect and respond to threats. Stay tuned! 

 

 

Do you have questions or feedback about Microsoft Defender for Office 365? Engage with the community and Microsoft experts in the Defender for Office 365 forum.

%3CLINGO-SUB%20id%3D%22lingo-sub-2557387%22%20slang%3D%22en-US%22%3EMaking%20the%20SecOps%20Team%20More%20Efficient%20-%20Focused%20Email%20Actions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2557387%22%20slang%3D%22en-US%22%3E%3CH4%20id%3D%22toc-hId--598887991%22%20id%3D%22toc-hId-291447759%22%20id%3D%22toc-hId-292226875%22%3E%3CFONT%20size%3D%223%22%3EThis%20post%20was%20authored%20by%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F758148%22%20target%3D%22_blank%22%3E%40johnengels%3C%2FA%3E%2C%20a%20Senior%20Program%20Manager%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Efrom%20the%20Microsoft%20Defender%20for%20Office%20365%20team.%3C%2FFONT%3E%3C%2FH4%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3EThis%20blog%20is%20part%20one%20of%20a%20multi-part%20series%20focused%20on%20the%20new%20and%20improved%20incident%20response%20capabilities%20within%20Microsoft%20Defender%20for%20Office%20365.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESecurity%20operations%20(SecOps)%20teams%20frequently%20need%20to%20investigate%20security%20alerts%20associated%20with%20emails%20and%20online%20interaction.%26nbsp%3B%20Critical%20to%20this%20is%20ensuring%20that%20malicious%20emails%20associated%20with%20a%20likely%20attack%20are%20fully%20removed%20from%20all%20mailboxes%20%E2%80%93%20plus%20verifying%20no%20users%20or%20mailboxes%20have%20been%20compromised%20through%20interaction%20with%20any%20delivered%20emails.%26nbsp%3B%20These%20days%2C%20the%20attack%20methods%20used%20by%20malicious%20actors%2C%20along%20with%20the%20high%20volume%20of%20email%20they%20send%20out%2C%20ensures%20that%20SecOps%20team%20are%20always%20busy%20with%20this%20task.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEarlier%20in%20May%202021%2C%20we%20announced%20that%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Femailwave%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20is%20positioned%20as%20a%20leader%3C%2FA%3E%20in%20The%20Forrester%20Wave%E2%84%A2%3A%20Email%20Security%2C%20Q2%202021%2C%20receiving%20the%20highest%20possible%20score%20in%20the%20incident%20response%20category.%20This%20represents%20the%20latest%20validation%20of%20our%20relentless%20effort%2C%20strategy%2C%20and%20focus%20on%20offering%20our%20customers%20industry-leading%20protection%20against%20threats%20orchestrated%20over%20email%20and%20collaboration%20tools%20%E2%80%93%20and%20of%20course%20industry-leading%20incident%20response%20capabilities.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMicrosoft%20Defender%20for%20Office%20365%20is%20now%20rolling%20out%20three%20email%20investigation%20improvements%20that%20will%20drive%20additional%20SecOps%20efficiencies.%20The%20following%20changes%20will%20directly%20reduce%20the%20volume%20and%20prioritize%20the%20most%20malicious%20automated%20investigations%20for%20SecOps%20approval%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EEmail%20actions%20are%20created%20only%20when%20malicious%20emails%E2%80%99%20latest%20delivery%20location%20is%20in%20a%20cloud%20mailbox%3C%2FLI%3E%0A%3CLI%3EPending%20email%20actions%20are%20updated%20based%20on%20the%20latest%20delivery%20location%3C%2FLI%3E%0A%3CLI%3EInvestigations%20prioritize%20the%20most%20malicious%20threats%20for%20action%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-2077896014%22%20id%3D%22toc-hId-2078675130%22%3E%3CSPAN%3EEmail%20actions%20are%20created%20only%20when%20malicious%20emails%E2%80%99%20latest%20delivery%20location%20is%20in%20a%20cloud%3C%2FSPAN%3E%20%3CSPAN%3Emailbox%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%3EPreviously%20automated%20investigations%20in%20Defender%20for%20Office%20365%20leveraged%20%E2%80%98original%20delivery%20information%E2%80%99%20to%20identify%20emails%20that%20needed%20cleanup.%26nbsp%3B%20This%20provided%20a%20view%20of%20emails%20that%20were%20initially%20visible%20to%20end%20users%20with%20recommendations%20on%20emails%20that%20should%20be%20removed.%26nbsp%3B%20With%20this%20change%2C%20we%20are%20now%20pivoting%20the%20investigation%20email%20clustering%20analysis%20to%20the%20%E2%80%98latest%20delivery%20location%E2%80%99%20information.%26nbsp%3B%20As%20a%20result%2C%20investigations%20for%20things%20like%20Zero-hour%20auto%20purge%20(ZAP)%20or%20user%20submissions%20will%20show%20malicious%20emails%20that%20are%20still%20present%20in%20inbox%20or%20junk%20folders%20at%20the%20time%20of%20the%20investigation%20still%20in%20need%20of%20removal.%26nbsp%3B%20The%20email%20location%20information%20for%20emails%20and%20email%20clusters%20will%20clearly%20show%20the%20latest%20delivery%20location%20and%20number%20of%20emails%20%E2%80%98in%20mailbox%E2%80%99%2C%20%E2%80%98not%20in%20mailbox%E2%80%99%20(i.e.%20blocked%20or%20remediated)%2C%20and%20%E2%80%98on-premise%2Fexternal%E2%80%99%20(inaccessible%20to%20Defender%20for%20Office%20365%E2%80%99s%20remediation).%26nbsp%3B%20Most%20importantly%2C%20to%20reduce%20SecOps%20work%2C%20the%20email%20analysis%20will%20now%20only%20trigger%20pending%20email%20actions%20when%20the%20emails%20are%20considered%20malicious%20and%20at%20least%20one%20email%20still%20in%20a%20cloud%20%E2%80%98mailbox%E2%80%99.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20latest%20delivery%20location%20and%20action%20changes%20that%20are%20currently%20rolling%20out%20apply%20to%20both%20the%20original%20emails%20that%20triggered%20the%20alerts%20as%20well%20as%20identified%20email%20clusters%20for%20similar%20emails%20and%20malicious%20URLs%20and%20files.%26nbsp%3B%20The%20net%20effect%20of%20these%20changes%20is%20that%20you%E2%80%99ll%20see%20more%20current%20location%20information%20with%20fewer%20email%20actions%20required%2C%20particularly%20for%20ZAP%20alert%20investigations.%26nbsp%3B%20After%20this%20change%2C%20if%20you%20see%20pending%20email%20actions%20for%20ZAP%20investigations%2C%20you%20should%20review%20and%20approve%20those%20actions%20to%20remove%20any%20residual%20email%20threats%20that%20remain.%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%22GiulianGarruba_0-1626463685139.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F296478i612C3DC3DD617279%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22GiulianGarruba_0-1626463685139.png%22%20alt%3D%22Figure%201%3A%20Investigation%20email%20cluster%20has%20no%20items%20still%20in%20the%20mailbox%2C%20therefore%20the%20threat%20has%20been%20prevented%20and%20has%20no%20pending%20action%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%201%3A%20Investigation%20email%20cluster%20has%20no%20items%20still%20in%20the%20mailbox%2C%20therefore%20the%20threat%20has%20been%20prevented%20and%20has%20no%20pending%20action%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-270441551%22%20id%3D%22toc-hId-271220667%22%3EPending%20actions%20are%20updated%20based%20on%20the%20latest%20delivery%20location%3C%2FH2%3E%0A%3CP%3EThe%20Defender%20for%20Office%20365%20team%20is%20also%20improving%20investigations%20to%20re-analyze%20the%20email%20status%20%3CEM%3Eafter%3C%2FEM%3E%20the%20investigation%20has%20completed.%26nbsp%3B%20Until%20an%20investigation%E2%80%99s%20actions%20are%20approved%20or%20rejected%2C%20the%20investigation%20will%20periodically%20re-evaluate%20the%20investigation%E2%80%99s%20email%20findings%20and%20actions%20against%20the%20latest%20delivery%20locations%20then%20update%20the%20remediation%20status.%20This%20updates%20the%20investigation%E2%80%99s%20findings%20and%20the%20pending%20actions%20based%20on%20the%20latest%20remediations%20from%20ZAP%2C%20manual%20admin%20actions%2C%20as%20well%20as%20other%20approved%20automated%20investigations%20actions.%26nbsp%3B%20If%20all%20malicious%20emails%20with%20pending%20actions%20have%20been%20removed%20from%20the%20mailboxes%2C%20the%20actions%20will%20cancel%2C%20with%20the%20incident%20and%20action%20center%20showing%20the%20emails%20as%20remediated%20(with%20updated%20location%20information).%26nbsp%3B%20If%20all%20the%20investigation%E2%80%99s%20email%20actions%20have%20been%20completed%20by%20other%20remediations%2C%20then%20the%20investigation%20will%20change%20to%20%E2%80%98remediated%E2%80%99%2C%20and%20the%20original%20alerts%20will%20close.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--1537012912%22%20id%3D%22toc-hId--1536233796%22%3EInvestigations%20prioritize%20the%20most%20malicious%20threats%20for%20action%3C%2FH2%3E%0A%3CP%3EInvestigations%20are%20also%20being%20updated%20to%20surface%20to%20SecOps%20personnel%20the%20most%20relevant%20threats%2C%20helping%20ensure%20they%20are%20given%20sufficient%20attention%20and%20that%20actions%20are%20driving%20critical%20containment%20activities.%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EFirst%2C%20the%20investigation%E2%80%99s%20email%20analysis%20is%20changing%20to%20use%20the%20latest%20Defender%20for%20Office%20365%20threat%20categories%3A%20malware%2C%20high-confidence%20phishing%2C%20normal%20phishing%2C%20and%20spam.%26nbsp%3B%20This%20provides%20security%20teams%20with%20the%20ability%20to%20focus%20on%20the%20most%20critical%20malicious%20threats%20included%20in%20the%20investigation%20(high%20confidence%2C%20e.g.%20a%20credential%20theft%20URL)%20vs.%20items%20that%20are%20simply%20suspicious.%26nbsp%3B%20It%20also%20ensures%20that%20comparing%20investigations%20to%20threat%20explorer%20or%20advanced%20hunting%20data%20provides%20more%20consistent%20results%20in%20terms%20of%20threat%20types.%3C%2FLI%3E%0A%3CLI%3EA%20second%20improvement%20is%20that%20investigations%20only%20create%20recommended%20actions%20for%20emails%20and%20email%20clusters%20determined%20to%20be%20the%20most%20critical%20threats%3A%20malware%2C%20high-confidence%20phishing%2C%20malicious%20URLs%20and%20malicious%20files.%26nbsp%3B%20This%20further%20reduces%20SecOps%20workloads%20%E2%80%93by%20focusing%20valuable%20time%20and%20actions%20on%20malicious%20emails.%3C%2FLI%3E%0A%3C%2FUL%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%22GiulianGarruba_1-1626463685185.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F296480i1BF5860B05F9EE2B%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22GiulianGarruba_1-1626463685185.png%22%20alt%3D%22Figure%202%3A%20This%20email%20cluster%20evidence%20has%20an%20action%20because%20it%E2%80%99s%20malicious%20high-confidence%20phishing%2C%20with%20emails%20remaining%20in%20the%20mailbox.%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%202%3A%20This%20email%20cluster%20evidence%20has%20an%20action%20because%20it%E2%80%99s%20malicious%20high-confidence%20phishing%2C%20with%20emails%20remaining%20in%20the%20mailbox.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22GiulianGarruba_2-1626463685211.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F296479i9ECA5AD4AB9CB10A%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22GiulianGarruba_2-1626463685211.png%22%20alt%3D%22Figure%203%3A%20In%20cases%20where%20email%20clusters%20only%20have%20suspicious%20items%20like%20the%20spam%20and%20normal%20phish%20cluster%20in%20the%20example%20above%2C%20the%20automated%20investigation%20will%20no%20longer%20queue%20a%20pending%20action.%26nbsp%3B%20Only%20malicious%20items%20in%20mailboxes%20get%20actions.%22%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-caption%22%20onclick%3D%22event.preventDefault()%3B%22%3EFigure%203%3A%20In%20cases%20where%20email%20clusters%20only%20have%20suspicious%20items%20like%20the%20spam%20and%20normal%20phish%20cluster%20in%20the%20example%20above%2C%20the%20automated%20investigation%20will%20no%20longer%20queue%20a%20pending%20action.%26nbsp%3B%20Only%20malicious%20items%20in%20mailboxes%20get%20actions.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-950499921%22%20id%3D%22toc-hId-951279037%22%3E%3CBR%20%2F%3EComing%20up%20in%20Part%202...%3C%2FH2%3E%0A%3CP%3EIn%20this%20blog%2C%20we%20talked%20about%20the%20new%20email%20analysis%20improvements%20in%20Defender%20for%20Office%20365%20investigations%20and%20how%20they%20will%20improve%20SecOps%20efficiencies.%26nbsp%3B%20The%20new%20threat%20types%2C%20latest%20delivery%20locations%2C%20and%20updates%20after%20investigation%20completion%20ensure%20that%20SecOps%20teams%20get%20clearer%20threat%20data%2C%20more%20accurate%20and%20recent%20location%20information%2C%20plus%20fewer%20and%20more%20focused%20actions.%20In%20the%20next%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmicrosoft-defender-for-office%2Fautomatically-triage-phish-submissions-in-microsoft-defender-for%2Fba-p%2F2733752%22%20target%3D%22_self%22%3Eblog%20post%3C%2FA%3E%2C%20we%20will%20hear%20from%20some%20of%20our%20closest%20partners%20leveraging%20these%20capabilities%20in%20Microsoft%20Defender%20for%20Office%20365%20to%20help%20efficiently%20and%20effectively%20detect%20and%20respond%20to%20threats.%20Stay%20tuned!%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDo%20you%20have%20questions%20or%20feedback%20about%20Microsoft%20Defender%20for%20Office%20365%3F%20Engage%20with%20the%20community%20and%20Microsoft%20experts%20in%20the%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2FMDOForum%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EDefender%20for%20Office%20365%20forum%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2557387%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3EThis%20blog%20is%20part%20one%20of%20a%20multi-part%20series%20focused%20on%20the%20new%20and%20improved%20incident%20response%20capabilities%20within%20Microsoft%20Defender%20for%20Office%20365.%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2557387%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EInvestigation%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ERemediation%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Sep 09 2021 09:37 AM
Updated by: