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

SD-WAN Design

SD-WAN benefits from the DevOps mindset. With DevOps, the steps in the process flow are basically: Plan, Code, Build, Test, Release, Continuous Deployment and Continuous Integration, Operate, Monitor through Continuous Feedback Loop, Notify, and Action. With a legacy WAN solution, the planning stage was the primary focus, and it was thought that design perfection will be achieved. With SD-WAN, perfection is only achieved through dynamic iteration. This can also be considered the CI/CD-based optimization process. SD-WAN design works better with an implementation of a Proof of Concept (POC), then pilot, then full production implementations. Each implementation is then optimized through the DevOps process, even if no code is modified but the solution is refined through the process.

The best SD-WAN design starts with a high-level design that takes into consideration the requirements, such as sites, circuits, bandwidth per site, aggregate hub bandwidth requirements, cloud...