S3 Bucket Access Logging Not Enabled
There is no record of who accessed which objects, so an exposure cannot be scoped after the fact.
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: Enable access logging 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
- Create (or reuse) a dedicated logs bucket (same region, different bucket from the source).
- Apply a lifecycle policy on the logs bucket: transition over 30 days to Glacier, expire over 365 days.
- S3 → bucket the resource → Properties → Server access logging → Enable → target the logs bucket.
- Confirm a log object lands in the target bucket within 1h of the next request.
- Set CloudTrail S3 data events on the logs bucket if you need read-API audit too.
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-173- 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.