Summary
In this chapter, we talked about the SASE service, its working definition, components, roles, and requirements, and then visualized the service in flight. A SASE service is simply a secure communications service. That service may be from a single branded software or hardware manufacturer or may be composed of multiple services from separate providers. The components of a SASE service include IAM, AAC, PEP, and EPC. This list of components will continue to evolve but this model helps us understand the various roles, which are subject to change each time a request for communication is initiated. Any endpoint can be in multiple roles at any given time, whereas each role requires separate security authentication and may be subject to multiple policies. The requirement for a SASE service is a least-privilege web of security policies and services. This web allows any service to restrict access, ensuring nothing slips through a gap. SASE services are complex, with constant updates...