Security / ZTNA / Delivery Mode

ZTNA cloud service provider or self-hosted — when should you buy cloud SSP?

Ordering “a ZTNA cloud service provider” without locking delivery mode is how you pay for seats your thick clients or residency clause cannot use. Choose cloud SSP or self-hosted first — then vendors.

Quick Take

Quick Take: A tender BOM that says "servers, switches, storage" buys you three different kits and a price comparison that means nothing. Write 9 fields on every line — function, performance floor, quantity with units, interfaces and optics, licence term, power and cooling, warranty, delivery window, acceptance test — add a deviation table, and ask for one alternative column. Then bids differ in price and delivery, not in what is being bought.

You are not writing paperwork. You are deciding what the evaluation committee will be able to compare. Spend two hours on the BOM now, or spend a tender round re-running it later. Send us the draft clauses and we will mark the lines that will come back incomparable, before the tender opens.

What goes wrong when the RFQ only says “ZTNA cloud service provider”?

Quick Answer: You award cloud seats that residency or thick apps cannot use — or you overbuy appliances when OpEx PoP would have shipped faster.

Typical scene: procurement searches ztna cloud service provider, picks the cheapest per-user cloud quote, then security finds OT HMIs and a data-residency clause that block cloud brokers. Rework starts after the award. Or the opposite: the estate is SaaS-heavy and global, yet the BOM buys appliance HA pairs “to own Zero Trust,” and remote users wait months for PoP-equivalent reach. Typical scenario, not a named customer.

The broad ZTNA buying guide 2026 covers ZTNA vs VPN, Prisma vs ZPA shortlists, and license meters. This page answers only the delivery-mode gate: buy cloud SSP ZTNA, or self-host appliance/VM.

Cloud SSP vs self-hosted — decision table (2026-10-23)

Quick Answer: Mode first; brand second. Soft prices pending confirmation.

DimensionCloud SSP / SASE PoP ZTNASelf-hosted appliance / VM
Control planeVendor cloud + tenant adminOn-prem / private cloud controller
User reachGlobal PoPs; fast remote onboardingLimited by your sites and connectors
CapEx vs OpExMostly seat / subscription OpExAppliance/VM CapEx + subscription
Best fitDistributed users, SaaS + HTTP private appsResidency, air-gap, OT/thick adjacency
RFQ riskSeats unused if apps not brokerableHardware idle if users are cloud-first
Example pathsZPA, Prisma Access, FortiSASE (cloud)FortiGate ZTNA / private brokers / VM controllers

Vendor names are delivery examples, not an award shortlist. Seat prices, PoP SLAs and appliance SKUs = industry estimate / pending confirmation on a dated quote. NIST SP 800-207 frames Zero Trust as policy decision/enforcement points — it does not mandate cloud or on-prem.

What “buy cloud SSP ZTNA” means for procurement

Quick Answer: You are buying brokered app access from a provider’s cloud — not a VPN concentrator with a new label.

Definition: buying ZTNA as a cloud service provider means the identity- and posture-aware broker for private apps runs in the vendor’s cloud PoP fabric; your sites run connectors (or equivalent) toward apps, and users never land on a flat network. Self-hosted means the policy decision/enforcement plane you operate sits on appliance or VM under your boundary.

Like choosing airline tickets versus buying your own plane: same destination (named apps), different who owns the control tower. If the route has a sovereignty gate, you need the plane you operate — not just cheaper seats.

Lock cloud SSP vs self-hosted on the RFQ, 6 steps

Quick Answer: Apps → constraints → mode → equal meters → dual-path columns → strip VPN shelfware.

  1. Step 1 — List apps and protocols — HTTP/SaaS vs thick client, RDP, SSH, OT — each row gets a brokerability flag.
  2. Step 2 — Mark residency and air-gap — If control plane or traffic cannot leave a boundary, cloud SSP is unfit for that segment.
  3. Step 3 — Choose delivery mode before brand — Cloud SSP seats vs self-hosted appliance/VM — print the mode on every RFQ line.
  4. Step 4 — Equalize user and posture meters — Same active users, MFA, device posture, and connector sites across bidders.
  5. Step 5 — Split dual-path quotes — Column A cloud SSP; column B self-hosted. Do not merge into one “ZTNA” lump sum.
  6. Step 6 — Strip VPN shelfware — Drop full-tunnel VPN seats for populations that move to ZTNA; keep only scoped fallback.

