Check ID:
Provider: GCP
Service:
Severity: MEDIUM
Categories:
Resource type:
iam_audit_logs_enabledProvider: GCP
Service:
iamSeverity: MEDIUM
Categories:
logging, forensics-readyResource type:
cloudresourcemanager.googleapis.com/ProjectWhat this check verifies
GCP project has Cloud Audit Logs configured to capture administrative operations and data access events for services and principals (per IAM Audit Logs, includingADMIN_READ, DATA_READ, DATA_WRITE).
Risk
Absent or partial audit logging reduces visibility into who accessed data or changed configurations, hindering detection and forensics. Misused identities can alter IAM to persist access, exfiltrate data, or delete resources, impacting confidentiality, integrity, and availability.Recommendation
Enable comprehensive Cloud Audit Logs for all services and principals, includingADMIN_READ, DATA_READ, DATA_WRITE. Avoid exemptions. Set org/folder defaults, centralize and retain logs, enforce least privilege on log access, protect logs from alteration, and alert on anomalous access.
Remediation
- Terraform
- Dashboard steps
References
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/gcp/CloudIAM/record-all-activities.html
- https://cloud.google.com/logging/docs/audit/
- https://docs.cloud.google.com/logging/docs/audit/configure-data-access
Where this check fires
This check runs on every scheduled scan against your GCP account. Findings appear at Cloud Security → Findings filterable byCheck ID = iam_audit_logs_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to GCP checks