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

Management Systems

Orchestration is a requirement for SASE, as human intervention to security threats or active attacks is not possible. It is not possible for the IT staff of an organization to both detect an attack and stop it within 2 milliseconds. The actual goal should be for attacks to be stopped within one tenth of a millisecond. Effective SASE design can achieve this goal.

The master orchestration platform should be something that will consolidate and collect telemetry from downstream orchestration, while interacting in a push/pull relationship with subordinate orchestration platforms. The master orchestrator must be able to share all collected knowledge with the SIEM as well as all other integrated service components with their respective tools.

API management should go beyond catalog services and provide policy compliance with permanent API backbone services. The API backbone should be a permanent construction that provides constant access to all available APIs for...