GUIDE · INCIDENT RESPONSE

Incident response playbooks: how to write one for each scenario

By the end of this guide you will know what an incident response playbook looks like, which scenarios to cover first, who should have a role in each one and how to tell whether the document holds up under pressure. It is not a technical manual: it is the method for turning a general plan into instructions a person can follow under stress.

Updated october 2026
11 min read
Altovar Technical Editorial Team

1. Why a general plan is not enough

Almost every business has a plan for managing cyber incidents, but when something happens the general plan becomes a document nobody opens. It describes roles and principles, but does not say who must call whom at night, which system must be isolated first or when to alert the legal adviser. The playbook comes from this gap. It is the operational version of the plan, written for a specific scenario and designed to be read on your feet, with a phone in hand.

The practical difference shows up within minutes. A plan says the incident must be contained. A playbook says which access to revoke, in what order, with which tool, and who must confirm the decision before switching off a system that serves customers. You do not need to write many at once: start with the scenarios most likely for your business and leave rarer variants for a later phase, once the first document has been tested.

2. Choosing the scenarios to cover

The first task is a short list of scenarios. Ask yourself which events could halt production, expose personal data or force you to communicate with customers and authorities. For most small and medium businesses the recurring scenarios are ransomware, credential theft through phishing, data leakage, unavailability caused by an attack and compromise of a supplier. Each scenario should be described in one sentence: what happens, who notices it first and which system is involved.

Not all scenarios deserve the same detail. Those that halt work or affect personal data should be treated in depth; the others can remain short cards. The following table is a starting point to adapt to your systems. Review it when suppliers, applications or the people with access to data change, because the priority of each scenario depends on what it is connected to.

ScenarioTypical impactWho notices it firstInitial priority
RansomwareEncrypted data and stopped servicesUsers or monitoring toolsHigh
Compromised accountAccess to email and documentsThe user or the email providerHigh
Data leakNotification obligations and loss of trustA customer, a supplier or an outside partyHigh
DDoS attackOnline services unreachableCustomers or network monitoringMedium
Compromised supplierDepends on the access grantedThe supplier itself or an unusual signalMedium

3. The structure of a playbook

Every playbook should follow the same structure, so that whoever reads it knows where to look, even under stress. It starts with the signal that activates the document: how to recognise that we are facing this scenario and not an ordinary fault. It then lists the immediate actions, with the order and the owner of each. After that come the internal and external contacts, the decisions that require approval and the criteria for declaring the incident closed.

Two elements are often forgotten. The first is the action log, in which every step is recorded with the time and the name of the person who carried it out. The second is a list of what must not be done, for example restarting systems before preserving their state, or deleting suspicious files without a copy. These details are what prevent the response from making the damage worse.

  • Activation signal: how to recognise the scenario
  • Immediate actions, in order, with an owner for each
  • Internal and external contacts, with an alternative channel if company email does not work
  • Decisions that require explicit approval
  • Closure criteria and handover to the recovery phase

4. Roles and responsibilities: who decides what

A playbook only works if every step has a person who knows they must carry it out. You usually need a decision owner, who authorises actions that halt the business; a technical lead, who coordinates analysis and containment; a communications contact; and a legal adviser or the data protection officer when personal data is involved. In small organisations one person may cover several roles, but a substitute must be planned.

Write names next to the roles and check that they can be reached. If the technical lead is on holiday, the playbook must say who replaces them and with what powers. Whoever manages external IT must know in advance that the call may come outside working hours and which accesses they may use. This part should be discussed with suppliers, because a contract without out-of-hours availability is a problem the document alone cannot solve.

5. Concrete actions, approvals and notification obligations

Every action in the playbook must be concrete: a verb, an object and an owner. Writing 'protect the systems' is useless to anyone. Writing 'isolate the file server from the network, leaving it powered on, and note the time' is useful. Where needed, state the tool or access required and where it is kept, because during an incident nobody wants to look for the administration account password.

The document must also say when to stop and ask. Switching off a production system or contacting the authority requires explicit confirmation. For personal data, GDPR, the European regulation on data protection, requires notification to the supervisory authority within 72 hours of becoming aware of the breach, when a risk to individuals is likely. If you fall within the scope of the NIS2 directive on the security of network and information systems, transposed in Italy by Legislative Decree 138/2024, the first report must be made within 24 hours. The playbook must indicate who assesses these obligations, with what advice, and which questions to ask in the first hours.

6. Testing and updating the playbook

An untested playbook is a draft. The simplest way to check it is a tabletop exercise, in which the response group reads the scenario, takes decisions and discovers where information is missing. Gaps emerge immediately: a phone number nobody has any more, an access that depends on a person who is on holiday, a step that assumes a system retired long ago.

