Why Cloud Security Breaks When Identity Is Treated as a Separate Layer
Security Boulevard, Thursday, November 12th, 2026
Identity and access must be designed alongside cloud infrastructure, not bolted on later, to avoid fragmented and lingering permissions.
The author argues that identity is part of cloud architecture, and designing it late leads to overlapping roles, inconsistent policies and access that is hard to audit.
AI agents given ordinary service accounts leave identities behind after their tasks end, so agent identities should be tied to the agent lifetime.
Federation can let CI/CD pipelines such as GitHub Actions authenticate to the cloud without stored long-lived keys, but it needs governance.
Least privilege also requires lifecycle management of permissions as environments grow.