Respond to incidents in Defender for Endpoint
Device timelines, response actions including live response and investigation packages, evidence and entity investigation, and attack disruption incidents.
- 16 min
- 4 concepts
- Try it yourself
- 3-question check
Learn
When a device is involved in an attack, Defender for Endpoint lets you see exactly what happened on it, contain it, collect evidence and clean it up, all remotely.
- 1
Investigate device timelines
The device timeline shows every recorded event on a device (process creation, file, network, registry, logon) in time order. Filter by event type, search, flag events of interest, and export. Start from the alert's time and work backwards to initial access and forwards to see what the attacker did next.
Remember: Work back from the alert to find how they got in.
- 2
Perform actions on the device, including live response and collecting investigation packages
Device actions: isolate device (full or selective, keeps Defender connected), restrict app execution (only Microsoft-signed), run antivirus scan, collect investigation package (logs, autoruns, processes, network connections in a zip), and initiate live response session (remote shell to run commands such as
processes,getfile,remediateand approved scripts from the library).Remember: Isolate first; live response to dig in.
- 3
Perform evidence and entity investigation
Entity pages show everything about a file (prevalence, signer, detections; actions like stop and quarantine, add indicator), user, IP address and URL/domain. The incident's Evidence and Response tab lists all evidence and remediation status. Submit files for deep analysis in the sandbox.
Remember: File seen on one device or a thousand? Check prevalence.
- 4
Investigate and remediate incidents identified by automatic attack disruption
Disruption incidents are tagged Attack Disruption and show contained devices and users. Investigate the attack, remediate, then release containment from the device or user page (or Action center) when safe. Check that contained assets weren't business-critical service accounts that should have been excluded.
Remember: Release containment once the threat is removed.
Device response actions
| Action | When |
|---|---|
| Isolate device | Stop lateral movement immediately |
| Restrict app execution | Allow only Microsoft-signed code |
| Collect investigation package | Forensics and evidence |
| Live response | Hands-on investigation and remediation |
| Run antivirus scan | Find and remove malware |
Try it
Which response action?
This interactive part needs JavaScript.
In the portal
- Device inventoryMicrosoft Defender portal: Assets > Devices
- Live response libraryMicrosoft Defender portal: Settings > Endpoints > Advanced features
- Action centerMicrosoft Defender portal: Actions & submissions > Action center
Key terms
Click a card to see the definition.
Check your understanding
3 questions. Score 80% or more and these skills are marked as confident in your SC-200 study plan.
Which action stops a device talking to the network but keeps it connected to Defender?
Isolation contains the device.
What must be turned on to run unsigned scripts in live response?
It's an advanced feature setting.
How are attack disruption incidents identified?
They carry a tag in the queue.
Sources
- Microsoft Learn: Device timeline
- Microsoft Learn: Take response actions on a device
- Microsoft Learn: Live response
- Microsoft Learn: Automatic attack disruption
Facts in this lesson are from Microsoft Learn. This site isn't affiliated with Microsoft.