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

Zero Framework

The initial components of the ZTF are IAM, access control, policy management, policy enforcement, and monitoring of all components. The ZTF does nothing by itself and only provides value when leveraged in conjunction with SASE services. These are dependent upon the ZTF components to continually provide effective security. Eventually, most SASE services will eliminate overlapping solution components. However, it is not expected that all attribute overlap will be removed. The reason some services must overlap features, functions, attributes, and other components is context. Context is the most often misunderstood concept when providing any human or machine communication. We will cover context in the upcoming Zero trust section.

Zero trust leverages the foundational concepts of the validated identity of the user, device, system, service, resource, or application, prior to any policy that allows access.

Identity is the first and highest priority. If we can eliminate...