Alright, let's cut through the marketing. SonicWall now has "Cloud Edge Secure Access." From what I can parse, it's their attempt at a SASE/SSE play, bundling ZTNA, CASB, and SWG into a cloud service. My immediate reaction is: is this a genuinely new platform, or just a repackaging of existing pieces with a new management console and another line on the invoice?
The pattern here is familiar. A vendor sees a market buzzword (SASE), slaps a new brand on a combination of old and acquired tech, and launches it as a separate SKU. This creates the classic "suite within a suite" problem. If you're already a SonicWall firewall customer, does this integrate seamlessly with your on-prem NSa, or is it a separate silo? More importantly, what's the licensing trap? Do you get a "unified" discount, or are you now paying for gateway licenses *and* user-based cloud licenses, effectively double-dipping?
I'm particularly skeptical of the CASB and ZTNA claims. SonicWall's strength has traditionally been in network-layer inspection. Building effective, API-driven cloud app security and context-aware identity policies is a different game. I'd need to see concrete examples of its discovery depth for unsanctioned SaaS, and how the ZTNA component handles non-enterprise devices without requiring a heavy agent. Otherwise, it's just a VPN replacement with a fancy name.
So, has anyone actually deployed this yet? I'm less interested in the datasheet and more in the operational reality. What does the onboarding actually look like? Are the policies truly unified, or do you still juggle two consoles? And the inevitable question: when the bill comes, does the ROI math work, or are you just paying for the same security outcomes with more complexity and a new vendor lock-in?
— skeptical but fair
Exactly my thoughts. That "suite within a suite" model is a killer for operational workflows. I tested an early build. The ZTNA connector for on-prem apps deploys as a virtual appliance on your network, separate from your NSa management. So you're managing policies in two places.
Their CASB felt lightweight, mostly API-based O365. Missed a ton of unsanctioned apps in my test tenant compared to a dedicated player. This feels like a check-box SKU to stop customers from leaving, not a platform built from the ground up.
The real test is the billing. Bet you're right about the double-dip.
Automate everything.
Spot on about the double-dip. You're now looking at a per-user/per-month fee for the cloud service, on top of your existing per-appliance support subs. No meaningful bundle discount if you're an existing customer.
The real trap is the "light" CASB. If it can't discover unsanctioned apps effectively, you'll still need a real CASB. So you're paying for a check-box feature and a real one. Classic vendor lock-in strategy - give you just enough to think you're covered.
always ask for a multi-year discount
You nailed the network-layer point. Their CASB is an API wrapper, not deep discovery. I saw the same thing in a trial - it only tagged apps I'd already authorized. Missed a whole shadow IT channel our dedicated tool caught.
And you're right to ask about the double-dip. From what I saw in the portal, it's separate licenses stacked on top. No unified dashboard for the NSa policies and these new cloud policies either. Makes you wonder why they didn't just bake this into the existing management.
Feels like a rushed SASE box-ticker, not a real platform.
Trial first, ask later.
You're spot on about the network-layer strength. It's the classic mismatch - vendors good at packets suddenly think they can do identity. The "context-aware" bit you mentioned is usually just a tag pulled from Azure AD, not real session analysis.
I'd add that their ZTNA is likely just their old SSL-VPN with a new paint job. That means you're paying a cloud subscription fee for what was a licensed feature on your existing box. The double-dip is almost guaranteed.
Cloud costs are not destiny.