Incident response lifecycle
Incident response is a cycle that starts before the incident
The incident response lifecycle: preparation, detection, analysis, containment, eradication, recovery, lessons learned. NIST SP 800-61 Rev. 3 maps it to CSF 2.0.
Every incident follows the same arc. Preparation: a plan, a team, tools, training. Detection: an alert or a report that something is wrong. Analysis: is it real, how far does it reach, how serious is it? Containment: stop the spread, and keep the evidence. Eradication: remove the attacker and the way they got in. Recovery: restore, verify, and watch closely. Then lessons learned, which feed straight back into preparation. NIST’s 2025 revision maps the same work onto the Cybersecurity Framework functions.
Preparing to respond · Going deeper
The response team, playbooks and exercises
Preparation means an incident response plan, defined roles, playbooks and tabletop exercises.
Preparation means an incident response plan, defined roles, playbooks and tabletop exercises. Roles. Incident commander runs the response and makes the calls the plan assigns. Technical lead and responders investigate, contain and eradicate. Communications staff, customers and media, one voice. Legal and privacy notification duties, evidence, law enforcement, the data protection officer. Executives business decisions such as shutting down a service or engaging outside help. Making it real. Outside help is arranged in advance: an incident response retainer, cyber insurance and its approved firms, and law enforcement contacts.
Roles
- Incident commander runs the response and makes the calls the plan assigns.
- Technical lead and responders investigate, contain and eradicate.
- Communications staff, customers and media, one voice.
- Legal and privacy notification duties, evidence, law enforcement, the data protection officer.
- Executives business decisions such as shutting down a service or engaging outside help.
Making it real
Outside help is arranged in advance: an incident response retainer, cyber insurance and its approved firms, and law enforcement contacts.
Running an incident
The hardest part of a response is the decisions, made at speed
A real response is a sequence of decisions on containment, evidence and notification, made by the people the plan names.
Here is a ransomware incident, hour by hour. At twelve past nine, EDR sees thousands of files renamed a minute on a file server. By nine forty it is confirmed: ransomware, two servers so far. Five minutes before ten, the first decision. Isolate the whole server segment now, and accept a four-hour outage. At half past ten: capture memory before anything is shut down. At eleven: personal data may be involved, so legal and the data protection officer are told, and a seventy-two-hour clock starts. Tuesday: passwords reset, persistence removed, the VPN flaw patched. Then recovery from offline backups. And two weeks later, a blameless review.
Containment
Contain fast, but know what each action costs you
Containment options trade speed against business impact and evidence; isolate rather than power off.
Containment has several levers, and each has a price. Isolate a host with EDR: it stops that machine spreading, costs one user, and keeps memory intact. Disable accounts: stops stolen credentials, but may alert the attacker. Block known bad addresses: useful, until they switch servers. Cut off a network segment: stops spread between zones, at the cost of an outage. Pull the power: stops everything, and destroys all memory evidence. So isolate, rather than power off.
Digital forensics
Collect the evidence that disappears fastest, first
The order of volatility (RFC 3227): registers, memory, temporary files, disk, remote logs, archives.
Digital evidence fades at different speeds. Processor registers and cache last nanoseconds. Memory, with running processes, open connections and encryption keys, lasts only until power-off. Temporary files and swap, minutes or hours. Disks, until overwritten. Remote logs, as long as they are retained. Backups, years. So collect from the top down, record every action, and image disks through a write blocker so the original never changes.
Forensic practice · Going deeper
Acquisition, imaging, timelines and legal hold
Know acquisition, write blockers, hashing for integrity, timelines, legal hold and e-discovery.
Know acquisition, write blockers, hashing for integrity, timelines, legal hold and e-discovery. Acquisition capture memory with a trusted tool, then image disks bit for bit. In the cloud, snapshot volumes and export logs before instances are terminated. Write blocker hardware or software that lets you read a drive without changing a single bit. Hashing a SHA-256 of the image at collection and before every analysis proves integrity. Timeline events from all sources merged on one clock (record time zones and clock drift) to tell what happened, in order. Legal hold an instruction to preserve all potentially relevant data once litigation is reasonably expected, overriding normal deletion. E-discovery finding and producing electronic records for legal proceedings. Document everything: who did what, when, with which tool. An unexplained change to evidence is a gift to the other side’s lawyer.
- Acquisition capture memory with a trusted tool, then image disks bit for bit. In the cloud, snapshot volumes and export logs before instances are terminated.
- Write blocker hardware or software that lets you read a drive without changing a single bit.
- Hashing a SHA-256 of the image at collection and before every analysis proves integrity.
- Timeline events from all sources merged on one clock (record time zones and clock drift) to tell what happened, in order.
- Legal hold an instruction to preserve all potentially relevant data once litigation is reasonably expected, overriding normal deletion.
- E-discovery finding and producing electronic records for legal proceedings.
Chain of custody
A chain of custody proves the evidence was never touched
A chain of custody records every hand-off; matching hashes prove integrity; a legal hold preserves data.
Evidence is only useful if you can prove nobody changed it. The responder images the laptop disk, records its hash, bags it, tags it and signs. The evidence locker logs it in and seals it. The analyst works on a copy and checks the hash first: it matches. Months later, the court sees the full log of every hand-off, and the same hash. Who, what, when, where and why, for every step. One gap, and the evidence can be thrown out.
Notification
Reporting deadlines are counted in hours, not weeks
GDPR 72 hours; NIS2 24 hours, 72 hours and one month; SEC 8-K four business days; HIPAA 60 days.
A breach starts several clocks. Under NIS2, essential and important entities in the EU send an early warning within twenty-four hours, a notification within seventy-two, and a final report within a month. GDPR gives seventy-two hours to tell the data protection regulator about a personal-data breach. US-listed companies file within four business days of deciding an incident is material. And HIPAA allows up to sixty days to notify patients. Most clocks start when you become aware, so contacts and templates are ready before you need them.
Lessons learned
Lessons learned keeps asking “why?” until it reaches a fix
Root cause analysis, such as the five whys, in a blameless review; track MTTD and MTTR.
The incident is over. Now make sure it cannot happen the same way again. Ransomware encrypted two file servers. Why? The attacker had domain admin rights. Why? The same password was used on a VPN account, and it was phished. Why? The VPN accepted a password alone. Why? An exception made years ago was never reviewed. That is the root cause. So the fixes are MFA on all remote access, separate admin accounts, and exceptions that expire. Each with an owner and a date.
Lesson complete
You finished “Incident response”
Nicely done.