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

Case Design

To design the Use Case, first, start with the end state production goals in mind. The Use Case must be defined concerning the UX. Identify the who, what, where, how, when, and why of the use case’s requirements.

In the following Use Case, think about what could be refined or added to better describe the experience goal. The end user gets sub-120 ms access to any application, anywhere, at any time, from three different device types. The security limits from ZTF are expanded to allow sub-optimal encryption and that traffic is remediated through a DMZ. Security also allows MFA, which is both a convenience and a risk mitigator through a policy. The why is defined as a high-level justification for the service to be provided as each service carries a risk that must be accounted for and mitigated.

Example Use Case

ZTNA – Zero Trust Network Access:

  • What: A remote access VPN replacement built to allow ZTF-based access to both cloud and on-premises...