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

Case Value

The primary value proposition for the Use Case method is simplicity. When communicating with SASE stakeholders, there must be a common basis of understanding that must be a written and agreed-upon scope. Without a written Use Case, the SASE project may cause consequences that impact the organization. The written Use Case allows the project manager to bring all stakeholders together for design and implementation.

For the project manager, a collective understanding of the final project outcome is necessary for the achievement of the project. Often, project teams vary in skill, understanding, perspective, and the context in which they interpret the project scope. By designing the project with a series of Use Case documents, each team can focus on their specific subject matter expertise. By doing so, the proof of value materializes in the testing phase of the project as each use case is proved ready for production.

The security team gains specific insights into what exceptions...