A one-page incident response plan
A plan you can read in two minutes beats a perfect plan nobody opens.
What to do
- Who to call first, with names and numbers.
- How to disconnect an infected device.
- Who speaks to staff, customers and the insurer.
- Where a printed or offline copy is kept.
Why it matters
During an attack, people make decisions under stress, often without email or Teams, and sometimes in the middle of the night. A short written plan means nobody has to guess who to call or whether to pull the network cable. It also helps the people who arrive to help, because they get the basic facts at once.
Many insurer policies include an incident hotline and rules about when to report. The plan is the place to write those down, so you do not have to dig out the policy documents while your systems are down.
What to put on the page
- Who leads: one named person and a deputy, with mobile numbers.
- Who to call: your IT supplier, the insurer's incident line and your bank, with numbers that work without your own systems.
- First moves: disconnect the affected device from the network but leave it switched on, and do not pay or reply to the attacker before you have taken advice.
- Who speaks: one person for staff, one for customers, and one for the insurer and the authorities.
- Duties: if personal data may be affected, a breach must normally be reported to Datatilsynet within 72 hours. Note the police too.
- Where things are: backups, admin logins for emergencies, and a list of your most important systems.
How to make it work
Keep a printed copy somewhere people can find it and a copy outside your Microsoft 365, because a plan that lives only in SharePoint is gone when SharePoint is. Put the leader's and deputy's numbers in their phones.
Walk through it once a year. Sit down for half an hour, pick a scenario such as an encrypted file server or a hijacked mailbox, and read the plan step by step. A gap found in a meeting room is better than one found during an attack. Update names and numbers whenever someone leaves.
What to tell your insurer
Insurers ask whether you have a written plan and whether it has been tested. Answer yes to the first only if it is written down, and to the second only if you have actually walked through it. Give the date of the last review.
How Ciras handles the plan
A written plan is not something Ciras can read from Microsoft 365. It goes into the short form in the report that you confirm and sign, alongside backups outside Microsoft and staff training.
Questions
Do we really only need one page?
For a small company, one page with names, numbers and first moves covers what matters in the first hours. Technical runbooks can live elsewhere and be linked from it.
Should we switch off an infected computer?
Disconnect it from the network first. Leaving it on can keep evidence that helps the investigators. Follow your IT supplier's or the insurer's advice once you reach them.
When should we call the insurer?
As early as your policy says, and usually sooner is better. Many policies have their own rules on notice and on which experts you may use, so read them now and copy the key points into the plan.
Who should know the plan exists?
Everyone. Staff do not need to learn it by heart, but they should know where it is and who leads. The most useful line for most people is simply: if something looks wrong, call this number.