PlaybookChecked 16 November 2026
Cloud account compromise incident response playbook
Stages
The template in full
1 When to use this playbook
Use this playbook when a cloud identity, such as a user, administrator, service account or application, is used by someone other than its owner.
2 Before you start: prerequisites
Complete these before an incident, as part of planning.
- Sign-in and audit logs are on and retained in the cloud tenant.
- The accounts that can grant application consent are known and limited.
- Two-step sign-in is required, with phishing-resistant methods for administrators.
- A break-glass administrator account exists and is stored securely.
3 Workflow
Work in this order. Record each step and its time in the incident log.
- Identify the account, the time window and the indicators: unusual sign-ins, impossible travel, new devices, new mailbox rules, new application consents.
- Contain: revoke sessions and tokens, reset the password and require a fresh two-step enrollment.
- Review application consents granted by the user or tenant-wide, and remove any suspicious application. Check permissions such as read and send mail.
- Rotate administrator passwords, private keys and service account secrets where compromise is suspected.
- Review what the account could reach and what it did: mail, files, configuration changes, new accounts.
- Check other accounts for the same pattern, such as a password spray across many users.
- Restore changed settings and add detections for the technique.
4 Decision points
Stop at each of these and record the decision, the decider and the time.
| Decision | Who decides | Information needed |
|---|---|---|
| Is it one account or many? | Technical lead | Sign-in patterns across accounts |
| Was an administrator account used? | Technical lead, executive sponsor | Role assignments, configuration changes |
| Was data accessed or sent out? | Privacy lead | Audit logs, downloads, forwarding |
5 Notices to check
Open section 10 of the plan and confirm whether any of these start a notice clock.
- If personal data was accessed, start the data breach plan.
- If the cloud provider is a processor for your customers, check section 12 and customer notice terms.
6 Exit criteria and follow-up
Close the playbook only when all of these are true.
- All sessions and tokens revoked; credentials rotated.
- No suspicious application consents remain.
- Detections are in place for the technique used.
About this playbook
What is the incident response playbook for cloud account compromise?
Microsoft publishes investigation playbooks for password spray, app consent grants, compromised and malicious applications, and token theft. The app consent playbook names the Application Administrator and Cloud Application Administrator roles as able to grant consent on behalf of the organization, and flags risky permissions such as Mail.* and Contacts.*.
CISA's containment guidance includes changing administrator passwords, rotating private keys and service or application account secrets where compromise is suspected.
Download the template
Free, no sign-up. Word (.docx, 3 KB): download. PDF (46 KB): download. Both files carry the same text as this page, edition 16 November 2026.
Related pages
- Incident response playbook: what it is and how to build a library
- Free incident response plan template
- Insider threat incident response playbook
- Lost or stolen device incident response playbook
- DDoS attack incident response playbook
- Third-party and supplier incident response playbook
- Incident response plan templates: the full set
- Incident response steps: the order and who does what
Sources
- Microsoft Learn, Password spray investigation
- Microsoft Learn, App consent grant investigation
- Microsoft Learn, Incident response playbooks overview
- CISA, Cybersecurity Incident & Vulnerability Response Playbooks (November 2021)
Last reviewed 16 November 2026. Each source above was read that day.