Concrete ways an agent goes wrong here without governance, and the control that catches each one.
01An agent probes the metadata endpoint
An agent reaches the cloud instance metadata endpoint to lift credentials, the move behind a breach that walked out with over a hundred million records. Authorization refuses the request and records it, so a server-side request does not become a credential theft.
02An agent escalates its own permissions
An agent tries to grant itself access beyond the identity role it was given. Tier-gated authorization blocks the escalation server-side and logs it, so an agent cannot widen its own reach.
03An over-permissioned token exposes storage
An agent is handed a storage token far broader than its task needs and begins enumerating buckets, the pattern that once exposed tens of terabytes. Scope-bounded authorization confines it to the storage its job actually requires.
04An agent abuses the Kubernetes API
An agent with cluster access starts issuing API calls outside its workload's scope. Authorization holds it to the namespaces and actions it was granted and records the attempt, so a foothold in one workload does not become the whole cluster.
05Halt cloud agents in an incident
A suspected compromise means cloud automation must stop now. One switch halts every governed agent in under a twentieth of a second, confirmed, and the halt holds through a restart.