Confused deputy
Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.
A security problem where something without permission to do an action tricks a more-privileged party into doing it. A cloud service acting on your behalf is a typical deputy, so the trust on its role has to say which of its customers or resources may use it.
An example, sourced
AWS documents the confused deputy problem as a security issue where an entity that lacks permission to perform an action can coerce a more-privileged entity to perform the action. AWS says it provides tools to protect your account when you give third parties (cross-account) or other AWS services (cross-service) access to resources in your account, and recommends keys such as aws:SourceArn and aws:SourceAccount in resource policies.
Why it matters here
Agent platforms are deputies by design: a service assumes your role. Conditions on the trust policy tie the role to one agent so another customer's agent, or another of yours, cannot use it. It is a cheap condition to add and an easy one to omit.
Related pages
Sources
- https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html, read 10 Nov 2026
Last reviewed 16 Nov 2026.