Reducing ransomware risk at a small business
Review the access paths ransomware can use, protect recovery copies and assign someone to security alerts before an incident interrupts work.

Ransomware can interrupt work by encrypting files or blocking systems. Attackers may also steal information and threaten to publish it. Restoring files won’t resolve every consequence of a stolen-data incident.
For a small business, the useful starting point is a review of how someone could get in, what that access would reach and how you’d recover. Give each finding an owner and a practical next step.
Look at the routes into your systems
The Cyber Centre’s ransomware playbook describes entry through phishing, compromised accounts and vulnerable systems. It also explains how attackers can spread through connected networks and target available backups.
List the services exposed to the Internet, including remote access, email and business applications. Check who maintains them, whether they’re still supported and how urgent security updates are handled.
Include access held by suppliers and former staff. A tool that’s outside your main identity system still needs an owner, a way to remove access and sign-in protection such as MFA.
Strengthen sign-in and limit what accounts can do
Use unique passwords where passwords remain necessary and enforce MFA on supported services. Prioritize administrator accounts, email and remote access. Check the exceptions instead of relying on a count of enrolled users.
The Cyber Centre’s phishing-resistant MFA guidance explains why an attacker can intercept some sign-in flows even when a person approves MFA. Supported FIDO2 methods can resist that interception. Number matching and one-time codes don’t offer the same resistance.
Keep administrative work separate from everyday email and browsing. Limit account permissions to the work required. A stronger sign-in method doesn’t make an infected device or stolen session harmless.
Decide who handles security alerts
Ask IT which events are monitored and who investigates them. Useful review areas include unusual sign-ins, new external forwarding, unexpected administrator changes and suspicious activity on computers and servers.
Write down in the support agreement what’s monitored and when. A security product being installed doesn’t tell you whether someone receives its alerts, how they investigate or when they’re available.
Have staff report unexpected prompts and messages promptly. Give them a reporting route that still works when their work email is unavailable.
Check the recovery path
Identify the data and systems needed to resume essential work. Check whether an attacker using production administrator access could also change or delete the backup copies.
Keep protected recovery copies and test restoration in a separate environment. Record the restore point, missing dependencies and time needed to make the recovered system useful. Agree how much lost work and downtime the business can tolerate.
Immutable storage, offline copies and separate backup administration can address different failure paths. Choose the combination for your systems. A backup job can report success and still fail to restore, so test it.
Prepare the first decisions
Keep an incident contact list outside the systems it describes. Include IT, the person who can make business decisions, your insurer if applicable and the people responsible for privacy and legal advice.
If ransomware is suspected, use the response plan and contact the designated responder through a trusted channel. Avoid wiping systems or reconnecting them before the responder has considered containment and evidence. Don’t restore into an environment that’s still compromised.
The Cyber Centre playbook directs victims to local police, the Canadian Anti-Fraud Centre and the Cyber Centre. Privacy reporting is a separate assessment. Where PIPEDA applies, the Privacy Commissioner’s breach guidance explains reporting and notification when there’s a real risk of significant harm, along with breach-record requirements. Provincial and sector rules may also apply.
Run a discussion exercise before an incident: work email is unavailable, shared files won’t open and a supplier needs an answer. Record the decisions you couldn’t make and fix the missing contacts, access or recovery steps.


