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

Stakeholders Technical

The technical stakeholders should be apparent but may be elusive in this context. Security, network, systems, applications, DevOps, administrators, program management, helpdesk, and management are all easy to identify but often not included in project planning.

SASE policies are based on ZTF, and no access exists until a policy is developed and implemented that allows access to the resource defined in the policy. For this reason, every part of the organization must be considered for policy development input.

Examples of Technical SASE Service dependencies that may not have been required by previous technology-based solutions are as follows:

  • Compliance teams will need a data feed from the policy enforcement points
  • Accounting will need to ensure variable costs flow to the responsible departmental budget
  • Legal departments need to ensure no undocumented extension of liability exists
  • Human resource teams must be precise to the minute on personnel...