Cambridge: 01223 209920        London: 020 3519 0124        Ireland: +353 1697 2287        Sheffield: 0114 349 8054        Suffolk: 0144 059 2163         Email: Lucy@breathetechnology.com
How to Create a Cyber Incident Playbook

How to Create a Cyber Incident Playbook

A suspicious Microsoft 365 sign-in, an encrypted file server or a finance colleague who has acted on a convincing fake invoice can all demand action before the full picture is clear. To create a cyber incident playbook is to decide what happens next before stress, uncertainty and commercial pressure take over.

For UK businesses and schools, a good playbook is not a lengthy document that sits unread in a compliance folder. It is a practical set of instructions that helps the right people contain a problem, protect staff and data, meet their obligations, and get essential services running again. It gives senior leaders confidence without asking them to become cyber security specialists.

Why an incident playbook matters

Cyber incidents are operational incidents. A ransomware attack can stop a school accessing learning systems before the first lesson. A compromised mailbox can lead to fraudulent payment requests. A lost laptop may contain sensitive pupil, customer or employee information. The technology issue matters, but so do the decisions around it: who can authorise a shutdown, who speaks to insurers, and when should affected people be told?

Without a defined plan, teams can lose valuable time asking basic questions. An internal IT manager may be working hard to investigate while an operations director is trying to decide whether staff should continue using their devices. Meanwhile, well-meaning colleagues might delete evidence, restart affected systems or send an inaccurate message to customers.

A playbook brings order to those first critical hours. It defines ownership, sets sensible escalation routes and makes clear that protecting the organisation comes before finding someone to blame. That is particularly useful where IT responsibility sits with a finance, operations or school business leader, or where a small internal IT team needs expert escalation support.

Set the scope before you create a cyber incident playbook

Start with the incidents most likely to cause material disruption in your organisation. You do not need a separate 40-page plan for every imaginable threat. A concise core plan, supported by scenario-specific actions, is usually more useful.

For many organisations, the priority scenarios are ransomware, business email compromise, unauthorised Microsoft 365 access, a lost or stolen device, denial of service, and a suspected data breach. Schools and trusts may also need specific actions for safeguarding-related compromises, parent communication systems and teaching platforms. Organisations that process payments should put invoice fraud and supplier impersonation near the top of the list.

Your scope should reflect what would genuinely hurt if unavailable or exposed. Identify the systems that support payroll, finance, communications, operational delivery, pupil information, customer records and remote access. Record the owners of those services, how they can be isolated, whether they are backed up, and how quickly they need to be restored.

There is a trade-off here. A broad plan is easier to maintain, but it can be too vague when a real incident happens. A highly detailed plan may be precise, but staff will not use it if it is difficult to find or understand. Aim for clear actions, short checklists and decision points that work at 2am as well as during a tabletop exercise.

Define who does what under pressure

Incident response fails when everyone assumes somebody else has made the decision. Your playbook should name people and deputies, not just job titles. Keep a secure offline copy of their personal or alternative contact details in case email and Teams are unavailable.

For most organisations, the following roles need to be clear:

  • The incident lead coordinates response activity, keeps the timeline and confirms priorities.
  • The technical lead investigates, contains the threat and manages restoration with internal IT or your managed service provider.
  • The executive decision-maker approves major actions, such as shutting down a service, engaging legal support or notifying key stakeholders.
  • The communications lead prepares clear messages for staff, customers, parents, suppliers and media where appropriate.
  • The data protection lead assesses personal data risk and manages reporting decisions, including engagement with the Information Commissioner’s Office.
  • The finance lead watches for fraud, pauses suspicious payments and contacts banks or insurers where needed.

In a smaller business, one person may cover several roles. That is fine, provided there is a deputy and the responsibilities are understood. The goal is not a perfect organisational chart. It is fast, accountable action.

Build the first-hour actions into every scenario

The first hour should be familiar, even if the incident is not. Your playbook should tell staff how to report a concern and what the response team does immediately.

