PIVTR-D
RGoogle Cloud playbook · Provider and accidental

Data lost through provider or operator error

Resources or data disappear through a mistake by Google, your operators or your automation, such as a Terraform apply or a cleanup job. Stop the cause before you restore. In May 2024, Google Cloud deleted UniSuper's Google Cloud VMware Engine private cloud after a blank parameter in an internal provisioning tool had given it a one-year term. UniSuper restored from backups, including copies kept with another provider.

Look here

LogSearch for
Admin Activity audit logWho deleted what. A CI or scheduler service account in principalEmail points to automation: gcloud logging read 'logName:"cloudaudit.googleapis.com%2Factivity" AND protoPayload.methodName:"delete"' --project=<project> --freshness=30d
System Event audit logChanges made by Google systems and service agents: logName:"cloudaudit.googleapis.com%2Fsystem_event"
Access Transparency logGoogle personnel access to your data, with reason: logName:"cloudaudit.googleapis.com%2Faccess_transparency"
Personalized Service Health, Advisory NotificationsA Google-side incident on your projects: gcloud service-health events list --project=<project> --location=global
Cloud Asset InventoryThe deleted resource's last configuration, up to 35 days back: gcloud asset get-history --project=<project> --asset-names=<full-resource-name> --content-type=resource --start-time=<utc>
Automation recordsThe run that deleted it: Cloud Build history (gcloud builds list), Cloud Scheduler jobs, and the Terraform plan and state
Cloud Storage soft deleteSoft-deleted buckets that can come back: gcloud storage ls --buckets --soft-deleted --full
Cloud SQL and Backup and DROther copies that can come back: Backup and DR vaults, and retained Cloud SQL backups listed with gcloud sql backups list --instance=-

Contain

#Item
1Decide whether an attacker is involved. An unknown principal, an unexpected address or new credentials send you to deletion and ransomware
2Stop the automation before restoring. Disable the Cloud Build trigger, pause the pipeline that ran the apply, and pause scheduled jobs: gcloud scheduler jobs pause <job> --location=<region>
3Cancel a pending VMware Engine private cloud deletion, which runs 3 hours after marking by default: gcloud vmware private-clouds undelete <private-cloud> --location=<zone>
4Restore a shut-down project: gcloud projects undelete <project-id>
5Restore soft-deleted buckets, then their objects: gcloud storage restore gs://<bucket>#<generation>
6Restore a deleted BigQuery dataset with the SQL statement UNDROP SCHEMA <dataset>;
7Restore a BigQuery table from time travel: bq cp <project>:<dataset>.<table>@<epoch-ms> <project>:<dataset>.<restored>
8Open a P1 support case when production is down, with ISO 8601 times, project IDs and resource names. P1 needs Enhanced or Premium Support. Ask Customer Care for BigQuery fail-safe data in the same case

Eradicate and recover

#Item
1Restore databases from retained Cloud SQL backups, Backup and DR vaults or copies in another project, region or provider, then verify data with the owners
2Fix the plan, script or input that deleted the resources, and review every destroy in a plan before the pipeline runs again
3Keep backups in a Backup and DR vault in another project and region with enforced retention: gcloud backup-dr backup-vaults create <vault> --location=<region> --backup-min-enforced-retention=p30d
4Set deletion protection, project liens and bucket soft delete on production, following deletion and ransomware
5Keep a copy of systems you cannot rebuild outside Google Cloud, and test restoring from it
6Confirm restored services against the recover stage
Watch out
  • Actions by Google systems and staff may not appear in your audit logs. Access Transparency covers staff access to data on supported services only.
  • Recovery windows differ. Bucket soft delete keeps objects 7 days by default and up to 90, and a shut-down project can be restored for 30 days. BigQuery time travel keeps 2 to 7 days, plus 7 days of fail-safe that only Customer Care can restore.
  • After a Cloud SQL instance is deleted, its automated backups are removed one per day. Instant snapshots are deleted with their disk, while standard and archive snapshots remain.

Joint statement from UniSuper and Google Cloud; Google Cloud blog, Details of Google Cloud GCVE incident. Google Cloud documentation: Cloud Audit Logs overview; Access Transparency overview and logs; Personalized Service Health; Cloud Storage soft delete; BigQuery time travel and restore deleted datasets; Cloud SQL backups; disk snapshots; Backup and DR backup vaults; Customer Care best practices and Technical Support Services Guidelines; gcloud reference for asset get-history, vmware private-clouds delete and undelete, scheduler jobs pause, sql backups list and backup-dr backup-vaults create. Checked September 2026. Re-checked October 2026: Cloud Storage soft delete (7-day default, up to 90 days); BigQuery time travel (2 to 7 days, plus 7 days of fail-safe recovered through Cloud Customer Care); Delete and restore projects (30 days); joint statement of May 8, 2024 and Google Cloud blog of May 24, 2024.

Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.