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 Integrate

An API allows for custom, on-demand service integration. Leveraging an API allows multiple systems to interoperate with minimal effort and produce compounded benefits. Almost every software service on the market today allows integration via an API. An API can map functions between two products whereby a push and pull relationship is created. If we think of each separate SASE service as a module, an API connects the modules while defining the correct relationship via policy.

The future of all software-based solutions requires a data interchange through a common API framework. This framework operates as a spine of sorts, providing structure and commonality between services. Each module can be visualized as connected to the spine through a rib that is the API. Today, this is not a common approach, as most organizations are using a series of APIs in an as-needed fashion. The issue with the as-needed approach is that it requires a defined project to custom solutions for...