Zero trust gets sold as a product. It is not one. It is a way of designing access so that being "on the network" no longer means being trusted. The old model was a castle with a moat: hard on the outside, soft on the inside. Once an attacker got past the VPN, they could reach almost everything. Zero trust removes that soft interior.
What Are the Core Principles of Zero Trust?
The U.S. National Institute of Standards and Technology describes zero trust architecture in NIST SP 800-207, and the Canadian Centre for Cyber Security publishes guidance on the same ideas. The principles boil down to:
- Verify explicitly. Every request is authenticated and authorized using identity, device, location and risk, not just a password.
- Least privilege. People and systems get the minimum access needed, ideally only when needed.
- Assume breach. Design as if an attacker is already inside: segment, monitor and limit how far they can move.
What Does Zero Trust Look Like for a Small Business?
You do not need a large architecture program. For a typical 50-person Canadian firm on Microsoft 365, zero trust in practice looks like this:
| Area | Old approach | Zero trust approach |
|---|---|---|
| Sign-in | Password, maybe MFA | Phishing-resistant MFA plus conditional access |
| Devices | Any laptop can connect | Only managed, healthy devices reach company data |
| Remote access | Full-network VPN | App-level access (ZTNA) or cloud apps directly |
| Admin rights | Everyone is a local admin | Separate admin accounts, just-in-time elevation |
| Network | Flat office network | Segmented: guests, staff, servers, cameras, payment devices |
| Monitoring | Logs nobody reads | Continuous monitoring of identity and endpoint behaviour |
Where Should You Start?
Pick the steps with the biggest payoff:
- Identity first. Enforce MFA everywhere and block legacy authentication. Move admins to phishing-resistant MFA.
- Device compliance. Enrol laptops in Intune or similar and require compliant devices for access to email and files.
- Remove standing admin rights. Staff should not be local administrators on their laptops.
- Shrink the VPN. If most work happens in Microsoft 365 and SaaS, the VPN may only be needed for a few legacy apps. Restrict it to those.
- Segment the network. Put printers, cameras, building systems and guest Wi-Fi on separate segments.
- Watch identity and endpoints together, so a suspicious sign-in and a suspicious process on the same user's laptop are connected.
Our guide to securing Microsoft 365 covers the identity pieces in detail.
Is Zero Trust Worth It for a Small Business?
The principles are, absolutely. The full enterprise program usually is not. A Regina insurance brokerage does not need a multi-year zero trust roadmap. It needs MFA that resists phishing, managed devices and someone watching. That captures most of the benefit at a fraction of the effort. Be wary of vendors who say a single product makes you "zero trust".
How Does Zero Trust Relate to Frameworks?
Zero trust supports the Protect and Detect functions of the NIST Cybersecurity Framework and many CIS Controls, and it maps well to the Cyber Centre's baseline controls for SMBs. If you are choosing a framework, see Which cybersecurity framework should a small business use?. For network design and remote access, our network and firewall security team can help plan a staged move away from flat networks and broad VPNs.