Independent reference. Not affiliated with any zero trust vendor. Updated Q1 2026.
ZeroTrustCost
SSE economics

SSE bundle cost: ZTNA plus SWG plus CASB plus FWaaS pricing

Security Service Edge bundles ZTNA, secure web gateway, cloud access security broker and firewall-as-a-service into one platform. This page compares SSE bundle pricing against the sum of unbundled point products, explains when SSE pays back versus over-buys, and frames the consolidation decision for mid-market and enterprise.

What it is

SSE versus SASE versus standalone components

Security Service Edge is the Gartner-defined category that bundles four cloud-delivered security capabilities: zero trust network access (ZTNA) for private application access, secure web gateway (SWG) for outbound traffic policy and malware scanning, cloud access security broker (CASB) for SaaS visibility and DLP, and firewall-as-a-service (FWaaS) for cloud-delivered firewalling. SSE is the security half of SASE; SASE adds SD-WAN to the same bundle. SSE emerged as a category in 2021 as Gartner recognised that organisations needed the security capabilities of SASE without necessarily replacing their existing WAN.

The credible enterprise SSE platforms per the latest Gartner Magic Quadrant for SSE and Forrester Wave for SSE are Zscaler, Netskope, Palo Alto Prisma Access, Cisco (combining Umbrella, Duo and Secure Access), Cloudflare One, and Microsoft (combining Entra Internet Access, Entra Private Access and Defender for Cloud Apps). The mid-market SSE-equivalent platforms include Skyhigh Security, iboss, Forcepoint and Versa. The category is still consolidating; some 2023 leaders have lost momentum (industry analysts have noted this in their reports) and some 2025 challengers have gained ground, particularly Microsoft as it has extended Entra Internet Access and Entra Private Access into a more credible SSE story.

SSE differs from buying the four components as standalone point products in three ways. First, integration: a single SSE platform presents one policy plane, one log stream, one identity integration, and one connector deployment, where four point products present four of each. Second, traffic plane: a single SSE platform inspects each user's traffic once and applies all four capabilities, where point products would each create their own traffic detour. Third, commercial: one vendor, one contract, one term, one support relationship, instead of four. The integration and traffic-plane benefits are real; the commercial benefit is often less material once procurement teams negotiate the four point products well.

Bundle pricing

Standalone versus SSE-bundled cost per component

ComponentStandalone per user / monthIn SSE bundleNotes
ZTNA$5 - $20 / user / monthIncludedAlways the core SSE component. Sometimes the only one actually used.
Secure Web Gateway (SWG)$3 - $8 / user / monthIncludedOutbound traffic policy, URL filtering, malware scanning.
Cloud Access Security Broker (CASB)$4 - $12 / user / monthIncludedSaaS app visibility and DLP for sanctioned and unsanctioned cloud apps.
Firewall-as-a-Service (FWaaS)$3 - $10 / user / monthIncludedCloud-delivered firewall, often replaces or augments branch-office firewall appliances.
DNS filtering$1 - $3 / user / monthIncluded or add-onSometimes bundled, sometimes positioned as a separate add-on.
Browser isolation$3 - $8 / user / monthOften add-onPremium SSE tier. Renders risky web content in remote container.
Data Loss Prevention (DLP)$5 - $15 / user / monthOften add-onNetwork DLP integrated into the SSE traffic plane. Often a separate licence tier.

Summing the four core SSE components at mid-market standalone pricing: $15 to $50 per user per month. SSE bundle pricing for the same four components is typically $15 to $25 per user per month, which is the 20 to 35 percent saving Gartner and the vendors quote. The saving is real for organisations that genuinely use all four components. For organisations that use only one or two, the bundle is over-buy and standalone point products are cheaper.

Decision framework

When SSE pays back, when it over-buys

ScenarioVerdictDetail
You need all four (ZTNA, SWG, CASB, FWaaS) and have none in placeSSE bundle pays backSaves 20-35% vs buying four point products separately.
You need only ZTNA (VPN replacement)Focused ZTNA-only is cheaperSSE marginal cost is 2-4x ZTNA-only. SWG/CASB/FWaaS are feature-waste.
You have working SWG and CASB; need ZTNA + FWaaSHybrid: keep SWG/CASB, add point ZTNA + cloud firewallOften cheaper than full SSE; lower lock-in.
You are also replacing SD-WANSASE (SSE + SD-WAN) consolidates the decisionSame SSE economics plus SD-WAN consolidation. 30-50% premium over SSE-only.
You have a complex existing security stack and SOC teamFocused platforms, not bundleConsolidation operational cost (re-skilling, migration, alert workflow changes) often exceeds licensing saving.
Lock-in

The lock-in profile of SSE bundles

SSE bundles create platform-level lock-in that grows with policy depth. In year one, switching SSE platforms is a meaningful but manageable migration: connector redeployment, policy re-authoring, SIEM integration changes, user training. By year three, the accumulated policy depth (often thousands of rules across the four components, with hundreds of exceptions and tens of integrations) makes switching genuinely difficult. By year five, SSE switching cost for a mid-market organisation can exceed first-year contract value of the new SSE platform, which is the lock-in trap vendors price into long-term commitments.

