# Confused deputy problem

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

The confused deputy problem is a security issue in which an entity with no permission to perform an action coerces a more privileged entity into performing it. In AWS, a service or third party that holds access to your account can be made to act for someone else unless you scope the trust with a condition.

## An example, sourced

AWS recommends aws:SourceArn, aws:SourceAccount, aws:SourceOrgID or aws:SourceOrgPaths in resource policies wherever an AWS service principal is granted access, and sts:ExternalId for third-party roles.

## Why it matters here

These conditions are what the workbench looks for when it reads a trust policy or a service principal statement.

## Related pages

- [OIDC identity provider: meaning and an example](/glossary/oidc-identity-provider/)
- [IAM role: meaning and an example](/glossary/iam-role/)
- [Service-linked role: meaning and an example](/glossary/service-linked-role/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/IAM/latest/UserGuide/confused-deputy.html (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://iampolicygenerator.com/glossary/confused-deputy-problem/

This site is not affiliated with Amazon Web Services. AWS service and product names are used only to describe AWS services.
