A Security Operations Center (SOC) analyst receives an EDR behavioral alert indicating an unauthorized persistence script running on an internal database host. In what order should the analyst execute the following actions to effectively contain, triage, and remediate the incident using EDR capabilities?
- 1Apply host network isolation via the EDR management console while preserving agent-to-cloud control communications.
- 2Terminate active malicious parent and child process trees associated with the persistence script execution.
- 3Collect volatile RAM and system artifacts remotely through the EDR forensic collector module.
- 4Analyze process tree lineage and historical EDR endpoint telemetry to determine root cause and initial entry point.
- 5Update global EDR policy with custom Indicators of Compromise (IOCs) and block rules enterprise-wide.
Answer
The correct operational sequence begins with isolating the endpoint network traffic, stopping active malicious processes, collecting volatile forensic data, conducting root-cause process tree analysis, and deploying enterprise-wide IOC block rules.
The standard incident response containment sequence for EDR workflow mandates immediate host-level network isolation (to stop lateral spread), followed by process termination (to stop active execution), volatile evidence capture (for forensics), root-cause analysis via process lineage telemetry, and enterprise policy updating (to enforce long-term mitigation).
Step-by-Step Solution
Key Concept
EDR Incident Containment and Investigation Lifecycle
Estimated Time:1m 30s