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 Automation

The automation of management functions is simple in that it requires permission granted in advance to perform up to 95% of all management functions and the autonomy to do so.

Most management platforms today offer libraries full of automation that are never used due to fear. While identified as risk or liability management, the enactment of a fear-driven process negates the sunk cost of the automated features of almost every piece of software.

Plan for automation! In the process of developing change control governance, each organization must create boundaries around what automations are acceptable to the organization. If the answer is none, the organization is missing cost reductions that have already been paid for and that may be realized through simple planning and testing.

To prepare for automation approvals, each automation must be tested in a non-production environment with manufacturer support, with lessons learned being documented. The honesty of...