01Description
Cloud storage containers, such as Amazon S3 buckets or Azure Blob containers, were found to allow public listing or reading of objects without authentication.
02Impact
Anyone who discovers the container can download its contents. Publicly exposed storage has been the cause of many large data breaches, and attackers scan for it continuously.
03Severity
Typically
High
Typically High. Severity follows the data exposed: Critical for personal, financial or credential data; Low if the bucket intentionally hosts public assets only.
04How to verify
- 1Identify storage containers associated with the organization's domains and applications.
- 2Test anonymous list and read access.
- 3Review the data exposed without downloading more than needed to establish sensitivity.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Remove public access and enable account-level public access blocks (for example S3 Block Public Access).
- 2Serve intentionally public files through a CDN with restricted origin access.
- 3Audit bucket and container policies regularly with a cloud security posture tool.
06References
Draft findings like this from your own evidence
Book a demo