Cloud playbooks
Each of the four providers has 22 playbooks in seven categories. A playbook lists where to look, the event names to search for, and the commands to contain and remove the attack. Each provider also has a page with the log setup, the first 15 minutes for any incident, and a table from the provider's own detections to the playbook to open. Use them with the cloud scenario, which covers what every cloud incident has in common.
Identity and access
Stolen credentials, taken-over accounts and the access an attacker leaves behind.
| Playbook | AWS | Azure | Google Cloud | Oracle Cloud |
|---|---|---|---|---|
| Long-lived credentials leakedA long-lived key or secret is stolen and used to change permissions. | IAM user access keys | Service principal secret | Service account key | API key or auth token |
| Human account takeoverAn attacker signs in as a person, then registers their own factors or changes the password. | Console or Identity Center user | Entra ID user | Google account | Identity domain user |
| Backdoor and persistenceAccess that survives the first clean-up: new principals, credentials, trust and federation. | Roles, keys, trust policies | Apps, credentials, federation | Service accounts and bindings | Users, keys, federation |
| Organization-level admin compromiseThe highest administrative identity is used, so every account or project is in scope. | Root or management account | Global Administrator | Org admin or super admin | Tenancy administrator |
| Cross-account and third-party access abusedAccess granted to a partner, a guest or another account is used from outside your control. | Cross-account roles | Guests and Lighthouse | Impersonation and delegation | Cross-tenancy policies |
Compute and containers
Workloads, servers and clusters used or abused by an attacker.
| Playbook | AWS | Azure | Google Cloud | Oracle Cloud |
|---|---|---|---|---|
| Workload credentials used off the hostCredentials issued to a workload are stolen and used from somewhere else. | EC2 instance role | Managed identity | Attached service account | Instance principal |
| Compromised server or virtual machineAn attacker has a shell on a cloud server. Preserve it before you isolate it. | EC2 instance | Virtual machine | Compute Engine instance | Compute instance |
| Kubernetes cluster compromiseA pod, node or cluster credential is used to reach the cluster API, other workloads or the cloud account. | Amazon EKS | Azure AKS | Google GKE | Oracle OKE |
| Compute hijacked for miningCompute is created or taken over to mine cryptocurrency at your cost. | EC2 and quota abuse | Virtual machines | Compute Engine | Compute |
| AI model service abusedStolen credentials run paid AI models, or reach the prompts, data and agents behind them. | Amazon Bedrock | Azure OpenAI | Vertex AI | OCI Generative AI |
Data and storage
Exposed, copied, encrypted or deleted data, and stolen secrets.
| Playbook | AWS | Azure | Google Cloud | Oracle Cloud |
|---|---|---|---|---|
| Object storage exposed or data takenA bucket or container is opened to the internet, or its contents are copied out. | S3 | Storage accounts | Cloud Storage | Object Storage |
| Database exposed or copiedA managed database, snapshot or backup is opened to the internet, shared or copied out. | RDS and snapshots | SQL and databases | Cloud SQL and BigQuery | Databases and backups |
| Data deletion and ransomwareData, backups or encryption keys are deleted or encrypted to cause loss or force a payment. | Deletion and ransomware | Deletion and ransomware | Deletion and ransomware | Deletion and ransomware |
| Secrets and encryption keys stolenSecret stores and key management are read to collect credentials for the next step. | Secrets Manager and SSM | Key Vault | Secret Manager and KMS | Vault |
Network and edge
Attacks on availability and on names and endpoints you own.
| Playbook | AWS | Azure | Google Cloud | Oracle Cloud |
|---|---|---|---|---|
| DDoS or application-layer attackTraffic floods or request patterns take a public endpoint down or scrape it. | Shield and WAF | DDoS Protection and WAF | Cloud Armor | WAF and load balancer |
| Dangling DNS and subdomain takeoverA DNS record points at a cloud resource you deleted, and an attacker claims that name. | Route 53 records | Azure DNS records | Cloud DNS records | OCI DNS records |
Pipelines and supply chain
Build systems and image registries that reach production.
| Playbook | AWS | Azure | Google Cloud | Oracle Cloud |
|---|---|---|---|---|
| CI/CD pipeline abusedA pipeline, its secrets or its trust in the cloud account is used to deploy attacker code or take credentials. | CI/CD and OIDC trust | DevOps and federated credentials | CI/CD and federation | DevOps and build credentials |
| Container image tamperingAn image in your registry is replaced or added, and workloads pull it. | ECR images | ACR images | Artifact Registry images | OCIR images |
Evasion and guardrails
Logging and controls turned off to hide an attack.
| Playbook | AWS | Azure | Google Cloud | Oracle Cloud |
|---|---|---|---|---|
| Logging or guardrails turned offAudit logs, detection or preventive policy is stopped or changed to hide activity. | CloudTrail, GuardDuty, SCPs | Diagnostic settings, Defender, Policy | Sinks, audit config, org policy | Cloud Guard, logs, Security Zones |
Provider and accidental
Incidents with no attacker: a vendor's bug, a provider's or operator's mistake, or a provider outage.
| Playbook | AWS | Azure | Google Cloud | Oracle Cloud |
|---|---|---|---|---|
| Data exposed by a bugA code or configuration change, yours or a vendor's, shows one customer's data to another. No attacker is involved. | Bug-caused exposure | Bug-caused exposure | Bug-caused exposure | Bug-caused exposure |
| Data lost through provider or operator errorA provider's mistake or your own change deletes resources or data that production depends on. | Provider or operator deletion | Provider or operator deletion | Provider or operator deletion | Provider or operator deletion |
| Regional outage or service disruptionA provider region or service fails, and you run on degraded service or fail over. | Provider outage | Provider outage | Provider outage | Provider outage |
Same job, different names
| Job | AWS | Azure | Google Cloud | Oracle Cloud |
|---|---|---|---|---|
| Control-plane audit log | CloudTrail | Activity Log, and Entra ID audit and sign-in logs | Cloud Audit Logs | Audit service |
| Threat detection | GuardDuty | Microsoft Defender for Cloud | Security Command Center | Cloud Guard |
| Organization-wide guardrail | Service control policies | Azure Policy | Organization Policy | Security Zones and quotas |
| Workload identity | Instance profile role | Managed identity | Attached service account | Instance principal |
| Temporary data link | Presigned URL | Shared access signature | Signed URL | Pre-authenticated request |
Retention, log names and commands differ by provider and license. Each provider page states what was checked against the provider's documentation and when.