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

Design Function

Each SASE Service independently has a functional model for design provided by the developer of that service. In the process of SASE design, each functional model must be laid out to compare functions for overlap. Integration mapping will be via API and that should allow the push/pull relationships between each service. The overlay of functionality requires a policy design that eliminates competition between features, functions, or attributes utilized by each service.

SASE functional design accounts for overlap between integrated services and remediates functional overlap that could impact performance or security. Historically, this has not been a requirement for technical architects as each system or service would run independently with little to no competition at a functional level. Often, in the SDN, SD-WAN, and SASE markets, the implemented solution has a 10-30% overlap in functionality, which causes negative interactions between systems. Competition for authority...