Cybersecurity

Preparing for a Cyberattack: An Incident Readiness Guide for SMEs (2026)

March 24, 2026 · 7 min read

Preparing for a Cyberattack: An Incident Readiness Guide for SMEs (2026)

Cybercriminals do not wait until a business is ready before they strike. Ransomware, stolen passwords and fraudulent payment requests hit small and mid-sized businesses every week, often outside office hours. You cannot rule out an attack entirely, but you can decide how much it will cost you. Preparation is what turns a cyberattack into a bad day instead of a bad month.

This guide covers both sides: what to put in place before an attack to limit the damage, and what to do, step by step, when one happens.

The threats you are preparing for

A good plan starts with knowing what you are planning for. The most common attacks against SMEs fall into a few families:

  • Malware: any malicious software that enters your systems, usually through an email attachment, a link or a compromised website, to steal data, spy on activity or damage files.
  • Ransomware: malware that encrypts your files and servers, and often copies your data first, so that attackers can demand a ransom to decrypt them and threaten to publish what they took.
  • Phishing: fraudulent emails, texts or calls designed to trick someone into giving a password, opening a malicious file or approving a payment. Our guide to phishing attacks shows how to spot them.
  • Business email compromise: an attacker takes over or imitates a real email account (yours, a supplier's or a client's) to redirect payments or request sensitive information.

Each of these leads to the same questions: can you keep working, can you recover your data, and who do you need to inform?

Before an attack: six things to put in place

1. Backups that survive ransomware

Backups are your last line of defence, and ransomware groups know it: they look for backups and try to delete or encrypt them first. A backup strategy that holds up follows a few rules:

  • Follow the 3-2-1 rule: three copies of your data, on two different types of storage, with one copy off-site.
  • Keep at least one copy immutable or offline, so it cannot be changed or deleted even with administrator passwords.
  • Back up your cloud data too. Microsoft 365 and Google Workspace keep your email and files available, but they are not a full backup service.
  • Test your restores. A backup you have never restored is a hope, not a plan. Restore a few files and, at least once a year, a full server.
  • Encrypt your most sensitive data and every laptop, so a stolen device does not become a data breach.

Nexxo manages Veeam backups with immutable copies for this reason: even if an attacker reaches the backup server, those copies cannot be erased.

2. Know what you have

You cannot protect, or restore, what you do not know about. Keep three simple documents up to date:

  • An inventory of your devices, servers, user accounts, cloud applications and the vendors who have access to your systems.
  • A network diagram: a visual map of your routers, firewall, servers, workstations and connections, so a technician can see at a glance what talks to what.
  • A data map: what data you hold, where it is stored, where it flows and who can reach it. If that data includes personal information, Quebec's Law 25 expects you to know where it is anyway.

3. Write an incident response plan

The worst moment to decide who calls whom is in the middle of an attack. A short, written plan answers those questions in advance:

  • Scenarios: list the attacks most likely for your business (ransomware on the file server, a hacked email account, a lost laptop, a fraudulent payment) and rank them by impact.
  • Roles: who leads the response, who decides on business matters, who talks to clients and staff, and who handles privacy obligations. Under Law 25, that last role belongs to the person in charge of the protection of personal information.
  • Contacts: your IT or security partner, your cyber insurer, a lawyer, your bank and key suppliers, with phone numbers that do not depend on your email working.
  • A plan B for communication: if email and Teams are down or compromised, how will you reach each other? Keep a printed copy of the plan and contact list.
  • Decision rules: who can approve shutting down systems, contacting police or engaging outside experts.

4. Check your cyber insurance

Cyber insurance can cover response costs, recovery and business interruption, but only under its conditions. Read your policy against the scenarios you listed. Many insurers now require MFA, endpoint detection and tested backups before they will cover a claim, and some require you to call their approved response team first. Review those clauses at every renewal.

5. Have someone watching

