Case A539E3 · Cloud · L4 Advanced
Stopping Data Leaving AWS
Interview questionAn attacker steals valid credentials inside our AWS organization. How would you stop them copying S3 data to their own account?
- 01 Answer
- 02 Example
- 03 Trade-offs
What a strong answer covers
Try it out loud first. Then check yourself:
- Data perimeter: only trusted identities, reaching trusted resources, from expected networks
- Trusted resources: SCP denying S3 writes unless aws:ResourceOrgID is your org, so data cannot land in attacker buckets
- Trusted identities: RCPs or bucket policies denying principals outside aws:PrincipalOrgID
- Expected networks: deny unless aws:SourceVpce or corporate IPs, so stolen creds fail from the internet
- 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?