S3 Bucket with Public Access Enabled
Anyone who learns the bucket name can read its contents, which is the single most common cause of public data exposure on AWS.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Block public access on S3 bucket.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- S3 Buckets on AWS
- The fix, by hand
- S3 → bucket the resource → Permissions → Block public access (bucket settings) → Edit → enable all four.
- Review the bucket ACL. Remove any AllUsers / AuthenticatedUsers grants.
- Review the bucket policy. Drop statements with Principal "*" unless the bucket is intentionally a static-site origin.
- For genuine static sites, keep BPA on at the account level and serve via CloudFront with an Origin Access Control.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-086- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.