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 Lifecycle

The SASE life cycle idea is one that Neil Danilowicz, while working on the MEF W117 project, came up with to allow AI-based security to be inserted into an active SASE session.

Once the SASE session is in place, the subject actor, the target actor, and the traffic flowing between them in the SASE session need to be monitored. This monitoring needs to be active to prevent security vulnerabilities and attacks.

SASE sessions are terminated as soon as the conditions in the subscriber policies are not being met. In other words, SASE sessions have life cycles that are orchestrated by the SASE service provider.

By creating a third wheel mechanism, a life cycle session can be established by leveraging the same security posture and session. This allows you to insert secure monitoring and management and prepares you for a future AI-based solution to actively mitigate quality, performance, and security that falls below the service levels defined in the SASE service.

...