A practical cybersecurity checklist for Ontario businesses with 10 or more staff, built on the Canadian Centre for Cyber Security baseline: 12 controls, what done looks like, and what to fix first.
TL;DR You don’t need an enterprise security program. You need a short list of controls that are actually in place, written down and checked. The 12 below follow the Canadian Centre for Cyber Security’s guidance for small and medium organizations. If you can only do three this month, make them MFA on every account, backups you’ve restored from, and a phone-call rule for payment changes.
A small business cybersecurity checklist is a short list of security controls you can confirm, one by one, as done or not done. It turns “are we secure?” into questions an owner can answer, and it’s the starting point for any cybersecurity services engagement worth paying for.
I’m Adam Bowles, Partner and CEO of ACT360. This checklist is written for Ontario businesses with 10 to 200 staff: enough people, accounts and devices that security can’t live in one person’s head anymore, but not enough to justify a full-time security team. Print it, go through it with whoever handles your IT, and mark each line honestly.
What Should a Small Business Cybersecurity Checklist Include?
A small business cybersecurity checklist should cover identity, devices, email, data, people, payments, vendors and incident response. Each item needs a clear “done” standard, an owner, and a date it was last checked.
You don’t have to invent the list. The Canadian Centre for Cyber Security publishes baseline cyber security controls for small and medium organizations, covering incident response, patching, security software, secure configuration, strong authentication, employee training, backup and encryption, mobile devices, perimeter defences, cloud and outsourced IT, websites, access control and portable media. Its shorter foundational actions for small organizations narrow that to six starting points.
The 12 controls below take that guidance and put it in the order we’d tackle it for a typical Ontario office, with the questions an owner can actually check.
Why Does a Cybersecurity Checklist Matter for Ontario Businesses?
Because incidents hit businesses of every size, and the most common attacks are simple ones. A checklist makes sure the basic controls are really in place instead of assumed.
Statistics Canada’s 2025 survey of businesses with 10 or more employees found that 16% were impacted by cyber security incidents. That’s 15% of small businesses with 10 to 49 staff and 21% of medium ones with 50 to 249. Among impacted businesses, scams and fraud were the most common method at 55%, and ransomware was involved for 8%.
The same survey found that 34% of businesses had cyber risk insurance in 2025, up from 22% in 2023. If you’re one of them, you’ve already seen how many of these 12 items appear on the application. Our guide to cyber insurance requirements in Ontario covers what underwriters ask.
Basic controls are also less common than people assume. In 2023, only 26% of Canadian businesses had written cyber security policies, and 22% trained non-IT staff.
What Are the 12 Controls on the Checklist?
The 12 controls are grouped into five areas: accounts, devices, email and data, people and payments, and outside access with incident response. Use the table to mark each one as done, partial or missing.
| # | Control | Done looks like |
|---|---|---|
| 1 | MFA on every account | Every staff, admin and remote access login asks for a second factor; legacy sign-ins are blocked |
| 2 | Admin accounts locked down | Few admins, separate admin logins, company-owned, two emergency accounts |
| 3 | Automatic patching | Windows, macOS, browsers and key apps update on a schedule, and someone checks the report |
| 4 | Endpoint protection | Every laptop and desktop runs managed security software that someone actually monitors |
| 5 | Email security | Filtering, attachment and link scanning, and a report button staff know how to use |
| 6 | Backups you’ve restored from | Daily backups, one copy offline or immutable, a restore tested in the last quarter |
| 7 | Staff training | Short regular sessions plus phishing simulations, tracked |
| 8 | Payment verification rule | No banking change without a call to a known number, plus dual approval |
| 9 | Access reviews and offboarding | Accounts removed on the last day; quarterly check of who can see what |
| 10 | Devices and Wi-Fi | Encrypted laptops, a separate guest Wi-Fi, firewall firmware current |
| 11 | Vendor and remote access | A list of every outside party with access, each using MFA |
| 12 | Incident response plan | One page: who to call, what to shut off, how to reach your insurer and bank |
Don’t score yourself generously. Expect a few partials, and that’s fine. The point is to see them.
Which Controls Should You Fix First?
Fix the controls that stop the most common and most expensive incidents first: MFA, tested backups and a payment verification rule. Then admin accounts, patching and endpoint protection. Training, access reviews and the rest follow.
- Turn on MFA for every account, starting with admins, finance and remote access.
- Restore one real file from backup this week to prove the backups work.
- Write a rule that banking changes always need a phone call to a known number.
- Cut admin accounts down to the few people who truly need them.
- Confirm patching and endpoint protection reports reach someone who reads them.
- Schedule a short phishing training session for finance and leadership.
- Write a one-page incident plan and print it, so it’s there when systems aren’t.
Why this order? Microsoft says MFA together with blocking legacy authentication stops more than 99.9% of common identity-related attacks. Backups decide whether ransomware is a bad week or a closed business. And a payment rule costs nothing.
How Do You Check Accounts and Access?
Check that MFA covers every login, that admin rights are limited to a few named people, and that ex-employees have no remaining access. Any one of these gaps can hand an attacker a working login.
Questions to ask whoever manages your IT:
- Can anyone in our Microsoft 365 tenant sign in with just a password? Show me.
- How many people have Global Administrator rights, and are any of them shared logins?
- When did the last person leave, and when was their account disabled?
- Who outside the company can sign in to our systems? Former IT providers, software vendors and accountants count.
- Do staff use a password manager, or do passwords live in a spreadsheet?
The Cyber Centre suggests passwords of at least 12 characters, or a passphrase of at least four words and 15 characters, with MFA added wherever it’s available. Our MFA implementation guide walks through the rollout step by step.
How Do You Check Backups and Devices?
A backup passes only if someone has restored from it recently and at least one copy can’t be reached or changed from your network. Devices pass if they’re patched, protected, encrypted and accounted for.
For backups, ask three things. When did we last restore something, and how long did it take? Is one copy offline or immutable, so ransomware can’t encrypt it? Does the backup include Microsoft 365 email and files, or just the server? Our post on data backup best practices goes deeper, including why Microsoft 365’s own retention isn’t a backup.
For devices, get a list. Every laptop, desktop and server, who uses it, whether it’s encrypted, and when it last updated. A device nobody can name is the one that never gets patched. Windows 10 reached end of support in October 2025, so anything still running it belongs at the top of the list.
How Do You Check People and Payments?
Check that staff have had recent phishing training, know how to report a suspicious message, and that nobody can change a vendor’s or employee’s banking details on the strength of an email.
Fraud is where small mistakes turn into large losses, so give this section real attention:
- Payment changes: a call to a phone number already on file, never one from the email.
- Dual approval on new payees and changed banking details.
- A report button in Outlook, and staff who’ve been told what happens when they use it.
- Short, regular training for finance, payroll and leadership first.
One of our Ontario clients learned why the hard way, without losing anything. A business partner received a convincing email from a lookalike domain asking to change banking details on a six-figure payment. The partner paused and asked. Our investigation found no breach in the client’s systems, and the client added phone verification and dual approval afterward. Our guide to phishing awareness training for Ontario businesses covers how to build that pause into your team.
What Should Your Incident Response Plan Cover?
A small business incident response plan should fit on one or two pages: who decides, who to call, what to disconnect, how to reach your insurer and bank, and where the plan lives when your systems are down.
Keep it short enough that people will read it. Include:
- Who’s in charge during an incident, and their backup
- Phone numbers for your IT provider, insurer, bank and lawyer, on paper
- What to disconnect first if ransomware appears
- How you’ll talk to staff and customers if email is down
- When privacy breach reporting may apply, and who decides
The Cyber Centre lists an incident response plan as the first of its baseline controls for a reason: it’s the control that decides how the rest of a bad day goes. Our article on cybersecurity as a business leadership issue explains why the owner, not just IT, should sign off on it.
Is There a Certification That Proves You’ve Done This?
Yes. CyberSecure Canada is a federal certification program for small and medium organizations based on Canada’s national baseline security standard. It isn’t something every business needs, but some customers and supply chains ask for it.
The Cyber Centre describes CyberSecure Canada as a program that helps small and medium organizations implement controls from CAN/CIOSC 104:2021, Canada’s baseline cyber security standard for small and medium organizations. ISED stepped back as program authority on March 31, 2023, and certification information now comes from the Standards Council of Canada. If a customer or contract asks for formal certification, this checklist is a good way to find your gaps before an audit.
If you want an outside view before going that far, our post on what a cybersecurity assessment actually covers explains what a proper review looks at.
Where ACT360 Fits
We start with the Assess and Comprehend steps of our ACTION approach: what’s actually running, what data matters most, and what you’re trying to protect, before recommending anything. From there, ACT360’s cybersecurity services cover most of this checklist: monitoring and threat response, endpoint and Microsoft 365 identity protection, email threat protection, security awareness training with phishing simulations, patch management, tested backups and the documentation insurers and customers ask for. Paired with managed IT, the checklist becomes something we report on every quarter instead of something you remember once a year.
Final Thought
Pick a date this month, book an hour with whoever manages your IT, and go through the 12 lines together. Mark each one done, partial or missing. Then fix MFA, backups and the payment rule first.
If you’d like help, book a free IT Readiness Assessment. We’ll go through the checklist with you and tell you plainly which gaps matter and what they’d take to close. You can also call 705-739-2281 or email [email protected].