The Versa SASE Portal is a cloud-based, single pane-of-glass console for configuring and managing a Versa SASE deployment. It applies consistent security, network, and user policy across Versa Secure Access (VSA) and Secure Web Gateway (SWG) services, connecting on-premises devices and cloud services under one policy set.
Key takeaways
- Cloud-based, single pane-of-glass console for SASE policy configuration.
- Delivers Versa Secure Access (VSA) and Secure Web Gateway (SWG) services.
- Configures real-time protection, secure client access, and TLS decryption.
- Applies consistent policy from on-premises devices to cloud services.
- SASE clients register here once before connecting to SASE gateways.
On this page: Why it mattersHow it worksVersa SASE Portal componentsVersa SASE Portal & VersaONEFAQ
Why is the Versa SASE Portal important?
Client-to-cloud SASE deployments split policy across many surfaces – internet access rules, private application access, TLS handling, client posture – that traditionally required separate consoles. The Versa SASE Portal collapses that into one cloud-based interface: administrators define real-time protection rules, secure client access profiles, and TLS decryption policy in a single place, then enforce them consistently across VSA and SWG.
That consistency matters most at the edges, where remote users and branch devices reach the same enterprise resources through different paths. A user connecting over VSA and a browser session filtered by SWG both draw on the same certificates and address objects configured once in the portal, so policy does not drift between access methods.
The portal is also the SASE client’s front door: a client registers there once, receives its gateway policy configuration, and only then negotiates a secure tunnel to a gateway – a single control point for bringing new users into a deployment.
What is the Versa SASE Portal?
The Versa SASE Portal is a cloud-based, single pane-of-glass interface for configuring and managing a Versa SASE deployment. It delivers two core services: Versa Secure Access (VSA), which connects users to enterprise-hosted applications using Zero Trust principles, and Secure Web Gateway (SWG), which secures internet browsing and access to internet-based applications. Both services run on the same underlying VOS-based SASE gateways, so the portal’s policy applies whether a session is bound for an internal application or the open internet.
Through the portal, administrators configure real-time protection rules, secure client access profiles for VSA client applications on desktops and mobile devices, TLS decryption, and per-user or per-group bandwidth limits. Global settings cover certificates, mobile device manager (MDM) integration for endpoint posture, site-to-site GRE or IPsec tunnels to the enterprise network, user and group authentication, and user-defined objects such as address groups, applications, schedules, and services that rules elsewhere in the portal reference.
Versa SASE Portal components
The portal’s configuration surface groups into a small set of areas. Real-time protection covers internet protection rules for SWG-enabled traffic and private application protection rules for VSA-enabled traffic, both matched by user, group, geolocation, zone, and IP address, with profiles like URL filtering, IPS, and malware protection layered on top. Rule actions are allow, deny, or reject. Secure client access governs how the VSA client behaves on end-user devices, including which gateways it can reach and which authentication method it uses.
TLS decryption and bandwidth limits apply as their own policy areas, available where the corresponding SWG or VSA service is enabled. Settings rounds out the portal: certificates, MDM profiles for device posture, site-to-site tunnels to on-premises networks, authentication profiles, and user-defined objects such as address groups and applications.
Versa SASE Portal & VersaONE
The Versa SASE Portal is the client-to-cloud front end of VersaONE’s SASE services, sitting alongside Versa Director, which orchestrates the underlying VOS estate, and Versa Analytics, which reports on it. VOS devices still onboard through Director’s zero-touch process; the SASE Portal is a parallel path for people rather than boxes – where administrators configure the VSA and SWG policy that governs users and clients, and where those clients register before connecting to a SASE gateway.
Versa Concerto can front the whole experience as a single cloud-native portal, with the SASE Portal’s configuration surfaces reachable from there. Either way, the portal’s policy – certificates, real-time protection rules, and client profiles – governs the same SASE gateways that VOS devices and SASE clients connect to.
Frequently asked questions
What services does the Versa SASE Portal configure?
Two core services: Versa Secure Access (VSA), Zero Trust connectivity to enterprise-hosted applications, and Secure Web Gateway (SWG), secure internet browsing. Around them, the portal configures real-time protection rules, secure client access, TLS decryption, bandwidth limits, and global settings like certificates and tunnels.
How does a SASE client connect through the portal?
A new client registers on the SASE portal once, over a TLS-encrypted connection, and receives its gateway policy configuration. Only after registration does it negotiate a secure tunnel to a SASE gateway, similar to how zero-touch provisioning onboards a VOS device to a Controller.
What is the difference between internet protection and private application protection rules?
Internet protection rules govern SWG-enabled traffic to and from the internet, filtering by application, URL, and user. Private application protection rules govern VSA-enabled traffic to internal applications, restricting which users can reach which private resources, both matched by user, group, and zone.
Can the Versa SASE Portal enforce per-user bandwidth limits?
Yes. Bandwidth limits are user-based traffic control policers applied on gateways, scoped to a user ID or user group, and enforced as per-session limits – one of the global policy areas configured directly in the portal alongside certificates and tunnels.
What authentication methods does the Versa SASE Portal support?
Each enterprise can configure one LDAP profile, one SAML profile, or a Versa Directory users-and-groups profile for authenticating users and clients. These profiles feed the secure client access rules that decide which gateways and methods a VSA client can use.
More on Versa SASE
If you want to learn more, these are sources we trust.
| Versa Networks: products | Versa Networks: secure SD-WAN | Versa Academy |
|---|---|---|
| The vendor’s product pages for the SASE services the portal configures. | How Versa packages secure connectivity across SD-WAN and SASE together. | Training and labs that cover SASE policy configuration hands-on. |
Related terms
If you’re reading about the Versa SASE Portal, these are worth looking at next.
| Versa Secure Access | Secure Web Gateway | Real-Time Protection |
|---|---|---|
| The Zero Trust remote access service the portal configures for client-to-application connectivity. | The internet security service the portal configures for browsing and internet-based applications. | The rule category the portal uses to apply security profiles to internet and private application traffic. |