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 Design

Engineering success requires successfully executing a strategy through knowledgeable technical resources that are empowered and enabled to perform. Often, the organization relies on previously successful efforts to define the criteria for current or future success. The results of tactical execution that leverages past success creates variable results. Failure rates can average more than 50% of projects, even those that leverage professionally qualified teams.

Often, organizations launch a project due to pressure for success without a design that guarantees success. The project should be held in the planning stage until the design provides a 99.999% probability of success. The organization’s financial well-being is at risk from poorly designed projects.

At the peak of Enterprise Resource Planning (ERP) software implementation, over 80% of ERP projects that invested over $ 500,000 USD into the project caused the catastrophic financial failure of the organization...