For example, if a device appears infected, the first action may be to disconnect it from Wi-Fi and wired networks without turning it off, then report it using an agreed telephone number. If an email account is compromised, the technical team may reset credentials, revoke active sessions, review mailbox rules and check for suspicious forwarding. If a fraudulent payment is suspected, the finance team should contact the bank straight away while IT preserves the relevant email evidence.

Avoid instructions that could make matters worse. “Delete the email” or “restart the server” might seem sensible, but both can destroy evidence or allow an attacker to regain access. The playbook should state when to preserve logs, screenshots, email headers and device details, and who is authorised to make changes.

A useful first-hour section answers five questions: what has happened, what must be contained, what services are affected, who needs to know now, and what evidence should be retained? Facts should be separated from assumptions. This prevents speculation from becoming the organisation’s working narrative.

Put communication and reporting decisions in writing

Technical recovery is only one part of the response. Staff need to know whether it is safe to use their accounts. Customers, parents or suppliers may need practical advice. Leaders need honest updates that explain what is known, what is being investigated and when the next update will arrive.

Prepare simple message templates in advance, but do not send them automatically. The wording depends on the facts, the scale of disruption and whether personal data has been affected. A premature message can cause confusion; waiting too long can erode trust. Your playbook should set approval routes and make clear who is permitted to speak externally.

Where a personal data breach is likely to result in a risk to people’s rights and freedoms, an organisation may need to report it to the ICO without undue delay and, where feasible, within 72 hours of becoming aware. Some incidents also require notification to insurers, banks, regulators, contract partners or law enforcement. Get specialist legal and data protection advice where the position is unclear. The playbook should prompt that decision, rather than trying to replace professional judgement.

Plan recovery, not just containment

Disconnecting a compromised system is often the right move. It is not the end of the job. Your playbook needs a recovery sequence that considers business priorities, clean backups, identity security and confidence that the threat has been removed.

Restoring everything at once is rarely sensible. Bring back the services that support safe, essential operations first. Verify backups before restoration, confirm that administrator accounts are secure, and apply necessary patches or configuration changes before reconnecting systems. If an attacker used a stolen Microsoft 365 account, restoring files without resolving identity controls may simply recreate the same opening.

This is where tested disaster recovery arrangements make a meaningful difference. Backups must be accessible, protected from tampering and regularly tested. Recovery time objectives should be realistic: a system restored in three days may be acceptable for archives but not for payroll, safeguarding records or a customer-facing service.

Test the playbook with the people who will use it

A playbook that has never been tested is an assumption, not a plan. Run a short tabletop exercise twice a year and after significant changes such as a cloud migration, acquisition, new school site or major supplier change.

Choose a believable scenario. Perhaps a member of staff approves a malicious multi-factor authentication prompt, then unusual mailbox activity is detected. Ask the team what they would do in the first 15 minutes, who would contact whom, how they would protect evidence, and what message leadership would receive. The value comes from finding uncertainty before an attacker does.

After each exercise or live incident, record what worked and what caused delays. Update contacts, improve technical controls, revise messages and make ownership clearer. Breathe Technology can support this work through cyber security expertise and practical incident planning, particularly where internal teams need additional capacity or independent guidance.

The best time to make difficult cyber decisions is when your systems are working, your people are calm and there is time to think. Give your team a playbook they can actually follow, keep it current, and it will provide far more than a document: it will provide direction when it matters most.


Download the Outsourced IT Support Checklist

Every Manager responsible for IT (Finance, Office Manager, Ops etc), that's not an IT Manager by profession should review their IT Support experience. How do you know if your expectations are realistic, is the team performing, are you at risk and didn't realise? Do you have doubts? Or are they simply great,

This Check Outsourced IT Support Checklist has been created, after performing hundreds of IT Audits over more than 20 years, revealing the most commonly found problems caused by IT Support Providers.

How does yours compare? Download for free today!

(PS. Your details remain confidential and will never be shared with anyone else)