Zscalerのブログ

Zscalerの最新ブログ情報を受信

Best Practices

How SASE Vendors Design Their Solution - Part 3: Not Everything Belongs in the Cloud (The Self-Hosted Necessity)

JULIAN WEINBERGER, JOE ARRA
November 17, 2026 - 5 読了時間
>How SASE Vendors Design Their Solution - Part 3: Not Everything Belongs in the Cloud (The Self-Hosted Necessity)

The Operational Realities of a Disconnected World

While the future of security is undoubtedly in the cloud, a truly comprehensive SASE architecture must acknowledge a critical operational reality: not every location can be reliably connected to it. For many industries, there are environments where the cloud is simply too far away or entirely inaccessible.

Consider these scenarios:

  • A secure, air-gapped military network where external connections are strictly forbidden for security reasons.
  • A highly isolated factory in a remote region, where local industrial control systems require low-latency communication that cannot tolerate a round trip to the cloud.
  • An office in a country with severe geo-routing restrictions or poor network infrastructure, making cloud performance untenable.

In these situations, a cloud-only SASE solution is a non-starter. A truly enterprise-grade SASE vendor must provide a way to extend its security architecture to these challenging environments. This is the "good" design: a hybrid SASE topology that embraces the necessity of an on-premises presence.

The Good: The Private Service Edge

The solution is a Private Service Edge (also known as an on-premises SASE node). This is a hardware appliance or, more commonly, a virtual machine that runs the exact same software, policies, and inspection engine as the vendor's global security cloud. This private service edge is deployed on-premises, providing a local point of presence for security enforcement.

Crucially, this is not simply a legacy virtual appliance. A well-designed private service edge is an extension of the SASE platform. It is centrally managed from the same cloud console, receives the same policy updates, and provides the same rich logging and telemetry as its cloud-based counterparts.

This architecture provides the best of both worlds:

  • Local Proxy Processing: All traffic is processed locally, ensuring the lowest possible latency for users and devices in that location. This is critical for real-time applications and industrial systems.
  • Consistent Policy Enforcement: The same set of granular DLP, threat prevention, and access control policies are applied on-premises as they are in the cloud, ensuring a consistent security posture across the entire organization.
  • Offline Survivability: If the connection to the central management cloud is lost, the private service edge can continue to operate autonomously, enforcing the last known policy configuration.

The Ugly: Stitched-Together Hybrid Solutions

Alternative SASE solutions often struggle to provide a clean, integrated on-premises offering. Some vendors may propose a disparate virtual appliance that does not run the same software stack as their cloud service. This creates a clunky, disjointed experience where policies must be managed in two different places, and the on-premises capabilities may lag significantly behind the cloud service.

This is the "ugly" approach: a hybrid solution in name only. It creates operational friction, results in an inconsistent security posture, and fails to deliver the unified management that is a core tenet of the SASE framework.

A mature SASE architecture is one that is flexible enough to meet the operational realities of the enterprise. By offering a fully integrated private service edge, a vendor demonstrates a deep understanding of the need for a hybrid topology. It acknowledges that while the brain of the security platform should reside in the cloud, its enforcement capabilities must extend to every edge of the network, no matter how remote or disconnected.

FAQs

A Private Service Edge (or on-premises SASE node) is a virtual machine or hardware appliance deployed locally within an organization's private infrastructure. It runs the exact same software stack, policy engine, and inspection capabilities as the vendor's global security cloud. This allows organizations to enforce consistent security policies locally, ensuring ultra-low latency processing for on-premises users and devices while maintaining unified management from a single cloud console.

Enterprises require a hybrid SASE architecture to support disconnected, isolated, or ultra-low-latency environments where routing traffic to a public cloud gateway is impossible or impractical. Critical use cases include air-gapped military networks, deep-sea oil rigs relying on high-latency satellite connections, remote manufacturing plants running real-time industrial control systems, and offices operating in regions with severe geographical routing restrictions.

A well-designed Private Service Edge features offline survivability. If the local node loses its WAN connection to the central cloud management plane, it continues to operate autonomously at the local network edge. It enforces the last known policy configuration and queues local traffic logs, ensuring uninterrupted security processing and zero downtime for local users until cloud connectivity is restored.

Stitched-together hybrid SASE solutions rely on disparate legacy on-premises appliances that run a different software stack than the vendor's cloud service. This architectural mismatch causes operational friction, inconsistent security enforcement, and disjointed management. Administrators are forced to manage policies in multiple consoles, and the on-premises appliances frequently lack the advanced inspection features, real-time updates, and parity of the cloud-native platform.

A local SASE proxy improves performance by enabling local proxy processing, which eliminates the latency overhead of backhauling traffic to a distant cloud security node. By inspecting and securing data packets directly on-premises, real-time applications and sensitive industrial systems experience the lowest possible transit latency while remaining fully protected by enterprise-grade DLP and threat prevention policies.

form submtited
お読みいただきありがとうございました

このブログは役に立ちましたか?

免責事項:このブログは、Zscalerが情報提供のみを目的として作成したものであり、「現状のまま」提供されています。記載された内容の正確性、完全性、信頼性については一切保証されません。Zscalerは、ブログ内の情報の誤りや欠如、またはその情報に基づいて行われるいかなる行為に関して一切の責任を負いません。また、ブログ内でリンクされているサードパーティーのWebサイトおよびリソースは、利便性のみを目的として提供されており、その内容や運用についても一切の責任を負いません。すべての内容は予告なく変更される場合があります。このブログにアクセスすることで、これらの条件に同意し、情報の確認および使用は自己責任で行うことを理解したものとみなされます。

Zscalerの最新ブログ情報を受信

このフォームを送信することで、Zscalerのプライバシー ポリシーに同意したものとみなされます。