What is SASE? | Secure access service edge

SASE includes four core security components:

1. Secure web gateways (SWG): An SWG prevents cyber threats and data breaches by filtering unwanted content from web traffic, blocking unauthorized user behavior, and enforcing company security policies. SWGs can be deployed anywhere, making them ideal for securing remote workforces.
2. Cloud access security broker (CASB): A CASB performs several security functions for cloud-hosted services, including revealing shadow IT (unauthorized corporate systems), securing confidential data through access control and data loss prevention (DLP), and ensuring compliance with data privacy regulations.
3. Zero Trust Network Access (ZTNA): ZTNA platforms lock down internal resources from public view and help defend against potential data breaches by requiring real-time verification of every user and device to every protected application.
4. Firewall-as-a-service (FWaaS): FWaaS refers to firewalls delivered from the cloud as a service. FWaaS protects cloud-based platforms, infrastructure, and applications from cyber attacks. Unlike traditional firewalls, FWaaS is not a physical appliance, but a set of security capabilities that includes URL filtering, intrusion prevention, and uniform policy management across all network traffic.

Depending on the vendor and the needs of the enterprise, these core components may be bundled with additional security services, including web application and API protection (WAAP), remote browser isolation, or Wi-Fi hotspot protection.

What are the advantages of a SASE framework?

SASE offers several benefits compared to a traditional, data center-based network security model:

• Identity-based Zero Trust network access. SASE leans heavily on a Zero Trust security model, which does not grant a user access to applications and data until their identity has been verified — even if they are already inside the perimeter of a private network. When establishing access policies, a SASE approach takes more than an entity's identity into account; it also considers factors like user location, time of day, enterprise security standards, compliance policies, and an ongoing evaluation of risk/trust.
• Blocking attacks against network infrastructure. The firewall and CASB components of SASE help prevent external attacks (like DDoS attacks and vulnerability exploits) from getting in and compromising internal resources. Both on-premise and cloud-based networks can be protected by a SASE approach.
• Preventing malicious activity. By filtering URLs, DNS queries, and other outgoing and incoming network traffic, SASE helps prevent malware-based attacks, data exfiltration, and other threats to corporate data.
• Streamlined implementation and management. SASE merges single-point security solutions into one cloud-based service, freeing enterprises to interact with fewer vendors and to spend less time, money, and internal resources configuring physical infrastructure.
• Simplified policy management. Instead of juggling multiple policies for separate solutions, SASE allows organizations to set, adjust, and enforce access policies across all locations, users, devices, and applications from a single portal.
• Latency-optimized routing. SASE helps cut down on latency by routing network traffic across a global edge network in which traffic is processed as close to the user as possible. Routing optimizations can help determine the fastest network path based on network congestion and other factors.

How does SASE compare to traditional networking?

In a traditional network model, data and applications live in a core data center. In order to access those resources, users, branch offices, and applications connect to the data center from within a localized private network or a secondary network that typically connects to the primary one through a secure leased line or VPN.

This model has proved to be ill-equipped to handle the complexities introduced by cloud-based services like software-as-a-service (SaaS) and the rise of distributed workforces. It is no longer practical to reroute all traffic through a centralized data center if applications and data are hosted in the cloud.

By contrast, SASE places network controls on the cloud edge — not the corporate data center. Instead of layering cloud services that require separate configuration and management, SASE streamlines network and security services to create a secure network edge. Implementing identity-based, Zero Trust access policies on the edge network allows enterprises to expand their network perimeter to any remote user, branch office, device, or application.

How organizations can implement SASE

Many organizations take a piecemeal approach to SASE implementation. In fact, some may have already adopted certain SASE elements without knowing it. Key steps organizations can take towards fully adopting a SASE model include:

1. Securing remote workforces
2. Placing branch offices behind a cloud perimeter
3. Moving DDoS protection to the edge
4. Migrating self-hosted applications to the cloud
5. Replacing security appliances with unified, cloud-native policy enforcement

These steps are broken down further in the white paper "Getting started with SASE," available for download here.

How Cloudflare enables SASE

Cloudflare is uniquely architected to deliver a platform of integrated network and security services across data centers in over 300 globally distributed cities, eliminating the need for enterprises to purchase and manage a complex collection of point solutions.

Cloudflare One is a SASE platform that securely connects remote users, offices, and data centers to each other and the resources that they need. To get started with Cloudflare One, see the Cloudflare One product page. Or, learn more about ZTNA, a crucial technology behind SASE.