Disable Data Access Audit Logs for a GCP Service
Platform: GCP
Mappings
- MITRE ATT&CK
- Defense Evasion
Description
Removes the Data Access audit log configuration for Cloud Storage from the project IAM policy. Data Access audit logs record data access operations such as reads and writes to GCS objects. Disabling them reduces an attacker's visibility footprint in Cloud Logging.
Warm-up:
- Snapshot the current project IAM policy (including any pre-existing audit config
for
storage.googleapis.com) so it can be restored on revert
Detonation:
- Set a DATA_READ and DATA_WRITE
auditConfigentry forstorage.googleapis.com(overwriting any existing config) - Remove the
auditConfigentry forstorage.googleapis.comfrom the project IAM policy via the Cloud Resource Manager API
Revert:
- Restore the exact
auditConfigthat existed before detonation (including any custom log types or exempted members), or leave the config absent if it was not present before
References:
- https://cloud.google.com/logging/docs/audit/configure-data-access
- https://cloud.google.com/resource-manager/reference/rest/v3/projects/setIamPolicy
- https://attack.mitre.org/techniques/T1562/008/
- https://redcanary.com/threat-detection-report/trends/cloud-attacks/
- https://www.sysdig.com/blog/suspicious-activity-gcp-audit-logs
Instructions
Detection
Identify when Data Access audit log configuration is removed from the project IAM policy
by monitoring for SetIamPolicy events in GCP Admin Activity audit logs where
the request removes or reduces auditConfigs entries.