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

Learn Explain

The new learning model is a self-taught approach by which engineering talent is promoted and rewarded for perpetually learning in alignment with and ahead of organizational needs.

The model is a combination of just-in-time, trial and error, testing, self-education, and perpetual learning. It requires that the student and the teacher be the same person without a curriculum to learn from. The timeline for proficiency is within six weeks every time the product or service evolves.

When explaining the need, it is important to clarify that formal education will not be available until after the product is scheduled for removal from production because the speed of the market in response to security concerns requires immediate updates on demand.

Software development cycles necessitate a 6- to 18-week goal for learning any new product or service. There are no subject matter experts to leverage until after it is too late for the organization to benefit from the new product...