06 / Remote access

VPN or zero trust: what changes for a small business?

Compare business VPN and zero-trust access concepts by application scope, identity checks, device posture and operational ownership.

Evidence-led guideSources checked 16 November 2026

The decision in brief

The question is not whether zero trust sounds more modern. It is whether a remote worker needs access to one application, an entire network, or a protected administrative environment.

What matters most

  • List actual applications and users before buying access software.
  • Network location alone should not grant broad implicit trust.
  • Revocation, device policy and support may matter more than product branding.

Start with the resource being protected

A conventional VPN can provide an encrypted path into a network. Depending on configuration, connected users may gain access to more network resources than they need. A resource-focused access design aims to grant only the appropriate service and permissions to an authenticated user or device.

NIST SP 800-207 describes zero trust as a set of architectural principles, not a single branded product. A well-run VPN deployment can still be appropriate for some workloads, especially where applications need network-level connectivity.

  • Which application or network resource must be reached?
  • Which identities and devices may reach it?
  • What access remains after a session or employment ends?

Inspect authentication and session decisions

Evaluate the identity provider, MFA, device health, session controls, application logging and role permissions. Confirm whether the service can grant access only to an application or must expose an entire subnet.

A vendor may describe a product as zero trust while leaving critical controls to the buyer’s configuration. Test those policies with a typical staff member, an administrator and a leaver account.

  • Strong authentication before access.
  • Least-privilege access to defined resources.
  • Quick revocation and auditable activity.

Include support, continuity and privacy

Understand how remote work continues during identity-provider outages, who controls emergency access, and how client software is deployed and updated. For cross-border services, review where personal information is processed and contractual obligations rather than treating an encryption feature as legal compliance.

A decision record should explain why the chosen access pattern fits the business’s actual applications, devices, suppliers and recovery needs.

Important distinction: A VPN is not categorically obsolete, and a zero-trust label does not independently prove safer implementation.

Questions to ask before buying

Use these as a written evaluation checklist rather than accepting the first sales proposal.

  1. What needs access, and what should never be exposed?
  2. Can we revoke a compromised device or employee immediately?
  3. Who maintains policies and handles outage recovery?
  4. Can the service operate on our actual software and networks?

Evidence and sources

These links identify the origin of the supporting standards, government advice and vendor descriptions. Source links are not endorsements. Time-sensitive features and commercial terms require fresh verification.

  1. NIST: Zero Trust Architecture, SP 800-207 · Checked 2026-11-16
  2. NIST: Implementing Zero Trust Architecture, SP 1800-35 · Checked 2026-11-16
  3. CISA: Guidance for MSPs and Small and Mid-sized Businesses · Checked 2026-11-16
Editorial note. This is independent buying guidance, not a hands-on product test, legal assessment, security audit, vendor endorsement or guarantee. No affiliate links appear in this guide.