Incident Response Lifecycle
NIST SP 800-61 defines the incident response lifecycle: (1) Preparation — policies, procedures, tools, and team training before incidents occur. IRP (Incident Response Plan), runbooks, and contact lists. (2) Detection and Analysis — identifying that an incident has occurred and understanding its scope. Log analysis, IDS/IPS alerts, user reports, SIEM correlation. (3) Containment — limiting the spread of the incident. Short-term containment (isolate affected systems) and long-term containment (clean systems while maintaining operations). (4) Eradication — removing the threat (malware, backdoors, compromised accounts). (5) Recovery — restoring systems to normal operations. Verify systems are clean before reconnecting. (6) Post-Incident Activity (Lessons Learned) — document what happened, update procedures, improve defenses.
Order of volatility: when collecting forensic evidence, capture most volatile data first. Order: CPU registers/cache → RAM (running processes, network connections) → Network traffic (currently flowing) → Disk (persistent) → Remote logs (offsite). RAM is lost when the system is powered off — capture it before pulling the plug.
Network Administrator Role in IR
Containment actions available to network admins: VLAN isolation (move compromised device to quarantine VLAN), ACL blocking (block traffic to/from compromised IP), port shutdown (disable switch port of compromised device), null routing (blackhole route to block traffic to C2 server), DNS sinkholing (redirect malicious domain to a sinkhole IP), firewall rule changes.
Evidence preservation: do not power off systems without capturing volatile evidence first. Do not run AV scans immediately — they modify timestamps and may destroy evidence. Capture network traffic (SPAN port), preserve log files (copy to write-protected media), photograph screen and capture running processes. Follow chain of custody procedures.