A security operations team has confirmed a active malware infection on a financial database administrator's workstation. Arrange the incident response playbook actions in the correct chronological order from first to last.
- 1Disconnect the affected workstation from the network by disabling its network interface.
- 2Capture a volatile RAM memory dump of the isolated system for forensic analysis.
- 3Remove persistent malicious artifacts and re-image the operating system from a secure baseline.
- 4Conduct a post-incident review meeting to document findings and refine incident playbooks.
Answer
The correct chronological sequence begins with host network isolation (containment), followed by volatile memory acquisition (forensics/preservation), followed by system sanitization and image restoration (eradication/recovery), and concludes with the post-incident review (lessons learned).
According to NIST SP 800-61 standards, once an incident is confirmed, the immediate step is Containment (isolating the host from the network). Next comes Evidence Preservation (capturing volatile RAM while the machine is running). Following evidence collection, Eradication and Recovery take place (removing malware and re-imaging from clean media). Finally, Post-Incident Activities (lessons learned) occur once operations return to normal.
Step-by-Step Solution
Key Concept
NIST Incident Response Lifecycle (Containment, Evidence Preservation, Eradication/Recovery, Lessons Learned)