A Security Operations Center (SOC) analyst is reviewing an automated response playbook triggered by an Endpoint Detection and Response (EDR) agent following a suspected credential dumping attack against a high-value server. In what chronological sequence should the EDR agent and SOC workflow execute these actions to contain the threat and preserve forensic evidence?
- 1Detect anomalous API memory read requests targeting the Local Security Authority Subsystem Service (LSASS) process.
- 2Enforce host-level software network isolation to prevent lateral movement while preserving agent management telemetry.
- 3Capture a volatile RAM memory dump and terminate the offending injector process tree.
- 4Query tenant-wide EDR telemetry using process hashes and parent-child execution lineages to identify other impacted endpoints.
Cevap
The correct chronological sequence is: 1) Detect anomalous API memory read requests targeting LSASS, 2) Enforce host-level software network isolation, 3) Capture a volatile memory dump and terminate the offending process tree, and 4) Query tenant-wide EDR telemetry to identify other impacted endpoints.
The sequence follows the core EDR lifecycle: Detection must precede response; host-level network isolation must be established immediately after detection to block lateral spread; volatile memory collection and process termination follow isolation to safely remediate the host; and tenant-wide telemetry correlation occurs last to assess broader enterprise compromise.
Adım Adım Çözüm
Anahtar Kavram
EDR Automated Containment and Incident Response Workflow Sequence