Sophos ZTNA
2025.02 commercialThe section your link pointed to isn't on Sophos ZTNA's page any more, so we've brought you to the top.
Sophos ZTNA is a zero-trust network access solution that verifies user and device identity before granting access to applications and resources.
Summary
Sophos ZTNA is a commercial zero-trust network access service that replaces traditional VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. access with per-application, identity-based connections to internal resources. It runs as a cloud service managed through Sophos Central, with a lightweight agent installed on endpoints and gateways deployed to protect resources on-premises or in the cloud. It suits IT and network security teams responsible for remote access who want to avoid managing VPN infrastructure directly, and it sits in the secure-access category alongside other ZTNA offerings that are gradually displacing VPNsVPNsA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection.. Sophos Central handles certificate issuance and renewal for gateways automatically, agents can be configured to leave local traffic untouched rather than hairpinning it through a tunnel, and domain controllers can be added as agent-based resources for connectivity behind them. With 8 releases in the window tracked, the product is under active, incremental development.
Sophos ZTNA is a zero-trust network access solution that verifies user and device identity before granting access to applications and resources.
Sophos ZTNA publishes no documentation we track, so the description above is written from general knowledge rather than the vendor's own words.
How Sophos ZTNA helps
Which internal applications can a given user reach without a full network-tunnel VPN?
grants per-application, identity-based connections instead of network-level access, so each request is checked against the resource being requested rather than an open tunnel
Does traffic to a resource on the local network get forced through the tunnel unnecessarily?
can be configured so the agent leaves on-premises traffic untouched, avoiding the hairpin round trip for local resources
Can users reach resources sitting behind a domain controller?
supports adding the domain controller itself as an agent-based resource, giving connectivity to what sits behind it without a separate path
Who has to manage certificate renewal on the gateways protecting these resources?
issues and renews gateway certificates automatically through Sophos Central once Let's Encrypt generation is enabled, removing manual renewal from the job
Is ZTNA available for a deployment in this particular Sophos Central region?
is rolled out across all Sophos Central regions, so availability is no longer tied to where the tenant is hosted
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Sophos ZTNA, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Sophos ZTNA puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
sophos.com, every changeSophos's home page and 1 more page as they looked each month from September 2021 to October 2026: 12 renders, 3 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
9 entries
No entries match these filters.
- August 20262
- May 20261
- January 20261
- June 20251
- April 20251
- March 20251
- January 20251
- July 20241
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →