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

Summary

A multidimensional approach is required to integrate IAM, context, situational components, time of day, location, and many other factors to deliver sub-millisecond, active security that is continuously relevant.

SASE requires IAM to unlock each policy in a ZTF. SASE leverages MFA to act as an enhancement for IAM. Context provides descriptive attributes that may be leveraged to add dimensional layers to security. The situational circumstances around access to a given resource may be grounds for allowing, blocking, or actively shutting down a given SASE session. Situational awareness equips active IPS and AIOps to intervene when necessary. Integrating IAM with SASE must be modular due to the pace of software release cycles. Attaching new products and services in real time must be done on demand and on the same day; it cannot take weeks to implement due to the impact that security threats will have on the organization.

Effective security has always been a layered approach...