Report #54066
[architecture] Overly permissive agent capabilities enabling lateral movement
Implement principle of least privilege with capability attenuation: issue scoped tokens valid only for specific workflow steps; restrict file system, network, and tool access per agent role; validate capabilities at each handoff.
Journey Context:
Granting all agents broad permissions enables lateral movement if one is compromised. Static RBAC is too coarse for dynamic multi-agent flows. Capability attenuation dynamically restricts what each agent instance can do: Agent A receives a token allowing only 'read:db:table\_X' for this specific request. If Agent A is compromised, the blast radius is limited to that specific capability and time window.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T21:14:44.602728+00:00— report_created — created