What is Security Services Edge (SSE)?

The ideas around Security Service Edge make total sense:

1. Faster workplace changes, especially due to the pandemic, made old security measures like firewalls and the devices that ran them outdated.
2. Relentless IT innovations continue to add new security vendors (have you attended an RSA conference?) 
3. Coincident with the pandemic, Zero Trust became another crucial IT initiative.
4. Long before SSE, internal applications were becoming webified. SaaS consumption is the highest-growth spend in IT followed closely by IaaS and PaaS. With internal and public clouds, nearly everything is done with a web browser!

Replacing outdated IT security equipment, consolidating vendors as much as possible, implementing Zero Trust access and securing cloud consumption created a fearsome foursome of needs that can be potentially satisfied with SSE. 

What is Security Services Edge?

Security Service Edge (SSE) offerings typically aggregate cloud-delivered security functions that attempt to work together to safeguard user access to web applications, cloud services, and private applications. It is intended to act as a security layer at the "edge" of the network, closer to users and applications, rather than relying on a central data center for security.

While most services are cloud-delivered, some services include a desktop component for both ensuring desktop security posture and steering traffic to the relevant cloud services.

Why Did Security Services Edge emerge?

Secure Services Edge (SSE) emerged as a response to the evolving IT landscape, particularly the rise of cloud computing, mobile workforces, and the dissolving traditional security perimeter. Here's a breakdown of the key factors:

Shift to Cloud

Businesses are increasingly relying on cloud-based applications and data storage. Traditional security models, centered on a central data center, became inadequate to secure access to these resources spread across the internet.

Mobile Workforce

With more employees working remotely, the need arose for secure access to corporate resources from anywhere, on any device. Legacy security solutions couldn't handle this kind of flexibility.

Dissolving Perimeter

The traditional network perimeter, where security was concentrated at entry points, is no longer effective. Data and applications are scattered across the cloud and user devices, making it harder to define a clear boundary to protect.

Application Webification

The age of client-server computing evolved to web access to back-end systems.

What is the origin of Security Service Edge?

The term "Secure Services Edge" (SSE) is a relatively new concept, emerging in the tech world around 2021. Here's a breakdown of its origin:

• Attributed to Gartner: Market research firm Gartner is credited with coining the term SSE in its 2021 Strategic Roadmap for SASE Convergence.
• Building on SASE: SSE is considered a subset of the broader concept of Secure Access Service Edge (SASE). SASE itself was introduced by Gartner in 2019 to address the need for a converged security model for the cloud era.
• Addressing Cloud Security Challenges: Gartner identified a gap between cloud security design and traditional WAN service edge design within organizations. SSE emerged as a way to bridge this gap and provide a more comprehensive security solution for cloud-centric environments.

While the specific technology behind SSE might have roots in earlier security tools, the term itself is a recent development specifically tailored to the growing need for securing access to cloud applications and services.

What are the main functional components of SSE?

SSE (Security Service Edge) combines networking and security functionalities to deliver secure access. Here are the main components of a typical SSE offering:

Secure Web Gateway (SWG)

• Acts as a checkpoint for all web traffic entering or leaving the network.
• Enforces web access control policies to restrict access to inappropriate or unproductive websites.
• Filters malicious websites, malware, and phishing attempts.

Read about Menlo Security SWG

Cloud Access Security Broker (CASB)

• Provides visibility and control over cloud applications used by the organization.
• Enforces security policies for cloud app usage, including data access and encryption.
• Prevents data loss from cloud storage and applications.

Read about Menlo Security CASB

Zero Trust Network Access (ZTNA)

• Implements a "zero trust" approach, where no user or device is inherently trusted.
• Grants access to resources based on continuous verification of user identity, device trust, and context.
• Secures access to applications regardless of user location (office, home, etc.).

Read about Menlo Secure Application Access

Firewall as a Service (FWaaS)

• Provides cloud-based firewall functionality to inspect and control network traffic.
• Filters unwanted traffic based on pre-defined rules and security policies.
• Protects against unauthorized access attempts and network breaches.

Read about Menlo Security Firewall as a Service

1. Enhanced Security Posture

• Unified security platform: SSE endeavors to consolidate multiple security functions into a single vendor offering, potentially providing a centralized approach to security management.
• Improved threat detection and prevention: In theory, by combining technologies like SWG, CASB, and ZTNA, SSE can offer enhanced protection against certain advanced threats and data breaches.
• Stronger compliance posture: There is evidence that in some cases, SSE has helped organizations meet regulatory requirements by providing visibility and control over data access and usage.

2. Improved User Experience

• Faster application access: By delivering security services closer to users, SSE can reduce latency and improve application performance. However, this argument is a bit unclear, because each of the services that comprise SSE were intended (at least, originally) to be close to users. Certain SSE components, like SWG and CASB, were somewhat aged out by so many users being sent home during the pandemic. 
  
  SSE however, is required by analysts such as Gartner to be cloud-delivered, which, by definition, may not be close to users. For fast application access to be truly realized, an SSE offering cloud points-of-presence, or POPs must be as close to each user community as possible. This must also accrue to mobile users in coffee shops and hotel rooms and common spaces.
• Simplified user experience: SSE can streamline authentication and authorization processes, making it easier for users to access resources gated by their SSE solution.
• Increased productivity: By eliminating some security-related friction points that users experience, SSE can boost user productivity and satisfaction.

3. Cost Efficiency

• Reduced operational costs: some SSE solutions can help organizations reduce the costs associated with managing multiple security point solutions. (See “Arguments against Deploying SSE”, below.)
• Optimized resource utilization: In certain cases, by consolidating security functions, SSE can reduce consumption of network resources and reduce certain infrastructure costs, such as support costs for aging infrastructure elements.
• Faster incident response: SSE can, in some cases, help organizations detect and respond to security incidents more quickly, reducing potential damage.

Cost and Complexity

• High initial investment: Implementing an SSE solution can be expensive, requiring significant upfront costs for hardware, software, and professional services.
• Complex integration: Integrating SSE with existing security infrastructure and applications can be complex and time-consuming, requiring specialized expertise.
• Ongoing management costs: SSE solutions require ongoing management and maintenance, including updates, patches, and monitoring, which can add to operational expenses.

Performance Impact

• Increased latency: Depending on the SSE solution and network conditions, there might be an increase in latency for users accessing cloud applications, impacting user experience.
• Network congestion: SSE can introduce additional traffic to the network, potentially leading to congestion and performance issues.

Vendor Lock-in

• Dependence on a single vendor: Choosing a specific SSE vendor can create vendor lock-in, limiting flexibility and potentially increasing costs in the long run.
• Limited choice of features: Some SSE solutions may not offer all the required features or functionalities, forcing organizations to rely on additional point solutions.

Security Risks

• Single point of failure: If the SSE service experiences an outage, it can disrupt access to critical applications and data, increasing security risks.
• Data privacy concerns: SSE solutions handle sensitive user data, raising concerns about data privacy and protection.

Potential Overlap with Existing Solutions

• Redundancy: Some organizations may already have security solutions in place that overlap with SSE functionalities, leading to potential redundancy and increased costs.
• Complexity: Managing multiple security solutions can increase complexity and introduce inconsistencies.