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 Managed

Effective management from a SASE perspective will be contractual. The modern IT organization must become effective at vendor management in real time. In the past, contracting was more of a procurement or legal team function. As we move into the cloud-native world, the average life cycle of an individual application running on a system is close to five minutes. In the past, an IT organization would spend more than a year evaluating applications, more than a year deploying those applications, and would plan to operate those applications for 10 years or more.

Today, the nature of DevOps allows us to create applications that are dynamically generated, both on-demand and provided just-in-time to meet the need. The speed of change will only accelerate in the future as we leverage resources where they are needed, when they are needed, how they are needed, and most importantly, providing the specific UX that is needed. By tearing down an application when it is no longer needed...