Attack scenario · Data security

Sensitive S3 data exposure

How does sensitive data in Amazon S3 get exposed? Sensitive exports land in a bucket whose policy allows broad or cross-account reads, and are found and copied by someone outside the company.

Fictional, educational scenarioData exposureLast updated · ATT&CK v20.1

Attack path · 3 stages

  1. 1

    Discover the bucket

    T1619

  2. 2

    Read objects anonymously

    T1530

  3. 3

    Retrieve exports in bulk

    T1119

For leadership

Executive summary

Amazon S3 is secure by default, yet misconfigured storage remains a recurring source of data exposure because access is controlled in several places at once — account settings, bucket policies, access points, object ownership and identity policies. A single well-intended change to share data with a partner can widen access far beyond the intended audience. The key executive questions are where regulated or customer data actually lives, which of those locations are reachable from outside the company, and whether the organization would be able to tell what was read if something went wrong.

For engineers

Technical summary

Bucket policies granting Principal "*" (with or without weak conditions), cross-account principals, or access points with broad policies allow reads by unintended parties. Block Public Access at the account level prevents public grants but not authenticated cross-account grants.

Environment and assumptions

Fictional company: analytics exports containing customer contact data are written nightly to "exports-shared". To let a partner fetch files, an engineer added a bucket policy allowing s3:GetObject to Principal "*" with a condition on a referrer header. Account-level Block Public Access is disabled for this account.

  • The adversary discovers or guesses the bucket name.
  • S3 data events are disabled.
  • Fictional and simplified for education.

Interactive

Attack sequence

Select a stage, or use the arrow keys, to see preconditions, evidence and controls.

Stage 1

Discover the bucket

Bucket names appear in front-end code, documentation or are guessed from naming conventions.

Preconditions
  • Predictable or leaked bucket name
Required access
  • None (internet).
Potential evidence
  • S3 server access logs showing anonymous requests
Defensive controls
  • Block Public Access at account level
Text version of the attack sequence
  1. Discover the bucket (T1619). Bucket names appear in front-end code, documentation or are guessed from naming conventions. Preconditions: Predictable or leaked bucket name. Evidence: S3 server access logs showing anonymous requests. Controls: Block Public Access at account level.
  2. Read objects anonymously (T1530). The referrer condition is trivially spoofed; objects are downloaded without credentials. Preconditions: Bucket policy allows Principal "*"; Block Public Access disabled. Evidence: Only S3 server access logs or data events record anonymous GetObject. Controls: Never use aws:Referer as an access control; Pre-signed URLs or partner-specific principals for sharing.
  3. Retrieve exports in bulk (T1119). Export file names follow a date pattern, so the adversary scripts requests for every nightly file going back months. Preconditions: Predictable object keys; No request-rate alerting on the bucket. Evidence: High volume of anonymous GetObject requests in access logs; Unusual data-transfer-out charges. Controls: Random, non-guessable object keys for shared files; Short object retention on sharing buckets.

Technique mapping

MITRE ATT&CK and ATLAS techniques referenced in this scenario
IDTechniqueTactics (official)Stages
T1619Cloud Storage Object DiscoveryDiscovery1
T1530Data from Cloud StorageCollection2
T1119Automated CollectionCollection3

Technique names and tactic assignments come from the imported MITRE data. Mapping a stage to a technique is Securitain’s analysis.

Why the attack can succeed

  • Referer headers are client-controlled and are not a security boundary.
  • Account-level Block Public Access was disabled to allow the change.
  • Without data events or access logs, the scope of exposure is unknowable.

What prevents or limits the attack

What may detect the attack

Detection signals and telemetry sources
SignalTelemetry sourceNotes
Bucket policy or ACL changes that add public or external principalsCloudTrail management events; IAM Access Analyzer external access findings—
Anonymous or external GetObject requestsS3 server access logs or CloudTrail data events—

Telemetry only helps if it is enabled before the incident and someone acts on it. Listing a signal here does not mean it is collected or monitored in your environment.

What Securitain may assess

  • Securitain can assess todayPublic and cross-account exposure checks on S3, KMS, SQS, SNS and Secrets Manager resource policies. Learn more
  • Securitain can assess todayDetection of identities with sensitive permissions such as broad S3 access, KMS decrypt or Secrets Manager reads. Learn more
  • Securitain can assess todayFinding-to-control mapping for supported frameworks (for example CIS, SOC 2, HIPAA, NIST and PCI DSS). Learn more

For leadership

Executive implications

confidentiality
Customer contact data may be copied by unknown parties.
compliance
Potential notification obligations; demonstrating scope requires logs that may not exist.

No financial loss estimates are given; impact depends on the data, contracts and regulation involved.

Next steps

  1. Enable account-level Block Public Access everywhere; document exceptions.
  2. Review Access Analyzer external-access findings for S3.
  3. Enable access logging on buckets holding customer data.

References

MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain