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 Business

Often, business stakeholders are represented by technology resources, but in the case of SASE Services, it is critical to involve the business stakeholders within the organization to define expectations from a UX perspective, as well as the business value requirements. With legacy systems being replaced by SASE, open access to systems was a default expectation that ultimately caused security vulnerabilities. With ZTF, the SASE Service will restrict all access to the new service or its resources until a policy exists that provides access. For this reason, the business needs to define expectations in a concise but comprehensive document. Success and test criteria should be defined at the point of receipt of the business expectations document.

Business value is the key expectation of technology departments. When that expectation is met, the organization invests in technology-based solutions. The opposite is also true as each organization has finite resources that...