Data Access Audit Logs Not Enabled

Data Access audit logs are not enabled for sensitive services, so reads of data and secrets, and many data changes, are not recorded in Cloud Audit Logs.

SeverityLow
CVSS 3.13.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N Open in the calculator
CVSS 4.02.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-778: Insufficient Logging
OWASP Top 10A09:2025 Security Logging and Alerting Failures
CategoryInsufficient Logging

Description

Cloud Audit Logs record activity in Google Cloud in several streams. Admin Activity logs, which record configuration changes such as IAM policy updates and resource creation, are always written and cannot be disabled. Data Access logs, which record API calls that read resource configuration or metadata (ADMIN_READ) and calls that read or write user-provided data (DATA_READ and DATA_WRITE), are disabled by default for most services, BigQuery being the main exception, because they can be voluminous.

The finding applies where Data Access logs are not enabled for services that hold sensitive data, such as Cloud Storage, Secret Manager, Cloud KMS, Cloud SQL and Firestore. Without them there is no record of who read an object in a bucket, accessed a secret version or used a key to decrypt data. The gap does not by itself let an attacker in, but it leaves the organisation unable to determine what data an attacker read after compromising an account, a key or a workload, or to detect unusual reads of secrets and sensitive buckets as they happen.

Investigations then have to assume that everything reachable was accessed, which widens the scope of any breach notification. The impact is lower where data access is recorded at another layer, such as by the application itself, or where the projects concerned hold no sensitive data.

The gap is identified on the Audit Logs page of the console's IAM settings, or in the auditConfigs section of the organisation, folder and project IAM policies, which lists the services and log types enabled.

Remediation

  • Enable DATA_READ and DATA_WRITE logs, and ADMIN_READ where useful, for services that hold sensitive data, at organisation or folder level so that every project inherits the configuration.
  • Manage volume and cost by enabling the logs selectively, by service and project, and by exempting well-understood high-volume principals, rather than leaving the logs off.
  • Route audit logs through an aggregated sink to a central logging project, a locked log bucket with retention set to the organisation's needs, or the organisation's SIEM, and restrict who can change sinks and log buckets.
  • Create alerts for sensitive data access, such as reads of high-value secrets or unusually large volumes of object reads.

For example, the following entry in an IAM policy enables Data Access logs for Cloud Storage:

auditConfigs: - auditLogConfigs: - logType: ADMIN_READ - logType: DATA_READ - logType: DATA_WRITE service: storage.googleapis.com

Confirm the fix by reading a test object or secret and finding the corresponding Data Access entry in Logs Explorer.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Google Cloud Findings

Every Google Cloud finding