Case 756427 · Cloud · L3 Applied

Cross-Account Confused Deputy

Practise as: Explain itLevel: L3 Applied
  1. 01 What is it?
  2. 02 How is it abused?
  3. 03 How do you stop it?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Third-party SaaS gets into your AWS account by assuming a role whose trust policy names the vendor account
  2. Confused deputy: another vendor customer submits your role ARN, and the vendor assumes your role on their behalf
  3. Fix: require sts:ExternalId in the trust policy, unique per customer and generated by the vendor, not the customer
  4. For AWS services acting for you, scope resource policies with aws:SourceArn and aws:SourceAccount conditions
  5. 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?

More Cloud cards

All Cloud cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09