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

SD-Why

The network, the internet, and the market are all evolving more quickly than technology departments can support. The old model is broken. In the old model, we upgrade hardware every five to seven years with many organizations running systems for up to 12 years. While this model is cost-effective from a capital expenditure perspective, it costs the organization the savings achieved multiple times over. The operating capital required for legacy hardware is put into labor, security mitigation, insurance, legal, lost productivity, organization performance issues, failed audits, and failed opportunities. The old model simply hides its costs and hurts the organization. Simply upgrading more quickly will not resolve the chasm between the old model and what is truly needed for success. Success requires a new model and a combination of technology, methods, tools, and education. The new model, when implemented correctly, can break even financially within 12 to 18 months while reducing...