SASE Lifecycle
The SASE life cycle idea is one that Neil Danilowicz, while working on the MEF W117 project, came up with to allow AI-based security to be inserted into an active SASE session.
Once the SASE session is in place, the subject actor, the target actor, and the traffic flowing between them in the SASE session need to be monitored. This monitoring needs to be active to prevent security vulnerabilities and attacks.
SASE sessions are terminated as soon as the conditions in the subscriber policies are not being met. In other words, SASE sessions have life cycles that are orchestrated by the SASE service provider.
By creating a third wheel mechanism, a life cycle session can be established by leveraging the same security posture and session. This allows you to insert secure monitoring and management and prepares you for a future AI-based solution to actively mitigate quality, performance, and security that falls below the service levels defined in the SASE service.
...
