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 Template

The templating process provides a method for seeking common ground in any technical architecture. From the simple template that a carpenter makes to repeat a design for a wooden chair to the complex templates used by Cloud Service Providers (CSP) to provision services on-demand, templates are used everywhere for consistent results. With SASE, SD-WAN, or cloud-based solutions, the use of a template is a requirement for scale, performance, consistency, and security.

In this context, a template is just a software-based, repeatable model that is created during the design process. This template is to be leveraged on demand for standing new services up. By templating the design of a site, service, device, connection, policy, or another solution component, each subcomponent of an approved architecture becomes consistent. Through consistency, scale is an available option, whereas legacy models that implement one subcomponent at a time with human labor create a variation that...