Cato ZTNA
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Cato Networks Ltd. · www.catonetworks.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Cato ZTNA at a glance
- Vendor
- Cato Networks Ltd.
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Cato ZTNA 3/5, the mean of 6 judges. Cato ZTNA, from Cato Networks Ltd., is a zero-trust access service that grants per-application, least-privilege access over a private global backbone of Sockets and points of presence. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Cato ZTNA, from Cato Networks Ltd., is a zero-trust access service that grants per-application, least-privilege access over a private global backbone of Sockets and points of presence. The bench scores it highest on access and connectivity and visibility and audit, at 7 across the table, with identity and policy at 6–7: single sign-on over OIDC with Microsoft Entra ID covers client, clientless and admin users, unassigned SCIM users are automatically disabled at the next 40-minute sync, and events stream to fourteen named SIEMs with turnkey Splunk and Microsoft Sentinel setups. Deployment and administration and architecture and assurance trail; the architecture is documented in unusual depth, including the vendor's own statement that active-active tunnels terminate on one point of presence and do not cover its outage. Sovereignty is the weak point at 2–3: headquarters sits in Tel Aviv, and the captured pages state no location for the control plane, logs or identities and name no subprocessors. No meaningful disagreement between judges was flagged. No price, tier or seat minimum appears in the captured pages.
Speaks for it
- Per-application, least-privilege access with clients for Windows, macOS, Linux, iOS and Android plus clientless and browser-extension users
- Entra ID single sign-on over OIDC covers client, clientless and admin users, and SCIM automatically disables unassigned users at the next 40-minute sync
- Raw events, admin audit logs and application flow metrics are exposed by API, with streaming to fourteen named SIEMs and turnkey Splunk and Microsoft Sentinel
- The Socket, point-of-presence and private backbone architecture is documented in unusual technical depth, including the published limitation that active-active tunnels terminate on one point of presence
- A GraphQL API with read and mutation operations, a playground, a sandbox and a deprecation policy gives a small team a real automation surface
Held against it
- Sovereignty scored 2–3: a Tel Aviv headquarters, and no public information on where the control plane, logs or identities are stored, on subprocessors, or on a data processing agreement
- Compliance appears as ISO 27001, SOC 2 and GDPR claims, with no public information on published audit reports, a bug bounty, a status page or an availability commitment
- The captured pages state no log retention period and document no log schema
- No public information on named gateway regions, cloud connectors other than Azure, split tunnelling or always-on client behaviour
- Documented site tunnels use a pre-shared key and Diffie-Hellman group 2 (1024-bit), which buyers should weigh
Best for
- You need per-application, least-privilege access under a single policy, covering managed laptops and contractors through clientless browser users
- Your identity source is Microsoft Entra ID and leaver cutoff matters — users unassigned in the SCIM app are disabled at the next sync
- You run Splunk or Microsoft Sentinel and want turnkey event streaming plus API access to raw events, audit logs and flow metrics
- You connect sites into Azure and want the documented route-based IPsec with BGP, automatic failover and high availability across multiple points of presence
Avoid if
- Your procurement must trace where identities and connection logs are stored and which subprocessors are involved — the published chain stops at a Tel Aviv headquarters and GDPR, ISO 27001 and SOC 2 claims
- Your traffic must not cross a vendor-operated backbone where data loss prevention inspects content — both are part of the documented data path
- You need site tunnels that survive a single point-of-presence outage — the vendor's own documentation states active-active tunnels do not, because both terminate on the same point of presence
The scores
| Criterion | Panel median |
|---|---|
| Access model & connectivity | 3.5 of 5 |
| Identity, access policy & device posture | 3.5 of 5 |
| Logs, audit trail & incident response | 3.5 of 5 |
| Deployment, API & administration | 3 of 5 |
| Architecture, reliability & security assurance | 3 of 5 |
| European sovereignty | 1 of 5 |
Access model & connectivity
Show reasoningHide reasoning
How this is scored
What the product connects and how: a managed gateway VPN with shared or dedicated gateways and dedicated static IPs, a peer-to-peer mesh between devices and servers, access per application or resource (ZTNA), site-to-site links between offices and cloud networks (AWS, Azure, Google Cloud), connectors behind a firewall without inbound ports, the protocols (WireGuard, IPsec, OpenVPN, a vendor protocol), split tunnelling and full tunnelling, always-on and auto-connect, clients for Windows, macOS, Linux, iOS, Android and ChromeOS, the gateway and relay locations, NAT traversal and relays, and access for contractors without a managed device.
0 — Gives no remote access of its own; a browser extension, a consumer VPN for anonymous browsing or a security tool that only filters traffic.
3 — A VPN client that connects users to one gateway or network; site-to-site, per-resource access, the clients per platform and the locations are basic or not described.
5 — Clients for Windows, macOS, Linux, iOS and Android, a modern protocol (WireGuard or IPsec), access to private networks through a gateway or connector without inbound firewall rules, split tunnelling, dedicated static IPs or self-run gateways, site-to-site or cloud network links, and the gateway or relay locations named.
8 — Access per application or resource rather than whole networks, peer-to-peer connections with relays as fallback, always-on and auto-connect, connectors for the major clouds and Kubernetes, gateways in many named regions, private DNS and split DNS, clientless browser access for contractors, and the protocol and encryption choices documented.
10 — Connectivity a distributed company runs on: every access model above in one product, high-availability gateways and connectors with failover documented, performance and throughput published per gateway type, post-quantum or equivalent key exchange documented, and an exit path to run the same network on self-hosted components.
The IT Lead
Per-application access under one least-privilege policy is the core of their pitch, which is exactly what I need to reach the ERP and file server without opening the plant networks, and clientless browser users plus licence-based Cato-allocated IPs cover contractor access and a fixed address for the supplier portal. The Azure tunnel pages document IPsec with IKEv2, BGP and multi-PoP failover, but we found no public information on always-on behaviour, split tunnelling, named gateway regions, or connectors for clouds other than Azure. 1 2 3 4
The DevOps Engineer
Universal ZTNA applies identity- and context-based least-privilege access to every user, device and resource rather than whole networks, with clients for Windows, macOS, Linux, iOS and Android plus clientless browser users, and route-based IPsec tunnels with BGP into Azure Virtual Network Gateways with automatic failover across multiple Cato PoPs. Sites attach through Sockets to a private global backbone with active/active, active/passive and last-resort cellular links. We found no public information on Kubernetes connectors, split or private DNS, or a list of named gateway regions on the captured pages. 1 2 3 4 11
The MSP Technician
Universal ZTNA with a single least-privilege policy per user, device and resource, a client on Windows, macOS, Linux, iOS and Android, clientless and browser-extension users for contractors, and route-based IPsec/IKEv2 with BGP into Azure with automatic failover and high availability across PoPs, carried on a private global backbone. The pages name no PoP locations, describe no split tunnelling, and document only Azure among the cloud links, which keeps it off the top anchors. 1 2 3 4 11
The Operations Manager
Zero-trust access is per application and least-privilege rather than a whole-network tunnel, with a clientless option that suits freelancers on their own laptops, and clients for Windows, macOS, Linux, iOS and Android. Site-to-cloud links to Azure run over route-based IPsec with BGP, automatic failover and high availability across multiple points of presence. I found no public information on split tunnelling, always-on behaviour or the named locations of gateways, so I cannot place it higher. 1 2 3 4
The Information Security Officer
Universal ZTNA is described as least-privilege access to every user, device and resource rather than whole networks, with clients for Windows, macOS, Linux, iOS and Android plus clientless browser users. Site-to-site connectivity to Azure is documented over route-based IPsec with BGP, automatic failover and high availability across multiple points of presence, with tunnel parameters published down to IKEv2, pre-shared key and Diffie-Hellman group 2 (1024-bit). I found no public information on connectors for the other major clouds, named gateway regions, always-on client behaviour, or split DNS. 1 2 3 4 11
The Skeptic
Per-application, least-privilege access is the documented model, with clients for Windows, macOS, Linux, iOS and Android, clientless users and a browser extension, and an Azure link through IPsec IKEv2 with BGP failover across multiple points of presence. We found no public information on named gateway regions, connectors for the other major clouds, split DNS, or always-on client behaviour. The documented site tunnel uses a pre-shared key and Diffie-Hellman group 2 (1024-bit), which buyers should weigh. 1 2 3 4
Identity, access policy & device posture
Show reasoningHide reasoning
How this is scored
Whether access follows identity and the state of the device rather than the network: single sign-on with Microsoft Entra ID, Google Workspace, Okta or any OIDC/SAML provider, SCIM or directory sync so a leaver loses access, multi-factor authentication, groups and per-resource access policies, least-privilege defaults, device posture checks (operating system version, disk encryption, EDR or MDM status, managed device certificates), just-in-time or time-limited access with approval, session lifetimes and re-authentication, and access revoked when a device is lost.
0 — No user identity at all; a shared key or configuration file grants access to the whole network.
3 — User accounts with a password or one identity provider; groups, per-resource policies and device checks are basic or not described.
5 — Single sign-on with Entra ID, Google Workspace and Okta, multi-factor authentication, user groups, access policies that restrict groups to named networks, resources or ports, automatic or SCIM-based deprovisioning, and basic device posture checks such as operating system version.
8 — SCIM provisioning from the major identity providers, per-resource policies with least privilege by default, device posture from EDR or MDM tools (for example CrowdStrike, SentinelOne, Intune, Jamf), just-in-time access with approval and expiry, session re-authentication, policies kept as code, and the policy model documented.
10 — Access control a security team can audit and trust: continuous evaluation of identity and device state during a session, policies tested before they apply, emergency revocation documented, device identity bound to hardware, and the decision for every connection explainable from the logs.
The IT Lead
Entra ID single sign-on over OIDC covers Windows, macOS, iOS, Android and Linux clients, and SCIM provisioning from Entra syncs every 40 minutes with users automatically disabled when unassigned — a leaver loses access the same day, my headline requirement. Access policy weighs identity, device posture, geography and application risk, and token validity forces re-authentication; we found no public information on named EDR or MDM posture sources, just-in-time approvals, or policies kept as code. 2 4 5
The DevOps Engineer
Entra ID single sign-on over OIDC covers client users, clientless users and management admins with configurable token validity and forced re-authentication, and SCIM provisioning syncs users and groups every forty minutes with unassigned users automatically disabled on the next sync. Policy combines identity with device posture, geography and application risk under a single least-privilege policy. We found no public information on posture integrations with named EDR or MDM tools, just-in-time access with approval, or keeping policies as code in Git with Terraform. 2 4 5
The MSP Technician
Entra ID single sign-on over OIDC covers client, clientless and admin users with configurable token validity and re-authentication, SCIM provisioning syncs every 40 minutes and disables a user automatically on unassignment, and access policy weighs identity, device posture, geography and application risk. I found no public information on just-in-time access with approval, posture feeds from named EDR or MDM tools, or policies kept as code. 2 4 5
The Operations Manager
Microsoft Entra ID single sign-on over OIDC covers client, clientless and admin users on all five operating systems, and SCIM provisioning automatically disables an unassigned user on the next sync — exactly the contract-end cutoff I need for freelancers. Policy combines identity, device posture, geography and application risk under one least-privilege policy, and token validity forces re-authentication. I found no public information on just-in-time approval, policies as code or which EDR or MDM tools feed the posture checks, and the documentation states nested group provisioning is not supported. 2 4 5
The Information Security Officer
Single sign-on runs over OIDC with Microsoft Entra ID for client, clientless and admin users, multiple identity providers are supported, and SCIM provisioning automatically disables a user who is unassigned on the next forty-minute sync — a leaver genuinely loses access. Policy is documented as identity plus device posture, geography, application risk and compliance ratings under a single least-privilege rule, and token validity settings with an always-prompt option give session re-authentication control. I found no public information on just-in-time access with approval, named EDR or MDM posture sources, or multi-factor enforcement specifics. 2 4 5
The Skeptic
OIDC single sign-on with Microsoft Entra ID covers client, clientless and admin users with configurable token lifetimes and forced re-authentication, and SCIM provisioning is documented deeply enough to show that a removed user is automatically disabled at the next sync. Policy is described as identity- and context-based, including device posture, geography and application risk. We found no public information on multi-factor enforcement, posture fed from EDR or MDM tools, just-in-time access, or policy as code. 2 4 5
Logs, audit trail & incident response
Show reasoningHide reasoning
How this is scored
What can be seen and proven afterwards: connection and access logs (who reached which resource from which device, when), admin and configuration audit logs, how long logs are kept per plan, log export and streaming to a SIEM (Splunk, Microsoft Sentinel, Datadog, an S3 bucket), alerts on unusual access, a view of active sessions and the ability to end them, DNS logs where DNS filtering is part of the product, and what the vendor states it does not log, such as the content of traffic.
0 — No logs of any kind; the admin cannot see who connected.
3 — A list of connected users or devices; access logs, admin audit logs, retention and export are basic or not described.
5 — Connection or access logs per user and device, an admin audit log of configuration changes, the retention period stated, log export by CSV or API, a view of active sessions or devices with the option to disconnect or revoke them, and a statement of what traffic data is and is not logged.
8 — Log streaming to named SIEM tools, network flow logs per resource, retention of a year or more stated per plan, alerts or webhooks on security events, logs filterable by user, device and resource, and the log schema documented.
10 — An audit trail that holds up in an investigation: every access decision and admin action recorded with its policy and reason, logs signed or tamper-evident, evidence suitable for ISO 27001, NIS2 or DORA audits, full export in an open format, and the customer able to keep logs entirely on its own infrastructure.
The IT Lead
Raw event logs, an admin audit feed for configuration changes and correlated incident stories are all reachable through the API, and events stream to fourteen named SIEMs with turnkey Splunk and Microsoft Sentinel setups — as a Sentinel shop I could wire that in. The pages also show every session tracked in one dashboard and webhook alerts; retention periods, per-plan log keeping and a statement of what traffic data is and is not recorded are not covered in what we captured. 2 6 7 9 11
The DevOps Engineer
The raw events feed is the documented entry point for event logs and security telemetry, an audit feed retrieves admin and configuration change logs, and correlated stories carry incidents with webhooks for link degradation and socket failover. Events stream to fourteen named SIEM tools including turnkey Splunk and Microsoft Sentinel, and every session is claimed to be trackable in one dashboard. We found no stated log retention periods or documented log schema on the captured pages. 2 6 7 9 11
The MSP Technician
A raw events feed, an admin audit feed for configuration changes, application and flow statistics, correlated security stories, webhooks for link degradation and socket failover, and streaming to fourteen named SIEM tools including turnkey Splunk and Microsoft Sentinel — enough to show a client who reached what. Retention periods per plan and a statement of what traffic data is not logged are not given on the captured pages. 2 6 7 9 11
The Operations Manager
There is an API audit feed for admin actions and configuration changes, a raw events feed for security telemetry, per-application flow statistics, and turnkey streaming to fourteen named SIEMs including Splunk and Microsoft Sentinel. Webhooks raise alerts for link degradation and socket failover, and every session is tracked in one dashboard. I found no public information on log retention periods, the log schema or the ability to end an active session, which is what my external auditor will ask about. 2 6 7 9 11
The Information Security Officer
Audit logs of admin actions and configuration changes, raw security telemetry and per-application flow metrics are all retrievable by API, and turnkey streaming to Splunk and Microsoft Sentinel plus thirteen further named SIEM feeds would carry everything to my SOC. Sessions are tracked in a dashboard and webhooks alert on link degradation and failover events. The captured pages state no retention period per plan and do not document the log schema — both questions my auditor will ask. 2 6 7 9 11
The Skeptic
Raw events, admin audit logs, application and flow metrics all have documented API endpoints, sessions are tracked in a dashboard, and events stream to fourteen named SIEM products with turnkey Splunk and Microsoft Sentinel. The captured pages state no retention period, no documented log schema, and no statement of what traffic data is and is not logged — and since data loss prevention inspects the traffic, what the vendor sees of the content is a fair question. 2 6 7 9
Deployment, API & administration
Show reasoningHide reasoning
How this is scored
How the product is rolled out and run by a small IT team or a service provider: time to the first connection, deployment of clients through MDM (Intune, Jamf, Kandji) with preconfigured settings, a central admin console, a documented REST API, a Terraform provider or configuration as code, roles for administrators, several teams, sites or customer tenants in one account, a multi-tenant console for managed service providers, a self-hosted or on-premises edition, the update process for clients and gateways, and support channels and hours.
0 — No central administration; every client is configured by hand with no console.
3 — A web console to add users and gateways; the API, MDM deployment, admin roles and multi-tenant set-up are basic or not described.
5 — A central admin console, a documented REST API, client deployment through MDM with preconfigured settings, admin roles, several networks or sites in one account, client updates managed centrally, and support channels and response times stated per plan.
8 — A Terraform provider or configuration as code, a multi-tenant console for service providers or several organisations, granular admin roles, a self-hosted or on-premises edition documented for production, gateways deployable as containers or cloud images, and webhooks or integrations with ticketing and chat tools.
10 — Administration that scales across many sites and tenants: every setting reachable by API and code with parity stated, staged rollouts of client and gateway updates, a self-hosted edition with feature parity stated, reseller or MSP billing per tenant, and an exit path for configuration and users documented.
The IT Lead
There is a knowledge article for deploying the Windows client through Intune — the install path I care about — plus a single management application, a GraphQL API for both reads and configuration changes with a documented deprecation policy, and CLI, Postman and sample-code tooling on their GitHub. Admin roles, a Terraform provider, a service-provider console and per-plan support response times did not appear in the captured pages. 1 8 9 11
The DevOps Engineer
The management application plus a GraphQL API with both read and mutation operations, a browser playground and GitHub helpers including CLI utilities and Postman collections give a small team a real automation surface, and there is a knowledge-base article for deploying the client with Intune. Multiple sites run in one account with per-site SLA settings, and support runs through the support portal and community. We found no public information on a Terraform provider, a multi-tenant console for service providers, or a self-hosted edition. 1 4 7 8 9 11
The MSP Technician
The Cato Management Application with site analytics, a documented GraphQL API with read and mutation operations, rate limiting and a deprecation policy, GitHub tooling, an MCP server, and an Intune deployment guide for the Windows client. For a provider like me the gap is the MSP story: I found no public information on a multi-tenant console with per-tenant billing, Terraform, granular admin roles or a self-hosted edition. 1 7 8 9 11
The Operations Manager
A central management application plus a GraphQL API supporting both reads and configuration changes, with a browser playground, Postman collections and CLI utilities, is more automation than my hourly-billed provider would need, and a knowledge-base guide covers deploying the Windows client through Intune. A support portal and community forum handle questions. I found no public information on Terraform, granular admin roles, a multi-tenant console for service providers or a self-hosted edition. 1 8 9 11
The Information Security Officer
A central management application, a documented GraphQL API covering both reads and configuration mutations, a sandbox, Postman collections and CLI utilities on the vendor's GitHub, and documented Windows client deployment through Intune make this operable by a small team. Support runs through a portal and community, with no response times stated per plan. I found no public information on admin role granularity, a multi-tenant console for service providers, or a self-hosted edition. 1 7 8 9 11
The Skeptic
A central management application and a documented GraphQL API with a playground, sandbox, deprecation notices, sample code and an MCP server form a real administration story, and an Intune deployment path for the Windows client is documented. We found no public information on administrator roles, a multi-tenant console for service providers, Terraform or configuration as code, staged update rollouts, or support response times per plan. 1 8 9
Architecture, reliability & security assurance
Show reasoningHide reasoning
How this is scored
How the product is built and how its claims are proven: a published architecture showing what the coordination servers, relays and gateways see, whether traffic passes through the vendor or end to end between devices, encryption and key management, open-source clients or servers, independent security audits and penetration tests with reports or summaries published, a vulnerability disclosure or bug bounty programme, high availability and failover of the vendor's control plane, what happens to existing connections when the vendor's service is down, the vendor's own public status page and incident history, and an SLA.
0 — Nothing is published about how the product works or is secured.
3 — Encryption is mentioned in marketing terms; architecture, audits, availability and the vendor's status page are basic or not described.
5 — An architecture overview of clients, gateways and the control plane, the encryption protocol and key handling named, an independent security audit or penetration test stated, a vulnerability disclosure contact, the vendor's public status page, and an availability SLA on the business plans.
8 — A security whitepaper with the data flow and what the vendor can see, open-source clients or core components, audit or pentest reports or summaries published by the auditor, a bug bounty, high availability of the control plane documented, existing connections kept alive when the control plane is down, and the incident history public with post-mortems.
10 — Assurance a regulated buyer can verify: fully open-source and reproducible components, recurring independent audits published in full, the control plane self-hostable with no call home, a documented failure mode for every vendor component, and several years of availability published.
The IT Lead
The socket-and-PoP architecture is documented in real depth — link scoring every few seconds, reroute on degradation, a cellular last resort — including the frank note that active-active tunnels terminate on one PoP and do not cover its outage. ISO 27001, SOC 2 and GDPR compliance are stated, but we found no public information on a status page, a vulnerability disclosure contact or bug bounty, an availability commitment, or open-source components. 3 7 10 11
The DevOps Engineer
The Socket link SLA architecture publishes the data path in detail — what the Socket measures, what the PoP aggregates and validates against its own telemetry, backbone rerouting, and failover including the documented limitation that active-active tunnels terminate on the same PoP. Tunnel encryption parameters are named (IKEv2, shared key, Diffie-Hellman group 2) and ISO 27001 and SOC 2 are stated, alongside a DLP inspection reference architecture. We found no public information on published audit or pentest reports, a vulnerability disclosure programme, a status page with incident history, or an availability SLA. 2 3 7 10 11
The MSP Technician
A real architecture is published — Socket, PoP and private backbone with active/active and active/passive WAN behaviour, last-resort cellular links and rerouting — and the pages state that active-active tunnels do not cover a PoP outage because both terminate on the same PoP. ISO 27001, SOC 2 and GDPR compliance are claimed, but I found no public information on a status page, an availability SLA, published audit reports or a bug bounty. 1 2 3 7 11
The Operations Manager
The link-monitoring architecture is documented in real depth: sockets measure latency, loss and jitter, points of presence validate the numbers and reroute traffic, and even the limitation that active-active tunnels share a single point of presence is published. Site tunnels use IPsec with IKEv2 and stated parameters, and ISO 27001, SOC 2 and GDPR compliance are claimed. I found no public information on published audit reports, a bug bounty, a vendor status page or an availability commitment. 1 3 7 11
The Information Security Officer
The Socket-to-PoP measurement, link scoring and backbone rerouting are documented in real technical depth, and the vendor openly states that active-active tunnels do not protect against a single point-of-presence outage because both terminate on the same PoP — the kind of candour I value. ISO 27001 certification, SOC 2 approval and GDPR compliance are stated, and a Rapid CVE Mitigation programme exists. I found no published independent audit report or penetration test summary, no bug bounty, no public status page and no availability commitment. 1 2 3 7 10 11
The Skeptic
The Socket, point-of-presence and private backbone architecture is documented in unusual technical depth, and the vendor states plainly that active-active tunnels do not survive a point-of-presence outage because both terminate on the same PoP — the vendor's own cloud is in the path. Traffic crosses the vendor's backbone and data loss prevention inspects it there, so the vendor can see content. ISO 27001, SOC 2 and GDPR compliance appear as badge claims; we found no public information on published audit reports, a bug bounty, a status page, control-plane failure behaviour, or a self-hosted edition. 3 7 10 11
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where account data, user and device identities, connection logs and configuration are stored and processed, which party runs the coordination servers, relays and gateways the traffic passes through, and who the subprocessors are (hosting, identity, email, support and payment tools). Independently sourced by the sovereignty pipeline. Gateway and exit locations outside Europe are part of what the product does and are not counted against it; where the logs and identities are stored and who processes them is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting of the control plane and logs unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but the location of the control plane and logs is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting of logs and account data available and an EU contracting entity or EU representative, but parts of the chain (relays, support, identity, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure for the control plane and logs, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record and connection on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The IT Lead
The vendor's headquarters address is in Tel Aviv, and beyond a published privacy policy and GDPR-compliance and certification claims, the captured pages state nothing about where account data, identities or connection logs are stored or processed. We found no public information on the subprocessor chain or a data processing agreement, so for an Austrian buyer the evidence to trace the chain is simply not there. 1 2 7
The DevOps Engineer
The contracting vendor is Cato Networks Ltd. headquartered in Tel Aviv, and it states GDPR compliance, ISO 27001 certification and SOC 2 approval with a published privacy policy. The captured pages give no statement of where the control plane, logs or user identities are stored or processed, and no subprocessor list. For a European buyer the processing chain therefore remains unverified. 1 2 7
The MSP Technician
The registered headquarters are in Tel Aviv, so the contracting entity sits outside the EU, and the pages claim GDPR compliance and publish privacy documents. Nothing on the captured pages says where account data, identities or connection logs are stored, who the subprocessors are, or that a data processing agreement is available. 1 2 7
The Operations Manager
The headquarters and legal address are in Tel Aviv, Israel, and I found no public information on where the control plane, user identities or logs are hosted, which subprocessors are involved, or a published data processing agreement. GDPR compliance and a privacy policy are stated, but that is the whole of the European story these pages give a buyer like me. 1 2 7
The Information Security Officer
The only firm facts are a Tel Aviv headquarters address and GDPR-compliant, ISO 27001 and SOC 2 badges; nothing in the captured pages says where account data, user and device identities, or connection logs are stored and processed, and no subprocessor list appears. For a NIS2 operator that must keep identities and logs in Europe with named subprocessors, I found no public information on data residency, an EU contracting entity, or a published data processing agreement. 1 2 7
The Skeptic
The published headquarters address is Landmark Tower, Tel Aviv, Israel, and the captured pages state no location for the control plane, logs or user identities and name no subprocessors. GDPR compliance is claimed as a badge and privacy pages exist, but we found no public information on a data processing agreement or where connection data is stored. A European buyer cannot trace the chain from these pages. 1 2 7
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per user or per device and tier, minimum seats, what dedicated gateways, static IPs, extra networks or sites cost, which features (SSO, SCIM, device posture, log streaming, longer retention, site-to-site) need a higher tier, the free tier and its limits, the price of a self-hosted or on-premises licence, monthly versus annual billing, minimum term and VAT.
0 — No public prices at all; every customer is a sales call or a partner quote.
3 — A starting price or a free tier exists, but how cost scales with users, devices, gateways or features is unclear.
5 — Tiers are public with a price per user and their main inclusions, but at least one commonly needed piece (dedicated gateways or IPs, extra sites, SSO or SCIM, log retention, the self-hosted licence) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (users, devices, gateways, networks), dedicated IPs and gateways priced, add-ons priced, minimum seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given team size, number of sites, gateways and devices, with every add-on, overage and support fee and the cancellation and data-return terms published.
The IT Lead
No price figures appear anywhere in the captured pages — no tiers, no per-user cost, no minimum seats — and the only pricing-related fact says the number of Cato-allocated IPs depends on the licence and directs buyers to a reseller or the vendor's sales address for more. I cannot begin to budget 140 users plus two plants from public pages alone. 3
The DevOps Engineer
The captured pages contain no price figures, tiers or seat minimums; the only pricing statement says the number of unique Cato-allocated IPs is determined by your license and directs additional IP requests to your reseller or sales. We found no public information from which an annual cost could be computed. 3
The MSP Technician
No price appears anywhere I could quote: IP counts are "determined by your license" with additional IPs via "contact your reseller or sales@catonetworks.com", ZTNA is licensed per user, and the commercial call to action is booking a demo. I cannot put a per-user figure in front of a client from these pages. 1 3 5
The Operations Manager
I found no public prices on the captured pages — licensing is referenced through SDP licences assigned per user and allocated IP counts determined by the licence, and additional IPs mean contacting a reseller or sales. From public information alone I cannot begin to compute what a year would cost my fifty-person firm. 3 5
The Information Security Officer
The only pricing fact I could find is that the number of unique allocated IPs is determined by your licence, with additional IPs available by contacting your reseller or the sales email address. No per-user or per-tier price, minimum seats, term, free tier or self-hosted licence price appears in any page I read. 3
The Skeptic
No price, tier, seat minimum or billing term appears in the captured pages; the only pricing-adjacent statement says the number of allocated IPs is set by your license and additional IPs mean contacting your reseller or sales. An annual cost is not computable from what was captured. 3
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Cato ZTNA
Is Cato ZTNA European?
Not determined: the vendor’s pages as captured do not say where Cato ZTNA is based.
Where does Cato ZTNA store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does Cato ZTNA have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Cato ZTNA?
As of 19 Nov 2026, the panel rates Defguard (3.5/5), Firezone (3.5/5) and Tailscale (3.5/5) highest among the other 19 Business VPN & Zero Trust Access products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Defguard (EU-Made, Poland). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Cato ZTNA alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on pricing on the pages we read (catonetworks.com, catonetworks.com/platform/universal-zero-trust-network-access-ztna, knowledge.catonetworks.com/docs/setting-up-a-cato-ipsec-tunnel-to-your-azure-virtual-network-gateway, knowledge.catonetworks.com/docs/configuring-entra-sso, knowledge.catonetworks.com/docs/scim-provisioning-with-entra-id-formerly-azure, knowledge.catonetworks.com/docs/exporting-xops-stories-to-your-siem and 5 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 9 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.catonetworks.com Checked 17 Nov 2026 Details →
- 2 Access model & connectivity — found from sitemap www.catonetworks.com Checked 17 Nov 2026 Details →
- 3 Access model & connectivity — found from sitemap knowledge.catonetworks.com Checked 17 Nov 2026 Details →
- 4 Identity, access policy & device posture — found from sitemap knowledge.catonetworks.com Checked 17 Nov 2026 Details →
- 5 Identity, access policy & device posture — found from sitemap knowledge.catonetworks.com Checked 17 Nov 2026 Details →
- 6 Logs, audit trail & incident response — found from sitemap knowledge.catonetworks.com Checked 17 Nov 2026 Details →
- 7 Logs, audit trail & incident response — found from sitemap www.catonetworks.com Checked 17 Nov 2026 Details →
- 8 Deployment, API & administration — found from sitemap knowledge.catonetworks.com Checked 17 Nov 2026 Details →
- 9 Deployment, API & administration — found from sitemap knowledge.catonetworks.com Checked 17 Nov 2026 Details →
- 10 Architecture, reliability & security assurance — found from sitemap knowledge.catonetworks.com Checked 17 Nov 2026 Details →
- 11 Architecture, reliability & security assurance — found from sitemap knowledge.catonetworks.com Checked 17 Nov 2026 Details →