Book Image

Diving into Secure Access Service Edge

By : Jeremiah
Book Image

Diving into Secure Access Service Edge

By: Jeremiah

Overview of this book

The SASE concept was coined by Gartner after seeing a pattern emerge in cloud and SD-WAN projects where full security integration was needed. The market behavior lately has sparked something like a "space race" for all technology manufacturers and cloud service providers to offer a "SASE" solution. The current training available in the market is minimal and manufacturer-oriented, with new services being released every few weeks. Professional architects and engineers trying to implement SASE need to take a manufacturer-neutral approach. This guide provides a foundation for understanding SASE, but it also has a lasting impact because it not only addresses the problems that existed at the time of publication, but also provides a continual learning approach to successfully lead in a market that evolves every few weeks. Technology teams need a tool that provides a model to keep up with new information as it becomes available and stay ahead of market hype. With this book, you’ll learn about crucial models for SASE success in designing, building, deploying, and supporting operations to ensure the most positive user experience (UX). In addition to SASE, you’ll gain insight into SD-WAN design, DevOps, zero trust, and next-generation technical education methods.
Table of Contents (28 chapters)
1
Part 1 – SASE Market Perspective
7
Part 2 – SASE Technical Perspective
15
Part 3 – SASE Success Perspective
20
Part 4 – SASE Bonus Perspective
Appendix: SASE Terms

Secure Session

SASE sessions are the core function of an SASE Service. The session is initiated when a user, device, service, or application tries to initiate communications with another user, device, service, or application. The initiator of the session is the subject of the session. The resource being accessed on the remote end is the target. The subject must meet all policy requirements from the ZTF to initiate any communications. The session must be secure to be allowed by policy as an SASE session. Any session that violates the policy must be terminated immediately without waiting for a timeout period.

Each session has a definite starting point and ending point that is managed by an SASE Service. Each session is subject to context, whereby if the context changes, the session must be terminated. Each session is subject to quality requirements, where adverse quality conditions may be considered a potential active threat to security. Each session must be monitored for both security...