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

Human Issue

The human issue with SASE is that human learning has a framework incompatible with the pace of the market. The previous model for software development was the waterfall or linear project plan that allowed for the distribution of work between teams of various skills. Inevitably, each team worked at different paces, with different approaches to solving challenges in their portion of the project. As the project timeline passed through each phase of development, the would-be product became more incompatible, which required significant labor, time, cost, and testing to resolve the issues.

The standard approach, while comfortable to skilled humans, consistently fails to meet the intersections of cost and market timing to be an effective killer app, while lighter and less feature-rich, inferior products hit the market in a massively profitable manner. These lesser products run proverbial circles around the more robust, correctly designed, appropriately staffed, and well-funded...