Case A539E3 · Cloud · L4 Advanced

Stopping Data Leaving AWS

Practise as: InterviewLevel: L4 Advanced

Interview questionAn attacker steals valid credentials inside our AWS organization. How would you stop them copying S3 data to their own account?

  1. 01 Answer
  2. 02 Example
  3. 03 Trade-offs
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Data perimeter: only trusted identities, reaching trusted resources, from expected networks
  2. Trusted resources: SCP denying S3 writes unless aws:ResourceOrgID is your org, so data cannot land in attacker buckets
  3. Trusted identities: RCPs or bucket policies denying principals outside aws:PrincipalOrgID
  4. Expected networks: deny unless aws:SourceVpce or corporate IPs, so stolen creds fail from the internet
  5. Trade-off: AWS services, vendors and public buckets need carve-outs (aws:ViaAWSService); validate with CloudTrail first

If the interviewer pushes back

  • Which legitimate workflows break first when you enforce aws:ResourceOrgID, and how do you carve them out safely?

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