
What Is SASE? Secure Access Service Edge Explained Simply
What is SASE? SASE (pronounced “sassy”) stands for Secure Access Service Edge. It is a cloud-based way of delivering network connectivity and network security together, as a single service, instead of running separate boxes in offices and data centres.
In short: instead of backhauling all traffic to a central office so it can pass through a firewall, SASE checks and protects users wherever they are, close to where they work, in the cloud. This guide explains what SASE is, what it includes, and when it makes sense.
What Is SASE in Plain English?
Traditionally, a company network looked like a castle: everyone worked in offices, traffic went through the office firewall, and the VPN let remote workers tunnel back inside. That model breaks when staff work from home, apps live in the cloud, and branches are everywhere.
SASE moves the castle walls to the cloud. A user — in an office, at home, or in a café — connects to the nearest SASE point of presence, where their identity is checked and security policies are applied before traffic goes on to the internet or a company app. The network and the security travel with the user, not the office.
The term was coined by Gartner in 2019. It is an architecture, not a single product: vendors package the pieces differently, but the idea is the same — networking and security delivered from the cloud, managed from one console.
The Five Core Parts of SASE
1. SD-WAN (software-defined wide area networking)
SD-WAN chooses the best path for traffic — broadband, 4G/5G or MPLS — and keeps performance up even if one link fails. It replaces rigid, expensive private lines for most branches.
2. Secure Web Gateway (SWG)
Filters web traffic, blocks malicious sites and enforces acceptable-use rules for internet browsing.
3. Cloud Access Security Broker (CASB)
Controls access to cloud apps (like Microsoft 365 or Salesforce), watching for risky sharing, downloads and shadow IT.
4. Firewall as a Service (FWaaS)
A cloud firewall that inspects traffic without a physical appliance in every office. See how the on-premises version works in our guide to what a network firewall is.
5. Zero Trust Network Access (ZTNA)
Replaces the traditional VPN: instead of giving a user access to the whole network, ZTNA grants access to one specific app, after checking identity and device health. Read our explainer on zero-trust network access.
SASE vs Traditional Network Security
| Factor | Traditional model | SASE model |
|---|---|---|
| Where security is applied | At the office or data centre | In the cloud, near the user |
| Remote workers | VPN back to the office, often slow | Direct, secured connection to the cloud edge |
| Hardware | Appliances in every site | Minimal; mostly cloud-delivered |
| Management | Many consoles, many vendors | One policy console (in theory) |
| Scaling to a new branch | Order, ship and configure hardware | Connect to the nearest cloud point of presence |
Practical Example
A company with 12 small branches and 200 remote workers used a central firewall and VPN. Remote staff complained that video calls and cloud apps were slow, because all traffic travelled to headquarters and back. Branches each ran their own firewall, patched on different schedules.
Moving to SASE, each branch connected over ordinary broadband to the provider’s cloud edge, where firewall, web filtering and zero-trust access were applied. Remote workers connected to the same edge instead of the VPN. The company retired most branch hardware, cut VPN complaints, and could apply one security policy everywhere — though it now depended on one provider and needed careful rollout to avoid breaking legacy apps that assumed a fixed office IP address.
Benefits and Drawbacks
Benefits: better performance for remote and branch users, fewer appliances to maintain, consistent policy everywhere, and easier scaling.
Drawbacks: dependence on a single vendor’s cloud, migration effort for legacy applications, and the risk of buying a “SASE” label that is really just a VPN or a firewall rebranded. True SASE converges networking and security; a single feature does not make a SASE product.
For the underlying secure-tunnel technology that SASE often replaces or complements, see our guide to what IPsec is.
Is SASE Right for Your Organisation?
- Yes, likely: many branches, many remote workers, heavy cloud-app use, or a hardware refresh coming up.
- Maybe not yet: a single office, mostly on-premises apps, or strict data-residency rules that limit cloud processing.
- Start small: pilot with one branch or one user group, measure performance and support tickets, then expand.
Frequently Asked Questions
What is SASE?
SASE stands for Secure Access Service Edge: a cloud service that combines network connectivity (like SD-WAN) with network security (firewall, web gateway, CASB and zero-trust access) in one platform.
Is SASE the same as a VPN?
No. A VPN tunnels a user into the whole corporate network; SASE gives verified users access to specific apps and applies security in the cloud, without backhauling all traffic to an office.
Does SASE replace a firewall?
It replaces the physical firewall appliance in most sites with firewall-as-a-service in the cloud, but the firewall function itself remains — it just runs elsewhere.
Is SASE only for large companies?
Not anymore. Smaller companies can buy SASE as a managed service and avoid running branch hardware, though they should weigh the subscription cost against their current setup.
What is the difference between SASE and SSE?
SSE (Security Service Edge) is the security-only half of SASE. SASE adds the networking side (SD-WAN); SSE assumes you already have networking sorted and just need cloud security.


