A small business can rehearse the first conversation of an incident without disrupting its services. This WHEN, NOT IF edition focuses on contact routes, deputies and access to the response instructions.
Your incident response contacts need to be reachable when your company email isn't.
Imagine the account used to coordinate a response is the one you now suspect has been compromised. The plan is saved in that mailbox, the provider's support number is in an old message, and the person who knows the contract is away. That is a planning exercise worth doing before an incident does it for you.
The Canadian Centre for Cyber Security recommends a written incident response plan with responsibilities and contact information. Its guidance is established advice, not a new warning I'm presenting as this week's breach.
For a small business, I'd take one critical service and walk through the first call. Identify the provider's verified support route, the person allowed to request help and a deputy who can cover an absence. Confirm what the provider will ask for, without putting passwords or recovery codes in the contact sheet.
Then choose an alternative communication channel the team has agreed to use. Store a protected, accessible copy of the essential instructions somewhere that doesn't depend entirely on the affected service. A plan sitting behind the broken login is very committed to staying private.
Test this as a tabletop exercise with a fictional scenario. Don't disable accounts or call an emergency line to see what happens. Ask the people involved to find the instructions and explain their next action. Record where they had to guess.
You don't need a thick incident manual to discover that the first phone number is wrong. Start by making sure the people in the plan can actually reach each other.
Breach Readiness Interview from Black Ice Labs: https://blackicelabs.ca/readiness
