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 Trust

SASE trust should always be zero trust. Many first-generation SASE offers have been based on SD-WAN or a firewall with added functions. The entire success of the SASE Service depends on effective security. For effective security, SASE deployments must leverage ZTF. SASE Security Policy will allow traffic that has met all the criteria for authorization; then, SASE Forwarding Policy will forward traffic as defined by that policy. Identity and Access Management Function (IdAM or IAM) serves as the basic building block for identifying who or what is trying to access the network. IdAM/IAMmay get you in, but ZTF will shut you down if something changes while traffic is in session. SASE trust is zero trust because there is never a time that a session should be allowed to exist unless all the policy conditions are continually met.

The first rule in SASE is that there is no trust. Any discussion about trusting in SASE should be considered using common vernacular and not considered...