Update the document after every test, after every real incident and whenever systems, suppliers or people change. Assign an owner to the document and a review date. Keep an accessible copy even when the corporate network is down, because a playbook stored only on the affected system is of no use. Exercise methods deserve a dedicated guide.

7. Common mistakes when writing one

The most common risk is treating the playbook as a document to be filed away. It is needed when the network is slow, email is compromised and someone asks what to do now. If it does not work under those conditions, it must be rewritten, not simply read more carefully. The best test is to ask whether someone who has never seen the document could follow it with a phone in hand. The mistakes repeated most often are listed below.

A second mistake is relying on templates found online without reading them. A template is useful as a structure, but the steps must reflect your systems, your suppliers and your obligations. Every sentence you cannot verify in your environment should be removed or marked as to be confirmed. It also helps to have the document read by someone who did not write it, because the author takes for granted many things that others do not know.

  • Writing a long document that nobody reads under pressure
  • Copying a generic template without adapting it to real systems
  • Assigning every step to a single person with no substitute
  • Not stating who can approve actions that halt the business
  • Forgetting suppliers and their out-of-hours contact channels
  • Not providing an alternative communication channel if email is compromised

8. Further reading

The general playbook should be completed with documents for individual scenarios. Topics that deserve their own guide are: what to do in the first hours of a ransomware attack, how to handle a compromised account after a successful phishing attempt, how to assess a data leak, how to prepare for a DDoS attack and how to react to the compromise of a supplier in the supply chain. Also covered are the preservation of digital evidence, crisis communication, tabletop exercises and the closure checklist.

If you read only one further guide, choose the one on the scenario you have classified as high priority in your table. Straight after, read the one on preserving evidence, because the choices made in the first hours determine what you will be able to prove later. The rest can follow at your own pace, depending on the needs of your business. A legal adviser can help you decide which scenarios have the highest priority from a legal point of view.

9. How to start

This week, take the scenario that would halt your business the most and write, on a single page, the first actions someone should take, with the name of the person who takes each one. Do not aim for perfection: the page is there to bring out questions. If you cannot write something, flag it as an open question rather than inventing an answer. Open questions are the most useful output of the first week.

Then bring together the people who would have a role, ask your IT supplier what out-of-hours availability it guarantees, and check that the document can be read without access to the corporate network. Take the result to the next management meeting and decide who is responsible for it. The document must have a name, a date and an owner from its first version, otherwise it will remain a draft forever.

Frequently Asked Questions

How long should an incident response playbook be?

There is no right length. A good playbook takes a few pages per scenario, because it has to be read on your feet during an emergency. If a document needs several readings to understand what to do in the first hours, it is too long for its purpose. Technical detail can go in an annex, while the operational part must be readable immediately by whoever has the phone in hand.

Who should write the playbook: in-house IT or an external supplier?

A shared drafting process is usually best. The IT manager or the supplier knows the systems and can describe the technical actions. Management must decide who approves actions that halt the business, and the legal adviser or data protection officer must check the notification parts. A supplier can prepare the draft, but the document must be approved by the business and tested with the people who will use it.

Does a small business need a playbook too?

Yes, but in a reduced form. Even a small business must know whom to call, which systems to isolate, who decides to switch things off and where to find supplier contacts if email is compromised. One page per scenario, with roles and contacts, is often enough. The difference lies in clarity, not in the number of pages.

Should the playbook state whether to pay or not to pay a ransom?

The playbook should not make this decision in advance as if it were obvious. It should state who assesses it, with what legal and technical advice, and which information is needed to decide. Paying does not guarantee the recovery of data or the absence of further harm. The choice must be made case by case, with experts, taking into account obligations towards the competent authorities.

How often should the playbook be updated?

It should be reviewed after every exercise and after every real incident. It should also be updated when systems, suppliers, managers or out-of-hours arrangements change. Set a periodic review date and a document owner. A playbook with outdated contacts is more dangerous than one never written, because it looks reliable.

What is the difference between a playbook and an incident response plan?

The plan describes principles, roles, objectives and how the response is organised. The playbook is the operational version for a specific scenario, with the steps, tools and owners. The plan says that a process exists. The playbook says what to do when a ransomware attack or a compromised account happens. You need both, and the plan comes first.

Does having a playbook mean you comply with the regulations?

No. A playbook is an operational tool, but the obligations arising from GDPR or NIS2 depend on the scope of your activity and must be verified with a consultant. The document helps you meet notification deadlines and shows that the response is organised, but it does not replace the legal assessment.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →