Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Incident response is the structured way an organisation prepares for, detects, contains, and recovers from a cybersecurity incident while preserving evidence and meeting reporting duties.

What Is Incident Response?
Incident response (IR) is the organised approach an organisation takes when a cybersecurity incident occurs—from the first alert to full recovery and the lessons that follow. Its purpose is to limit damage, restore normal operations quickly, preserve evidence, and meet legal and contractual obligations.
An incident might be a ransomware outbreak, a compromised Microsoft 365 mailbox sending invoice fraud, a leaked database, or an insider copying files before resigning. What separates a contained event from a crisis is rarely the technology; it is whether people know who decides what, and how fast.
Two models dominate. The SANS model describes six steps, often remembered as PICERL. NIST’s long-standing four-phase lifecycle from SP 800-61 Revision 2 was replaced in April 2025 by NIST SP 800-61r3, which maps incident response onto the six functions of the NIST Cybersecurity Framework 2.0: Govern, Identify, Protect, Detect, Respond, and Recover.
| SANS (PICERL) | NIST SP 800-61r2 (legacy) | NIST SP 800-61r3 / CSF 2.0 |
|---|---|---|
| Preparation | Preparation | Govern, Identify, Protect |
| Identification | Detection and Analysis | Detect |
| Containment, Eradication, Recovery | Containment, Eradication and Recovery | Respond, Recover |
| Lessons Learned | Post-Incident Activity | Improvement across all functions |
The practical message of r3 is that incident response is not a separate team’s problem; it is woven into risk management, asset inventory, and continuous improvement.
Alerts arrive from EDR, the SIEM, users, suppliers, or occasionally the attacker’s ransom note. Analysts confirm whether the activity is real, establish scope, and assign a severity. Good triage relies on indicators of compromise, timelines, and knowing what “normal” looks like.
Containment buys time. Short-term actions include isolating hosts through EDR, disabling compromised accounts, revoking session tokens, and blocking command-and-control domains. The trade-off is real: pulling the plug too early can alert the attacker and destroy volatile memory evidence; waiting too long lets ransomware spread. Decisions should be pre-agreed in playbooks rather than debated at 02:00.
The team removes persistence mechanisms, resets credentials (including the KRBTGT account twice if Active Directory was compromised), patches the entry point, and restores systems from backups known to be clean. Recovery is staged and monitored, because reinfection in the first few days is common when a backdoor was missed.
A blameless review within a couple of weeks captures the root cause, the timeline, what slowed the team down, and the specific improvements that will be made. Without this step, the same gaps reappear in the next incident.
Regulatory clocks start early, often before the technical picture is clear:
Legal counsel should be involved early, both for privilege and for decisions about ransom demands, law enforcement contact, and public statements.
An effective programme rests on a few concrete elements:
Incident response and digital forensics work hand in hand: responders stop the bleeding, while forensic analysts reconstruct exactly what happened and what data was touched.
If you need experienced responders on call, our incident response services team can support you from first triage to final report.
Activate your incident response plan and assemble the core team. Preserve evidence by isolating affected machines through your EDR rather than powering them off, so memory remains intact. Disable obviously compromised accounts, start a written timeline of every action and decision, and move sensitive discussions to an out-of-band channel. Contact your legal adviser and, if you have one, your retained incident response provider.
No. A security incident is any event that threatens the confidentiality, integrity, or availability of systems or data. It becomes a personal data breach under UK GDPR only when personal data is accidentally or unlawfully destroyed, lost, altered, disclosed, or accessed. A blocked phishing attempt or a contained malware infection with no data access is an incident, not a reportable breach.
At least once a year with a tabletop exercise involving executives, and more often for the technical team. Retest whenever there is a significant change, such as a cloud migration, a merger, or new key personnel. Rotate scenarios between ransomware, data theft, and supplier compromise so that different parts of the plan are exercised and outdated contact details are discovered before a real incident.
The NCSC and law enforcement strongly discourage paying, because payment funds criminal groups and does not guarantee data recovery or deletion. Payments may also breach sanctions law if the group is designated. The UK government has proposed a ban on ransom payments by public sector bodies and operators of critical national infrastructure. Any decision should involve legal counsel, insurers, and senior leadership, documented carefully.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.