GCP Audit Logging Not Enabled
Administrative actions are not recorded, so there is no way to establish who changed what.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable audit logging.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Any resource in the account
- The fix, by hand
- IAM and Admin → Audit Logs → select all services → enable Admin Read + Data Read + Data Write at the project level.
- For high-volume services (Cloud Storage, BigQuery) add per-principal exemptions instead of disabling the log type.
- Sink the _Default bucket to a long-term retention bucket (Logging → Logs Router → create sink to a separate project).
- Confirm new audit entries appear in Logs Explorer within 5 min.
- Document the retention window in the project's compliance README.
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-1254- 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.