Three tactics reduce lock-in risk. First, negotiate term aggressively in the first deal: prefer one-year or two-year terms to five-year terms, accepting a higher per-user price in exchange for portability if the platform disappoints. Second, demand data portability in the contract: policy export in machine-readable format (CSV at minimum, ideally a vendor-neutral policy language), log export to your SIEM in real time, and configuration backup. Third, keep identity outside the SSE bundle: if your identity provider is also your SSE provider (some vendors offer this), switching SSE is much harder because identity is the deepest integration point in the stack. Keeping identity and SSE on separate vendors makes SSE meaningfully more portable.

For risk-averse organisations the right architecture is identity (separate vendor) plus ZTNA (separate vendor or SSE) plus everything else (SSE or focused point products as appropriate). For lock-in-tolerant organisations the right architecture is single-vendor consolidation across identity, SSE and increasingly endpoint, which simplifies operations at the cost of switching flexibility. The choice depends on organisational maturity and procurement strategy rather than on pure economics.

Cross-links

Related cost references

Frequently asked

SSE bundle cost questions

What is SSE (Security Service Edge)?
SSE is the Gartner-defined category that bundles ZTNA, secure web gateway, cloud access security broker, and firewall-as-a-service into a single cloud-delivered platform. It is the security half of SASE (Secure Access Service Edge); SASE adds SD-WAN to the same bundle. SSE emerged in 2021 as a recognition that organisations needed the security capabilities of SASE without necessarily replacing their existing WAN. Gartner publishes an annual Magic Quadrant for SSE; Forrester publishes a Wave for SSE; the dominant platforms across both are Zscaler, Netskope, Palo Alto Prisma Access, Cisco (Umbrella plus Duo plus Secure Access), Cloudflare One, and Microsoft Entra Internet Access / Private Access.
How much does an SSE bundle cost per user?
SSE bundle pricing typically lands at fifteen to twenty-five dollars per user per month for mid-market deployments. Pricing varies by which capabilities are included: ZTNA-plus-SWG-only at the lower end (twelve to eighteen dollars), full SSE with ZTNA plus SWG plus CASB plus FWaaS plus DNS at the upper end (twenty to thirty dollars). Enterprise deals at multi-year term with high user counts run fifteen to twenty dollars per user per month. Add browser isolation, advanced threat protection, and data loss prevention add-ons to the core SSE bundle and pricing rises to thirty to forty-five dollars per user per month.
When does SSE pay back vs over-buy?
SSE pays back when you need all the bundled capabilities and do not already have them. If you would otherwise buy ZTNA, SWG, CASB and FWaaS as four separate products, the SSE bundle is typically 20 to 35 percent cheaper than the sum of the four point products at equivalent quality. SSE over-buys when you only need ZTNA and already have working SWG, CASB and FWaaS. The marginal cost of SSE over a focused ZTNA-only platform is roughly two to four times. The audit question is simple: which of the four bundled capabilities do you genuinely need that you do not already have?
What is the difference between SSE and SASE?
SASE bundles SSE plus SD-WAN. SSE is the security half; SASE adds the networking half. If you have working SD-WAN you do not need SASE; SSE is the right choice. If you are also replacing SD-WAN, SASE consolidates the security and networking decisions into one vendor and one contract. The cost difference: SASE is typically 30 to 50 percent more expensive per user per month than SSE because of the SD-WAN component, but it eliminates the cost of buying SD-WAN separately. For most mid-market organisations not actively replacing SD-WAN, SSE is the right scope.
Which SSE platforms are credible in 2026?
Per the Gartner Magic Quadrant for SSE 2025 and the Forrester Wave for SSE Q1 2024, the credible enterprise-grade SSE platforms are Zscaler, Netskope, Palo Alto Prisma Access, Cisco (combination of Umbrella, Duo, and Secure Access), Cloudflare One, and Microsoft (combination of Entra Internet Access, Entra Private Access, and Defender for Cloud Apps). For mid-market, lighter-touch SSE-equivalent stacks exist from Skyhigh Security, iboss, Forcepoint, and Versa. The category is still consolidating; some 2023 leaders have lost momentum and some 2025 challengers have gained ground.
How do we avoid SSE bundle lock-in?
Three tactics work. First, negotiate term aggressively: prefer one-year or two-year terms to five-year terms in the first deal, accepting a higher per-user price in exchange for portability if the platform disappoints. Second, demand data portability in the contract: policy export in machine-readable format, log export to your SIEM, configuration backup. Third, keep identity outside the SSE bundle. If your identity provider is also your SSE provider (some vendors offer this), switching SSE is harder because identity is the deepest integration point. Keeping identity and SSE on separate vendors makes SSE more portable.
What is the most common SSE over-spend?
Buying full SSE when you only need ZTNA. Roughly half the SSE deals we see in mid-market organisations are bought for a ZTNA-replacement use case (VPN replacement), and the SWG, CASB and FWaaS components sit unused or used at 10 to 20 percent capacity. A focused ZTNA-only platform at five to ten dollars per user per month delivers the ZTNA capability at a third the SSE bundle cost. The fix: audit the actual usage of bundled capabilities in any existing SSE deal at contract renewal, and right-size to ZTNA-only if SWG/CASB/FWaaS are not in real use.