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 Bonus

The first several years of SD-WAN solutions consistently failed in production. This failure was primarily due to an overall lack of understanding of the differences between legacy, routed WAN solutions and the new SD-WAN solutions that leveraged policy differently to forward traffic instead of relying on the routing protocols. The disaggregation of data and control plan for policy-based decision-making in SD-WAN effectively grandfathered much of the skill of the world’s best network engineers. SD-WAN felt as if programmers purposely sought to eliminate network engineering as a skill in favor of active software-based decision-making.

It is interesting that the WAN engineer and the SD-WAN engineer can have an entire conversation using the same words but with two distinctly separate definitions for each word. Both WAN and SD-WAN designs use routing and policy but in completely different ways from each other. In fact, it has often been easier to teach SD-WAN to someone...