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

SASE Trust

In SASE, there is no trust! SASE has been identified as an evolutionary, secure communications service. It is based on a collection of existing services. The standards being developed for SASE are providing a revolutionary improvement in how secure communications are achieved. Every few weeks, SASE evolves through the DevOps process. In production, the foundation for effective SASE is a Zero Trust Framework (ZTF).

With the ZTF, all resources, systems, communications, and so on are closed by default, and only by successfully meeting security policy requirements are resources unlocked. Imagine network cards that only receive electrical signaling once all policy requirements are met. In the ZTF, switch ports would require active Multi-Factor Authentication (MFA) approval prior to allowing a specific network card to receive any access to the port. There are potentially hundreds of layers of security that can be employed through the ZTF, and all those security controls can...