SASE principal elements are: • Convergence of
WAN and network security functions. • A
cloud-native architecture delivering converged WAN and security as a service that offers the
scalability, elasticity, adaptability and self-healing typical of all cloud services. • Globally distributed fabric of PoPs delivering a full range of WAN and security capabilities with low latency, wherever business offices, cloud applications and mobile users are located. To deliver low latency at any location, SASE PoPs have to be more numerous and extensive than those offered by typical public cloud providers and SASE providers must have extensive
peering relationships. •
Identity-driven services. An identity can be attached to anything from a person or branch office to a device, application, service,
IoT device or edge computing location at the source of connection. Identity is the most significant context affecting SASE security policy. However, location, time of day, risk/trust posture of the connecting device and application and data sensitivity will provide other real-time context determining the security services and policies applied to and throughout each WAN session. • Support for all edges equally, including physical locations, cloud data centers, users’ mobile devices and edge computing, with placement of all capabilities at the local PoP rather than the edge location.
Edge connections to the local PoP may vary from an SD-WAN for a branch office to a VPN client or clientless
Web access for a mobile user, to multiple tunnels from the cloud or direct cloud connections inside a global data center. Depending on the implementation, SASE may reduce the number of apps and agents required for a device to a single app, while providing a consistent experience to the
user regardless of where they are or what they are accessing.
Consistent security Consistent security via a single cloud service for all WAN security functions and WAN connections. Security is based on the same set of policies, with the same security functions delivered by the same cloud service to any access
session, regardless of application, user or device location and destination (cloud, data center application). Once the SASE provider adapts to a new threat, the adaptation can be available to all the edges. == Criticism ==