Attacks are often launched at night or on weekends, when nobody is looking. Endpoint detection and response (EDR) tools spot suspicious activity, but someone has to act on their alerts. You can train or hire internal staff, or rely on an IT partner that monitors your systems around the clock. Our article on EDR vs antivirus explains what that monitoring involves.

Your employees are part of the picture too. Short, regular awareness training on phishing and fraudulent payment requests prevents many incidents before they start.

6. Practise

Once a year, walk through one scenario with your team in a tabletop exercise: "It is Monday morning and the file server is encrypted. What do we do?" You will find the gaps in your plan in an hour, instead of during a real attack. Pair it with a real restore test.

During and after an attack: what to do, step by step

1. Contain the damage

Disconnect affected computers from the network (unplug the cable, turn off Wi-Fi) rather than shutting them down, unless your IT partner tells you otherwise; powering off can erase useful evidence. If an email account is compromised, reset its password and sign out all sessions. Do not delete anything yet.

2. Call for help early

Call your IT or security partner and your cyber insurer right away. The first hours count, and some insurers only cover costs if they are informed quickly and their process is followed.

3. Identify what happened

Work out where the attack came from, which systems and accounts are affected, and what data may have been accessed, copied or encrypted. Was it an employee error, a stolen password, a vulnerable system?

4. Document everything

Keep a timeline: what was seen, when, by whom, and what actions were taken. You will need it for your insurer, for any report to authorities and for your own review.

5. Meet your Law 25 obligations

If personal information is involved, Quebec's Law 25 applies. You must assess whether the incident presents a risk of serious injury to the people concerned. If it does, you must notify the Commission d'accès à l'information and those people. Every confidentiality incident, serious or not, must be recorded in your incident register. Our guide to the confidentiality incident register explains what to record, and our Law 25 compliance guide covers the rest of the law.

6. Clean up and recover

Remove the attacker's access: reset passwords, revoke suspicious sessions and remote access, and patch the weakness that let them in. Restore systems from clean, verified backups, starting with what the business needs most. Watch closely for signs that the attacker is still present.

7. Report and learn

You can report the incident to the police and to the Canadian Centre for Cyber Security. Once systems are stable, hold a short review: what worked, what did not, and what will change. Then update your plan.

Preparation pays off. In one of our published case studies, a client hit by ransomware had the attack contained and its systems restored over a single weekend, because monitoring, backups and a response process were already in place.

FAQ

What is the first thing to do if we suspect a cyberattack?

Isolate the affected devices from the network without shutting them down, then call your IT or security partner and your insurer. Avoid deleting files or trying to clean things up yourself before the scope of the attack is understood.

Should we pay the ransom?

There is no simple answer, and the decision should never be made alone. Paying is no assurance that you will get your data back or that it will not be published, and it can make you a target again. Talk to your insurer, your lawyer and your security partner first. Good, tested backups are what give you the option of not paying.

When do we have to notify the Commission d'accès à l'information?

Under Law 25, you must notify the Commission and the people concerned when a confidentiality incident involving personal information presents a risk of serious injury. Every incident, even minor, must also be recorded in your incident register.

How often should we test our backups?

Restore a few files regularly, for example every month or quarter, and do a full restore test of a critical system at least once a year. Also test after any major change to your servers or backup setup.

Do we really need an incident response plan as a small business?

Yes, and it does not need to be long. Two or three pages that list roles, contacts and the first steps for your main scenarios are enough to save hours of confusion during an attack.

Who should be on our incident response team?

At minimum: a decision-maker from management, your IT or security partner, the person in charge of personal information under Law 25, and someone responsible for communication with staff and clients. Add your insurer and lawyer as external contacts.

Get ready before you need it

Nexxo monitors our clients' systems 24/7, picks up critical issues in under 15 minutes and manages the backups, detection and response that keep an attack from turning into a crisis. Our cybersecurity services in Montreal include helping you build and test your incident response plan. Book a free assessment to see how ready your business is today.

← Back to Blog