IPCRIME | The Digital Arsenal | Research guide | November 21, 2026. The Tigerfish transcription-data exposure illustrates how sensitive media can become publicly accessible without anyone defeating a login screen. For organizations that own Amazon S3 buckets, regular permission reviews are a practical way to reduce that risk. This guide uses AWS documentation; it is not a claim that IPCRIME audited Tigerfish or performed a live S3 penetration test.
Start with the right question
Ask whether each bucket is intended to serve public files, restricted internal documents or data shared with a specific external account. That classification matters before changing access settings: a deliberate public website and a confidential archive have different design requirements. Confidential recordings, identity documents, employment information and customer exports should not be publicly readable merely because an organization needs to share them with one partner.
Understand Block Public Access
Amazon S3 provides four Block Public Access settings that work at bucket, access-point, account and AWS Organizations levels. AWS recommends enabling all four for accounts and for buckets that do not explicitly require public distribution. The service applies the most restrictive applicable combination. One setting may stop new public access-control lists from being added without removing an old policy, so operators should review the complete effective policy rather than relying on a single checkbox.
Audit from the AWS console, not from an outsider’s scanner
Within an account you are authorized to administer, open the S3 console and examine the External access summary. AWS’s IAM Access Analyzer for S3 reports findings where a bucket is accessible to the public or to other AWS accounts. It can identify whether a bucket policy, access point or ACL grants that access. Access Analyzer requires an appropriate account-level analyzer in each Region; it does not automatically inspect everything merely because a single Region’s page is open.
A practical five-step review
- Inventory: list buckets across Regions and identify an owner, business purpose and classification for each.
- Inspect: use IAM Access Analyzer findings to locate public and external access within your own AWS environment, and review the relevant policy or ACL.
- Decide: determine which access is intended and contractually authorized, including temporary sharing with vendors.
- Restrict: for confidential buckets, enable appropriate public-access blocks and replace broad permissions with narrower account roles or approved access mechanisms.
- Validate: confirm that authorized applications still work, recheck analyzer findings and document an owner responsible for future policy changes.
Do not break intentionally public services
Some static sites and download portals genuinely serve public files. AWS warns administrators to understand application impact before activating blanket blocks. For S3-backed web content, the company’s documentation describes secure delivery through CloudFront origin access controls as an alternative to making the storage bucket itself publicly readable. The broader principle is to make the published application public while keeping its underlying storage protected whenever possible.
What Access Analyzer does not answer
A finding that a bucket is public does not prove someone downloaded its data. The absence of a public-access finding in one Region does not prove that every workload and identity in the organization is appropriately restricted. IAM identity permissions, resource policies, cross-account integrations, object-level behavior, replication and logging all need consideration. AWS says external-access summaries are refreshed on a schedule; administrators should verify changes and not treat a dashboard as real-time forensic evidence.
Preserve the ability to investigate
Where appropriate, use AWS logging and monitoring services to retain access evidence, while considering cost, retention and privacy obligations. If a sensitive bucket is discovered to be public, first secure the exposure through an authorized change, preserve relevant configuration and access records, and involve the organization’s security and privacy contacts. Do not upload the exposed content to another cloud service or publish a sample online to prove the lapse existed.
Related IPCRIME reporting
Tigerfish investigation: transcripts and raw recordings exposed in public storage; Underground Leak Watch: evidence-based exposure records.
Official documentation and limits
AWS: S3 Block Public Access settings; AWS: reviewing bucket access with IAM Access Analyzer; AWS: S3 bucket protection and distribution options. This is an original documentation-grounded guide, not hands-on test results, a vulnerability exploit or a recommendation to probe third-party accounts. Perform these steps only on infrastructure you own or are explicitly authorized to administer.