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

Service Requirements

The requirements for a SASE service start with secure communications and then improving on that concept. In terms of the requirements of the service, various business, performance, communication, and security needs must be met. From the perspective of the service itself, it will have requirements from the manufacturer, the industry, and the government. More information will be provided in this section.

Business requirements include cost, value, function, and ease of use. A well-designed solution will reduce current or future costs while enabling secure business communications.

Performance requirements include bandwidth, throughput, quality, latency, and the speed at which changes take place. The system should perform at the current market standards regarding performance and be able to adapt to increase performance as new performance resources become available.

Security requirements include encryption, encapsulation, logging, response, mitigation, remediation...