Comparison - Pangolin vs. SonicWall
SonicWall firewalls are common in small and mid-sized businesses and with the MSPs that support them, and many of those businesses get remote access from the firewall's SSL VPN and the NetExtender client. SonicWall has been moving its remote access story elsewhere: the SMA 100 appliances have reached end of support, and SonicWall now steers customers toward Cloud Secure Edge, its cloud ZTNA service. This article compares Pangolin with each of SonicWall's options and covers how Pangolin fits next to a SonicWall firewall you plan to keep.
What is Pangolin?
Pangolin is an open-source zero-trust network access platform built on WireGuard. You install a lightweight connector, called a site, on a machine inside a network you want to reach. The site only makes outbound connections, so the network needs no public IP, no port forwarding, and no inbound rule on the firewall.
Anything the site can reach can become a resource, and you grant users, roles, and machine clients access to each one. Public resources go through Pangolin's identity-aware reverse proxy: web apps on your own domains, and SSH, RDP, and VNC sessions in the browser, all behind Pangolin login. Private resources need the Pangolin client and cover hosts, CIDR ranges, private HTTPS, pangolin ssh, and exit nodes. Clients connect to sites peer-to-peer with NAT hole punching and fall back to a relay when they can't.
You can use Pangolin Cloud, self-host the whole stack, or use the cloud control plane with your own remote nodes. Pangolin supports multiple organizations per account, which suits MSPs managing many customers.
What SonicWall offers for remote access
SonicOS SSL VPN runs on SonicWall TZ, NSa, NSsp, and NSv firewalls. Users connect with NetExtender on Windows and Linux, or with Mobile Connect on macOS, iOS, Android, and ChromeOS, which SonicWall is renaming to NetExtender on those platforms. The firewall listens for VPN connections on its WAN interface, authenticates users locally or against LDAP, RADIUS, or SAML, and uses user groups and address objects to decide what each user can reach. SonicWall's Global VPN Client provides IPsec as an alternative.
Secure Mobile Access (SMA) was SonicWall's dedicated remote access appliance line. The SMA 100 series is now end of sale and end of support. The SMA 1000 series continues as physical and virtual appliances with a clientless browser portal and the Connect Tunnel client.
Cloud Secure Edge (CSE), formerly Banyan Security, is SonicWall's cloud security service edge. It includes ZTNA, a cloud VPN, secure web gateway, CASB, and DNS filtering. Connectors in your networks, including one built into SonicOS 7.1.2 and later, dial out to CSE's Global Edge Network, and CSE enforces access policy in its cloud with device trust checks at connection time. It's licensed per seat through MySonicWall.
SonicWall's VPN products have had serious, actively exploited vulnerabilities. CVE-2024-40766, an access control flaw in SonicOS SSL VPN, was used in ransomware attacks in 2024. In November 2026 CISA added CVE-2026-19868, an SSL VPN flaw that can bypass SAML-enforced MFA, to its Known Exploited Vulnerabilities catalog. SMA appliances have appeared on the same list several times.
At a glance
| Feature | Pangolin | SonicWall SSL VPN / SMA | SonicWall Cloud Secure Edge |
|---|---|---|---|
| Inbound exposure | None on your networks; sites only dial out | Listens for connections from the internet on the firewall or appliance | Connectors dial out to SonicWall's cloud edge |
| Access model | Users and roles per resource; deny by default | Groups and address objects; users get a tunnel into the network | Per-service policy with device trust checks |
| Browser access | Web apps on your domains; SSH, RDP, VNC in the browser | SMA 1000 portal only; not part of SonicOS SSL VPN | Not a focus; ZTNA is client and connector based |
| Data path | Client to site directly when possible; relay otherwise | Through the firewall or appliance | Through SonicWall's cloud edge |
| Self-hosting | Full stack self-hostable, or cloud with your own remote nodes | On-prem firewall or appliance | Cloud service, with a self-hosted private edge option |
| MSP use | Multiple organizations per account | Managed per firewall or appliance | Billed through the MySonicWall MSP platform |
| Open source | AGPLv3 or commercial license | Proprietary | Proprietary |
| Firewall and IPS | Not a firewall; runs alongside one | Full NGFW with IPS, content filtering, and more (SonicOS) | Cloud SWG, CASB, and DNS filtering; no on-prem firewall |
Detailed comparison
Where access terminates
SonicOS SSL VPN and SMA appliances accept connections from the internet, so the firewall or appliance has a service exposed to anyone who can reach its address. That's the source of most of the security incidents above, and it's why patch speed matters so much with these products.
Pangolin doesn't put a listener on your network. Sites dial out to a Pangolin server, which can be Pangolin Cloud, a server you host in a cloud VPC, or a remote node you run. Users connect to that server or directly to a site using NAT hole punching. The SonicWall only needs to allow outbound traffic from the site.
Cloud Secure Edge takes the same outbound-connector approach, and SonicWall itself describes it as a replacement for SSL VPN rather than a hardened version of it. The difference with Pangolin is who runs the edge: CSE enforces policy in SonicWall's cloud, while Pangolin can run entirely on your infrastructure or in Pangolin Cloud.
Access model
SSL VPN on SonicOS grants network access by group, with address objects deciding what each group can reach. Users get a tunnel into the network, and as exceptions accumulate, access tends to widen.
CSE moves to per-service access with device trust, which is a better model and closer to Pangolin's.
Pangolin defines each resource explicitly, such as a host, a subnet, or a web app, and grants users and roles access to it. Nothing is reachable until you do. Private resources can be limited to specific ports. Roles can map from your identity provider's groups automatically.
Browser access
SonicOS SSL VPN on the firewall is client-only. SonicWall's clientless portal comes with the SMA 1000 appliances, which are a separate product to buy and patch.
Pangolin's public resources give each web app its own URL on your domain with an automatic certificate, served from Pangolin Cloud or from servers you run. Users sign in with SSO, a PIN, a passcode, an email code, or a shareable link, and rules on path, IP, country, and ASN control who gets through. SSH, RDP, and VNC also run in the browser after the same login, which is useful for giving an outside vendor access to one server without a VPN account.
For MSPs
Many SonicWall customers are managed by MSPs. Pangolin supports multiple organizations under one account, each with its own sites, resources, users, and identity providers, so one team can manage access for many customers from one dashboard. Labels, blueprints, and the integration API help with templated rollouts. See Pangolin for MSPs.
CSE is also available through SonicWall's MSP platform with per-seat billing, which suits MSPs that standardize on SonicWall across their customer base.
Identity and devices
SonicOS SSL VPN authenticates against local users, LDAP, RADIUS, or SAML, with TOTP or RADIUS-based MFA. CSE adds device trust checks.
Pangolin uses built-in users or any OIDC provider, such as Entra ID, Google Workspace, or Okta, and can revalidate sessions against the provider every few minutes. Its clients report device posture such as disk encryption, firewall state, and antivirus, and Pangolin can require admin approval for each new device per role. Pangolin Cloud and Enterprise Edition log authentication events, admin actions, requests, and network sessions, and can stream them to a SIEM.
Running both
Pangolin isn't a firewall. It doesn't do IPS, gateway antivirus, content filtering, or perimeter policy. A common setup keeps the SonicWall as the firewall, turns off SSL VPN on the WAN, and runs Pangolin sites behind it for remote access. Sites run as a binary or container on Linux, Windows, or macOS.
Which one fits
SonicWall fits when you want firewall and remote access from one vendor, and Cloud Secure Edge fits SonicWall shops that want cloud ZTNA and secure web gateway billed alongside their existing licenses.
Pangolin fits when you want remote access that never exposes a VPN listener on your network, works the same behind any firewall, includes browser access to web apps, SSH, RDP, and VNC, and can be self-hosted or run in the cloud. It's open source and can manage many customer organizations from one account.
FAQ
Can I use Pangolin with my SonicWall firewall?
Yes. Run a Pangolin site on a machine behind the SonicWall. It only needs outbound internet access, so you can disable SSL VPN on the WAN interface.
Is SMA 100 still supported?
No. SonicWall lists the SMA 100 series as end of sale and end of support, and offers a trade-in to Cloud Secure Edge.
Is Pangolin a replacement for NetExtender?
For remote user access, yes. The Pangolin client gives users access to private hosts and subnets on Windows, macOS, Linux, iOS, and Android, and the reverse proxy covers browser access.
Related comparisons
Try Pangolin
Get started with Pangolin. You can self-host the server or sign up for the cloud and try it with no commitment.
Get in touch
If you want more detail on how Pangolin can fit your setup, reach out.
About Pangolin
Pangolin is the open-source access platform that lets IT and security teams connect their workforce, AI agents, and infrastructure without the friction of legacy VPNs and stitched-together security tools. By unifying a zero-trust VPN, zero-trust reverse proxy, privileged access management, and an identity-aware AI gateway under one policy model, Pangolin helps organizations shrink their attack surface, contain stolen credentials, and pass audits with less work. Teams can roll it out one service at a time, self-hosted or on Pangolin Cloud, and verify exactly how their access is secured because every component is open source.
