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 Manual

The manual method of managing SASE, while simple and easy for seasoned operational teams, varies greatly between each service integrated into an overall SASE framework-based solution. A single organization may have dozens of SASE services, all of which have their own management platform. Each service requires the continual focus of the operational team to maintain security, quality, and performance requirements. Each individual service will require training. Each service will require a different configuration set. Extensive cross-service testing will need to be performed in a lab prior to exposing it to an end user. Each change is an opportunity for a lapse in an SLA. Each change will affect the end user experience.

The value of every device, logical service, application, or platform being operated by a one-on-one human for support evaporated more than 20 years ago. Many years ago, a major corporation would custom-build desks individually for management employees at...