Incident Response Lifecycle
The NIST SP 800-61 Incident Response lifecycle provides a structured framework for handling security incidents. Following a systematic lifecycle reduces attacker dwell time, limits breach scope, and produces evidence for legal action and post-incident improvement.
The Six Phases (NIST SP 800-61)
Phase 1 - PREPARATION
Build IR capability before incidents occur
- Establish IR team and escalation contacts
- Deploy SIEM, EDR, and logging infrastructure
- Write and test IR playbooks for common scenarios
- Conduct tabletop exercises and red team engagements
- Pre-position forensic tools and evidence storage
Phase 2 - IDENTIFICATION
Detect and confirm that an incident has occurred
- Alert sources: SIEM, IDS, EDR, help desk report, external notification
- Determine: Is this a real incident or a false positive?
- If real: What systems are affected? What is the incident type?
- Assign severity level: Critical / High / Medium / Low
Phase 3 - CONTAINMENT
Stop the bleeding - limit damage without losing evidence
- Short-term: Isolate affected systems from the network
- Long-term: Patch, clean, or rebuild before reconnecting
- CRITICAL: Preserve evidence BEFORE containment actions
Phase 4 - ERADICATION
Remove malware, close attack vectors, eliminate persistence
- Remove backdoors, scheduled tasks, startup entries
- Patch the exploited vulnerability
- Reset compromised credentials
- Verify no attacker presence remains
Phase 5 - RECOVERY
Restore systems to normal operation with confidence
- Restore from clean backups, or rebuild from scratch
- Verify system integrity before reconnecting
- Monitor closely for signs of re-compromise
Phase 6 - POST-INCIDENT ACTIVITY (Lessons Learned)
Improve defenses based on what was learned
- Timeline reconstruction: When did attacker gain access?
- Root cause analysis: What vulnerability was exploited?
- Improvements: What controls would have prevented or detected sooner?Incident Severity Classification
- Critical (P1 - Immediate response, 24/7): Ransomware, data breach of PII/PHI/PCI, full domain compromise, active ongoing attack. Response time: < 15 minutes. Escalate: CISO, Legal, PR immediately
- High (P2 - 4-hour response): Malware on critical server, credential compromise for privileged accounts, confirmed intrusion but limited scope. Escalate: IR team lead, system owners
- Medium (P3 - 24-hour response): Malware on workstation, phishing with credential submission, policy violation with potential security impact. Escalate: IR team member
- Low (P4 - 72-hour response): Policy violations, unsuccessful attack attempts, suspicious but unconfirmed activity. Escalate: Security analyst on duty
Common Mistakes
- Jumping to eradication before identification - cleaning a system before understanding the attacker's full footprint causes you to miss persistence mechanisms and the true scope
- No IR playbooks before an incident - during an active incident is the worst time to design your response process; pre-written playbooks reduce response time by hours
- Ignoring the lessons-learned phase - organizations that skip post-incident reviews face the same incidents repeatedly
Tip
Tip
Practice Incident Response Lifecycle in small, isolated examples before integrating into larger projects. Breaking concepts into small experiments builds genuine understanding faster than reading alone.
The foundational security model: Confidentiality (privacy), Integrity (trust), and Availability (uptime).
Practice Task
Note
Practice Task - (1) Write a working example of Incident Response Lifecycle from scratch without looking at notes. (2) Modify it to handle an edge case (empty input, null value, or error state). (3) Share your solution in the Priygop community for feedback.
Quick Quiz
Common Mistake
Warning
A common mistake with Incident Response Lifecycle is skipping edge case testing - empty inputs, null values, and unexpected data types. Always validate boundary conditions to write robust, production-ready cybersecurity code.
Key Takeaways
- The NIST SP 800-61 Incident Response lifecycle provides a structured framework for handling security incidents.
- Critical (P1 - Immediate response, 24/7): Ransomware, data breach of PII/PHI/PCI, full domain compromise, active ongoing attack. Response time: < 15 minutes. Escalate: CISO, Legal, PR immediately
- High (P2 - 4-hour response): Malware on critical server, credential compromise for privileged accounts, confirmed intrusion but limited scope. Escalate: IR team lead, system owners
- Medium (P3 - 24-hour response): Malware on workstation, phishing with credential submission, policy violation with potential security impact. Escalate: IR team member