Glossary

Incident response plan

IRP Cyber incident response plan

Definition

An incident response plan records who does what when a security incident happens, including decisions, contacts and recovery arrangements.

It records responsibilities, reporting routes and decision points before a crisis. Staff need to reach it even when normal systems or company email are unavailable.

A customer may include “Incident response plan” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

An incident response plan gives people usable instructions when normal work is disrupted. It identifies who takes charge, how employees report a concern and when decisions need escalation. The NCSC's preparation guidance for small businesses recommends documented responsibilities, contact details and clear trigger points.

Keep the plan focused on likely incidents and the first decisions people must make. Record how to reach the IT provider outside normal hours, who can authorise shutting down a service and where relevant insurance information is stored. Make a safe copy accessible if company email or shared drives stop working.

For example, an employee at a small consultancy might notice unexpected messages sent from the finance mailbox. The plan identifies who to call, who can restrict the account and who decides whether customers need a warning. Staff can begin the agreed response without waiting for the founder to find the provider's contract.

A document alone cannot establish readiness. Rehearse it, correct gaps and confirm that suppliers will provide the support you expect. Avoid writing one rigid script for every possible attack; record responsibilities and decision points that remain useful when the incident develops differently from the scenario you imagined.