Compliance · Low severity
GCP GCS Bucket Access Logging Disabled
There is no record of who read or wrote objects, so a question about data exposure cannot be answered.
Free to start. No card. The playground just needs your work email.
Google Cloudprovider
Lowseverity
Compliancewhere it shows up
Manualfix, change spelled out
Google Cloud
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
01
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
02
Explain
Every finding says exactly what to change: Enable access logging on GCS bucket.
03
Fix
The finding opens with the change already spelled out, so the fix is one ticket, not an investigation.
- Applies to
- GCS Buckets on Google Cloud
- 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-142- 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.