A serious cyber incident rarely provides all the facts before the business has to make decisions. Technical teams may still be working out what happened while staff need instructions and customers are already noticing a disruption. Decisions about what can continue, what should be stopped and what can safely be restored often have to be made with incomplete information.
That is why incident preparation is as much about people and authority as it is about technology. A response plan becomes considerably more useful when those expected to follow it have rehearsed the awkward decisions, not simply read the document.
Establish a way to lead the response
Name an incident lead and someone who can deputise. Identify who will coordinate technical activity, business operations, communications and any relevant legal or regulatory advice. In a smaller organisation, one individual may cover several responsibilities, making backup arrangements and realistic workload particularly important.
Maintain the contact details and alternative communication arrangements the team would need if email or the usual collaboration platform were unavailable or untrustworthy. Record supplier and insurer contacts, together with any conditions for engaging specialist support. The NCSC's incident preparation guidance supports setting out responsibilities, contact routes and escalation triggers before an incident occurs [S2].
From the outset, keep facts separate from assumptions. Record when the issue was raised, which services are believed to be affected, who is investigating and when the next update is expected. This isn't paperwork for its own sake. It helps a new shift understand the position and gives the business a record of decisions taken before all the answers were known.
An incident plan needs to work on a difficult day, with incomplete information and people who may be unavailable. A contact list stored only in the affected collaboration system is of limited value if that platform cannot be reached or trusted. A named incident lead is also a fragile arrangement without a deputy. I would keep the opening record simple: what is confirmed, what remains an assumption, which services are affected, what decision is needed next and when the position will be reviewed. The intention is continuity of control while technical investigation continues, not paperwork for its own sake.
Make continuity choices explicit
Consider an illustrative engineering business whose scheduling platform becomes unavailable. Staff can allocate urgent work manually, but only for a limited number of engineers. Which customer commitments come first? How much work can be delivered safely? Who tells customers about the change?
The aim is to keep an acceptable level of service operating while investigation and recovery continue. However, a workaround has its own limits. It can introduce errors, require information that is also unavailable or create new exposure if access controls are relaxed without thought. The service owner needs to understand those limits and how records will be brought back into agreement later.
Containment decisions can affect operations too. Isolating systems might prevent further damage while interrupting legitimate work. Pre-agreed authority allows prompt action, but significant trade-offs should still reach an appropriate business decision-maker. An incident should not have to wait for a large committee to assemble before routine emergency powers can be used.
Continuity usually involves accepting an imperfect service level for a limited period. The engineering business may be able to allocate emergency jobs manually while postponing routine appointments. That requires an owner, a realistic capacity limit and an agreed way of explaining the change to customers. It also requires information that remains available during the disruption. A workaround that relies on inaccessible scheduling data is not a fallback. Rehearsing a small part of the process can establish what staff can really deliver and how transactions will be reconciled when normal systems return.
Treat recovery as a business acceptance decision
Getting an application running again is an important technical step. It is not, on its own, the point at which a business service has recovered. The environment must be suitable to use, essential dependencies must be available and the information needs to be sufficiently accurate to trust.
Technical specialists should guide containment, evidence preservation and restoration. Improvised changes may compromise an investigation or allow the problem to return. Backup arrangements are vital, but their existence is not proof of successful recovery. The NCSC's malware and ransomware guidance recommends checking restoration and protecting the backups themselves [S10]. Business testing must also allow for validating data and returning to a useful level of operation.
Some consequences continue after systems come back. The organisation may still be dealing with disclosed information, customer concerns or investigations. Technical restoration and resolution of the incident are related, but they are not identical.
Recovery is better treated as a sequence of checks than a single technical milestone. Can authorised employees access the environment? Do essential integrations work? Are the records sufficiently accurate to trust? Can transactions be completed and verified? The service owner should help define these acceptance criteria before the incident. A staged restoration may be appropriate, with the most important services returning before less urgent work. The order matters because a successful server restart may still leave orders, payments and customer records needing reconciliation.
Communicate what is known
An early update should be clear about the confirmed operational impact, the response in progress and when more information will be provided. It should avoid confident statements about cause, scale or data exposure until the evidence supports them. Someone also needs to coordinate messages to employees, customers and suppliers so that the account remains consistent.
Notification and reporting obligations vary with the incident and the rules applying to the organisation. A generic message template cannot decide whether a report is legally required. The response plan should identify the advisers and current official guidance needed to assess those obligations promptly.
Clear communication does not require false certainty. It is possible to explain what service is disrupted, which temporary arrangements are in place and when the next update is due, while saying that the cause remains under investigation. Internal messages matter just as much as external ones: staff need to know which activities must stop, which may continue and how to report new information. If normal channels are compromised, the alternative should have been agreed beforehand. Consistent messages support operational decisions; they cannot replace those decisions.
Rehearse a realistic difficulty
A short discussion exercise can reveal a missing contact, an uncertain authority or conflicting expectations without touching a live system. The NCSC provides structured resources through Exercise in a Box [S11]. The RJA toolkit offers a separate illustrative scenario and a place to capture decisions and actions.
I would judge an exercise by what changes afterwards. Each finding needs an owner and a way to check the improved arrangement. Discovering that an important hand-off fails in rehearsal is useful, provided the business does something about it.
A useful exercise introduces something the written plan does not conveniently resolve: an unreachable senior contact, conflicting accounts of which data is reliable or a supplier who cannot respond in the expected window. It tests judgement and coordination rather than whether participants remember a set of instructions. The strongest result is a small number of uncomfortable discoveries with accountable owners and dates, followed by evidence that arrangements have actually changed. The aim is a more dependable business capability, not a discussion exercise that can simply be marked as completed.
Sources and further reading
[S2] NCSC. Small Business Guide Response and Recovery. Step 1 Prepare for incidents. Read original guidance
[S10] NCSC. Mitigating malware and ransomware attacks. Read original guidance
[S11] NCSC. Exercise in a Box Getting started. Read original guidance
The source collection records these references as checked on 28 October 2026. Source attribution does not imply endorsement.
Scenarios are illustrative, not client case studies. This article provides general business guidance, not a security audit, certification or substitute for sector-specific technical, legal or contractual advice.
