Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Security Service Edge?

SSE delivers web filtering, SaaS control, private application access, and data protection from the cloud, so the same policy applies whether a user is in the office or at home.

Illustration for the cybersecurity term Security Service Edge
Home / Blog / Cybersecurity Terms / What Is Security Service Edge?
17 November 2026

What Is Security Service Edge?

What Is Security Service Edge?

Security Service Edge describes the cloud-delivered security half of SASE, separated out as its own category by Gartner in 2021 because organisations were adopting it independently of any change to their wide area network. The idea is to move the controls that used to live in appliances at the office perimeter into a distributed cloud service, so that the policy applies to a user in a branch, at home, or in a hotel without any difference in enforcement.

The Components

Secure web gateway. Outbound inspection, URL categorisation, malware scanning, and sandboxing of downloads. This is the function the on-premises proxy used to perform, relocated so that it covers users wherever they are.

Cloud access security broker. Visibility and control over SaaS. In inline mode it sits in the traffic path and can block uploads to unsanctioned services. In API mode it connects to tenants such as Microsoft 365 or Salesforce to inspect data at rest, spot external sharing, and detect risky OAuth grants — which catches things the traffic path cannot see, including data shared directly between two cloud services.

Zero trust network access. Users reach specific internal applications through a broker that checks identity and device posture, rather than receiving a network route as a VPN would. This is usually the component that justifies the project, because it directly replaces a VPN concentrator whose vulnerabilities are a standing concern.

Data loss prevention. Applied consistently across web traffic, SaaS tenants, and private applications, with a single policy rather than one per channel.

Firewall as a service. Policy for non-web traffic, which matters once there is no on-premises edge handling it.

Why Organisations Move

The honest driver in most cases is that the old model no longer matches where work happens. Backhauling a home worker’s Microsoft 365 traffic through a VPN to a data centre so it can pass through a proxy and then go back out to the internet adds latency and cost for no security benefit, and it means the security stack is sized for peaks it should never see.

A second driver is appliance risk. VPN concentrators and perimeter gateways have been among the most exploited enterprise systems in recent years, and each one is a device you must patch urgently, monitor, and eventually replace. Moving that function to a service shifts the patching obligation to the provider — which is a genuine reduction in work and a transfer of risk rather than its elimination.

A third is consistency. One policy, applied identically regardless of location, is far easier to evidence to an auditor than a set of rules spread across appliances in several offices.

What to Examine Before Buying

Sequencing a Migration

Start with ZTNA for a pilot group, because the comparison with the VPN it replaces is immediate and measurable. Move outbound web traffic next, running the cloud gateway alongside the on-premises proxy before cutting over. Add CASB in API mode early — it produces useful findings about SaaS sharing and OAuth grants within days and requires no traffic change. Address firewall as a service and any remaining appliance functions last.

Keep the policy intent documented separately from the vendor configuration. The components are portable in principle and not in practice, and a written policy model is what makes a future migration a translation rather than a rebuild. Our Infrastructure and Architecture Review Services cover the target architecture and the order of work.

FAQ – Frequently Asked Questions

Is SSE the Same as SASE?

No. SSE is the security component set delivered from the cloud: secure web gateway, CASB, ZTNA, DLP, and firewall as a service. SASE is SSE plus software-defined wide area networking. Many organisations adopt SSE on its own because it replaces security appliances with a clear owner and budget, leaving branch connectivity for a separate decision.

Does SSE Replace Our VPN?

The ZTNA component does, and that is usually the strongest part of the business case. Instead of granting a network route, the broker connects a verified user and device to a specific application. This removes the internet-facing concentrator, which has been a leading target, and limits what a compromised account can reach to the applications it is entitled to.

What Are the Data Protection Implications?

The provider decrypts your traffic and holds logs of user activity, which is processing of personal data under UK GDPR. Name the provider in your records of processing, confirm where points of presence and logs are located, put international transfer safeguards in place, complete a data protection impact assessment, and tell staff their traffic is inspected.

Where Should We Start?

ZTNA for a pilot group, because it replaces something specific and the comparison is measurable. Run CASB in API mode alongside it, since it requires no traffic change and surfaces SaaS sharing and OAuth risks quickly. Move outbound web traffic next, in parallel with the existing proxy before cutting over, and leave remaining appliance functions until last.

Related Terms

You May Be Interested In These

What Is Malware Analysis?

Cybersecurity Terms

17 November 2026

What Is Malware Analysis?

Read More
What Is DevSecOps?

Cybersecurity Terms

17 November 2026

What Is DevSecOps?

Read More
What Are the Types of Threat Intelligence?

Cybersecurity Terms

17 November 2026

What Are the Types of Threat Intelligence?

Read More