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

Integrate Identity

SASE provides direct integration paths and, in some cases, comes bundled with an identity management solution. Direct integration reduces the design, build, deploy, and operation cycles for the project but takes the disadvantaged approach of linear integration. In the early days of secure communications, linear integration was not just the only option for security but was a preferred quality mechanism. Allowing a programmer to develop the security mechanisms from a foundational level up allowed the organization to achieve the desired effect with precision. This approach has been instrumental in academically training the critical thinking process that is espoused in college-educated engineering teams. In other words, the right way of developing products has been consistently proven wrong when measured financially, through performance-based metrics, tested for security, or audited for compliance.

Many organizations have failed financially in the past two decades...