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

DevOps Impact

The DevOps mindset is a doctrinal approach to continual improvement through secure development iterations. The two primary impacts on SASE from a DevOps perspective are security and reliability. Each iteration of the DevOps loop should produce a product that is more reliable and secure. Each iteration should cause material improvement over at least one aspect of the product or service. DevOps practice should cause us to think in a more perpetual fashion than our previous experiences would suggest.

The pressures in farming as an industry often cause overutilization of natural resources, which in turn destroys the resources necessary for successful farming. If DevOps methods were applied to farming, the natural resources available for farming would increase in both volume as well as quality. This continual improvement approach to farming would create increased productivity while reducing the consumption of natural resources.

In technology, the farming example is proven...