Small first step: open your app inventory. If three columns — protocol, residency, air-gap — are blank, fill them before comparing any cloud SSP price.

Who must buy cloud SSP — who must self-host?

Quick Answer: Global SaaS-heavy: cloud. Residency/OT/air-gap: self-hosted (or hybrid by segment).

Global knowledge workers, HTTP private apps, IdP ready. Cloud SSP ZTNA wins on time-to-access and OpEx. Put PoP regions and connector sites on the first RFQ.

Plant OT, thick clients, or sovereignty clauses. Self-hosted appliance/VM (or a hybrid: cloud for office users, local brokers for OT). Do not force one cloud seat SKU across both populations.

  • Fit: dual-path RFQs that must show cloud SSP and self-hosted columns; migrations off full-tunnel VPN; SASE packages where ZTNA is the private-app line.
  • Not fit: consumer VPN; single laptop “Zero Trust” retail; buyers with no app list or IdP.

Delivery-mode traps on ZTNA RFQs

Quick Answer: Cloud seats for non-brokerable apps; appliances for cloud-only users; double VPN+ZTNA meters.

TrapWhat happensFix
Award cloud SSP before app auditSeats idle; OT still on VPNBrokerability flag per app
Self-host “to own” with no residency needSlow remote rolloutPrefer cloud SSP for that segment
One lump “ZTNA” priceModes not comparableDual-path columns
Keep full VPN + full ZTNA seatsShelfware CapEx/OpExScoped VPN fallback only
Ignore IdP/MFA readinessZTNA becomes slow VPNBudget IdP before seats
Skip connector site countSurprise appliance/VM linesList sites on RFQ day one

Frequently Asked Questions

Quick Answer: A tender BOM is the issuer's pricing baseline: same lines, same units, same licence years. Bidders answer with a deviation table, and the committee compares lines, not totals.

A vendor that delivers Zero Trust Network Access from cloud PoPs (often inside SASE/SSE): identity- and posture-brokered access to named apps without placing users on a flat VPN segment. Examples of cloud-delivered paths include Zscaler ZPA, Palo Alto Prisma Access, and Fortinet FortiSASE — exact SKUs pending your dated quote.

When you need fast global user reach, OpEx seats, and the control plane can live in the vendor cloud — and you have no hard residency, air-gap, or protocol constraint that blocks cloud brokers. If those constraints exist, size self-hosted appliance/VM controllers plus connectors.

When policy requires on-prem control plane or data-plane adjacency, OT/thick clients that need local brokers, air-gapped sites, or sovereignty clauses that forbid cloud PoP termination. Self-hosted still uses connectors; it is not “VPN with a new label.”

Not always. ZTNA is the private-app access piece. SASE/SSE bundles often add SWG, CASB, and FWaaS. Buy ZTNA meters first; only add SWG/CASB seats if the RFQ lists those use cases — see the broad ZTNA buying guide for license traps.

Equalize: active users, named apps, posture checks, connector count/sites, PoP regions, IdP/MFA, fallback VPN scope, and whether control plane is cloud or self-hosted. Strip overlapping full-tunnel VPN seats for the same population.

Yes. Send app list and constraints. We mark which lines fit cloud SSP and which need appliance/VM within 1 business day. Prices and lead times pending confirmation.

Key Takeaway

Key Takeaway: Buy ZTNA as a cloud service provider when PoP reach and OpEx fit and apps are brokerable; self-host appliance/VM when residency, OT, or air-gap lock the control plane. Freeze mode on the RFQ. BENQUAN maps cloud SSP vs self-hosted in 1 business day; prices pending confirmation.

Have an app list and two ZTNA quotes?

Send user count, app inventory (HTTP vs thick), residency and air-gap constraints. BENQUAN returns a cloud-SSP vs self-hosted shortlist within 1 business day. Seat prices pending confirmation.

Free Compatibility & Delivery Risk Assessment

Or call +852-21349834 · info@benquan.hk

Contents