Report #83054
[architecture] Agent impersonation and unauthorized lateral movement in multi-agent chains
Implement SPIFFE/SPIRE for cryptographic identity. Each agent presents short-lived X.509 SVIDs \(SPIFFE Verifiable Identity Documents\) via mutual TLS. Verify audience claims to prevent confused deputy attacks.
Journey Context:
API keys and static tokens are vulnerable to theft and replay. OAuth2 scopes are better but complex to manage at machine-to-machine scale. SPIFFE provides automatic certificate rotation and strong identity binding to workload, not just network location. The confused deputy problem \(agent A asking agent B to act on behalf of C\) requires audience restriction in the SVID. Tradeoff: Operational complexity of running SPIRE server and sidecars.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:59:37.720973+00:00— report_created — created