GCP Data Access audit logs disabled
Cloud Audit Logs has three streams. Admin Activity is always recorded, but Data Access logs (who read or wrote data) are off by default for most services, leaving a blind spot.
Why it matters
After a breach, the key question is often 'what did they read' — without Data Access logs, there's no answer.
Compliance frameworks expect access to sensitive data to be auditable; the default leaves that gap.
How to check for it
- Console → IAM & Admin → Audit Logs: check which services have Data Read / Data Write enabled.
- Review the IAM policy's auditConfigs for the services that hold sensitive data.
How to fix it
- Enable Data Access audit logs for the services that store sensitive data (at least Data Read) and route them to a retained log bucket.
- Balance cost by enabling Data Access logging on sensitive services rather than everything.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Why are Data Access logs off by default?
- They can be high-volume (and billable), so Google leaves them off until you opt in per service.