A Security Operations Center (SOC) analyst receives an active EDR behavioral alert indicating that an unauthorized process executed `vssadmin.exe delete shadows /all /quiet` on an enterprise workstation and is actively attempting to encrypt files on connected SMB shares. Place the incident response actions in the correct chronological sequence to contain the threat and perform initial triage.
- 1Initiate host-level network isolation through the EDR console to block lateral traffic while maintaining agent-to-console communication.
- 2Revoke active session tokens and disable the compromised user account credentials in the central identity provider.
- 3Execute an EDR agent action to kill the malicious process tree and pull a volatile memory dump for execution analysis.
- 4Collect endpoint telemetry logs and sample payloads via EDR remote shell for root-cause analysis and threat hunting.
Answer
The correct sequence of actions is: 1) Initiate host-level network isolation through the EDR console, 2) Revoke active session tokens and disable compromised user account credentials, 3) Execute an EDR agent action to kill the malicious process tree and pull a volatile memory dump, and 4) Collect endpoint telemetry logs and sample payloads via EDR remote shell.
In EDR incident response, immediate containment takes precedence over investigation steps. Isolating the host via the EDR agent instantly restricts network connectivity and prevents lateral encryption across SMB shares without severing EDR console access. Next, revoking identity tokens prevents the attacker from using compromised credentials on other network hosts. Terminating the malicious process and capturing memory stops local damage and captures volatile evidence. Finally, collecting forensic logs enables root-cause analysis.
Step-by-Step Solution
Key Concept
EDR Incident Containment and Response Workflow
Estimated Time:2m 0s