If you have read our introduction to ZTNA and VPN, you know the basic difference in the ZTNA vs VPN question: a VPN puts a device on your network, while ZTNA grants access to specific applications after checking who and what is asking. This guide is for the next step, deciding what to do about it in your own business.
The decision comes down to four questions
1. Where do your applications live?
If most applications are cloud based, such as Microsoft 365 and software as a service, you may not need a VPN for them at all. Identity controls like conditional access do the work. If you still have servers and applications in an office or data centre, you need a way to reach them, and that is where a VPN or ZTNA earns its place.
2. How much do you trust the devices?
Personal or unmanaged devices are a risk on any network. ZTNA and conditional access can require that a device is enrolled, encrypted and patched before it reaches company data. A traditional VPN checks identity but often does less about device health. Good endpoint security and device management narrow this gap either way.
3. How much damage could one stolen login do?
With a flat VPN, a stolen login may expose file servers, printers and management consoles. With ZTNA, access is limited to the applications that person uses. If your data is sensitive, as with law firms, accountants and financial advisors, limiting that reach is worth the effort.
4. How much complexity can you manage?
A VPN is familiar and quick to set up. ZTNA and zero trust policies need more thought upfront but are easier to scale as you add cloud applications and remote staff. A managed service provider can carry that complexity for you.
Side by side
| Factor | VPN | ZTNA |
|---|---|---|
| Security model | Trust after connecting | Verify each request |
| Blast radius of a stolen login | Large | Small |
| User experience | Connect first, then work | Mostly seamless |
| Performance | Traffic often routed through the office | Direct to the application |
| Setup effort | Low | Moderate |
| Fits legacy systems | Yes | Sometimes, with connectors |
A sensible path for most small businesses
- Start with identity. Enforce multi-factor authentication and use Microsoft Entra ID conditional access to control who gets in and from which devices.
- Shrink what needs a VPN. Move applications to the cloud where it makes sense.
- Tighten the VPN you keep. Require MFA, restrict access by group and log connections.
- Add ZTNA gradually. Introduce it for the most sensitive applications first.
- Review each year. Remove old accounts and unused access rules.
This staged approach improves zero trust security without a disruptive project.
Want the wider picture? Our guide to cybersecurity assessments shows how remote access fits into an overall review.
When keeping a VPN is fine
A VPN is a reasonable choice for a small team with a few on site systems, a simple setup, and strong MFA. Do not replace something that works because a vendor says it is outdated. Replace it when it no longer fits your risk or your applications.
We can review your applications, devices and users and recommend a practical remote access design.
Talk to our security teamFrequently asked questions
Can we use ZTNA and a VPN together?
Yes. Many businesses run both for a period, using ZTNA for modern applications and a VPN for legacy systems.
Is ZTNA more expensive than a VPN?
It can cost more in licensing and setup, though it may reduce other costs such as hardware and support time. Compare total cost for your situation.
Will remote staff notice the change?
Usually only positively, as access to cloud applications becomes quicker and sign in prompts become more consistent.
Related service: Cyber Security Assessment
Last updated



