Case 756427 · Cloud · L3 Applied
Cross-Account Confused Deputy
- 01 What is it?
- 02 How is it abused?
- 03 How do you stop it?
What a strong answer covers
Try it out loud first. Then check yourself:
- Third-party SaaS gets into your AWS account by assuming a role whose trust policy names the vendor account
- Confused deputy: another vendor customer submits your role ARN, and the vendor assumes your role on their behalf
- Fix: require sts:ExternalId in the trust policy, unique per customer and generated by the vendor, not the customer
- For AWS services acting for you, scope resource policies with aws:SourceArn and aws:SourceAccount conditions
- Review trust policies for wildcard or whole-account principals without conditions; IAM Access Analyzer flags external access
If the interviewer pushes back
- Why must the vendor generate the ExternalId, and why is it not treated as a secret?