A security analyst receives a high-severity alert from an Endpoint Detection and Response (EDR) agent indicating that a malicious WMI event subscription has been registered on a critical enterprise server and is attempting to execute unauthorized PowerShell scripts. Place the containment and incident response steps in the correct sequential order from initial response to final remediation.
- 1Analyze EDR telemetry alerts and confirm the anomalous WMI process lineage.
- 2Initiate host-level network isolation via the EDR console to prevent lateral movement.
- 3Terminate active malicious processes and child threads running under the WMI host process.
- 4Use EDR live response tools to gather volatile memory artifacts and process inspection logs.
- 5Remove persistent WMI bindings, restore system configurations, and rejoin the host to the network.
Answer
The correct sequence begins with validating telemetry alerts, followed by network isolation of the host, process termination, live response artifact collection, and finally persistence cleanup and host restoration.
In standard incident response protocols using EDR technology, the first step is validating telemetry alerts. Once confirmed, immediate network isolation protects the rest of the enterprise from lateral movement. Next, running malicious processes are killed to stop active damage, followed by collecting volatile live response artifacts for root cause analysis. Finally, persistent threat artifacts (such as WMI bindings) are deleted and the clean endpoint is restored.
Step-by-Step Solution
Key Concept
EDR Incident Containment and Investigation Workflow