At a glance
- Owner
- StratQuad
- Version
- November 2026
- Applies to
- Organisations using cloud email, particularly Microsoft 365 and Google Workspace
- Mandatory
- Guidance
Key points
- Much BEC now starts with adversary in the middle phishing, which steals a session cookie after multi factor authentication succeeds. Resetting the password alone does not evict the attacker.
- Containment means revoking sessions, removing attacker inbox rules and persistence, and re registering MFA methods, as well as resetting the password.
- Call the bank's fraud team immediately for any payment already made. Speed matters more than anything else in recovering funds.
- Payroll diversion typically arrives as a request to change an employee's bank details, sent from the real employee's compromised account.
- Phishing resistant authentication and an independent call back check on payment detail changes prevent most cases.
Recognise it
Common indicators:
- A request to change a supplier's or employee's bank details, often urgent and near a payment run.
- Inbox rules that move, delete or forward messages containing words such as invoice, payment, bank or payroll.
- Sign ins from unfamiliar locations or hosting providers immediately after a phishing email, often with a valid MFA claim.
- Replies from customers or suppliers to emails the user never sent.
- New mailbox permissions, forwarding addresses, OAuth app consents or registered MFA methods.
Contain
- Revoke all sessions and refresh tokens for the account, then reset the password, or disable the account until the investigation is complete.
- Remove attacker persistence
Inbox rules, forwarding, delegated mailbox access, newly registered MFA methods and devices, and consented applications.
- Block attacker infrastructure seen in sign in logs and the phishing site's domain.
- Search the tenant for the same phishing email and sign ins from the same infrastructure, to find other compromised accounts.
- Warn finance and HR to freeze pending bank detail changes and verify any made in the past weeks.
Practitioner note
Run the containment steps together, in one sitting. Resetting the password first while sessions remain valid tells the attacker they have been noticed while leaving them inside the mailbox. In Microsoft 365, check the unified audit log for MailItemsAccessed and inbox rule events to establish what the attacker read and changed; that drives the data breach assessment.
Recover payments
- Call your bank's fraud team now, give the payment details and ask them to contact the receiving bank. Recovery chances fall sharply within hours.
- Report to Report Fraud (England, Wales and Northern Ireland) or Police Scotland, and record the crime reference.
- Tell the affected supplier or employee through a known good channel, not the email thread.
- Notify your insurer if you hold cyber or crime cover.
Assess notification duties
A compromised mailbox almost always contains personal data. Assess whether the attacker accessed it and whether the breach is reportable to the Information Commission within 72 hours. See Reporting a cyber incident in the UK.
Prevent recurrence
- Phishing resistant authentication (FIDO2 security keys or passkeys) for finance, HR, payroll and administrators first, then everyone.
- Conditional access requiring compliant or managed devices, which defeats most stolen session reuse.
- An independent call back to a number already on file for any change of bank details, with no exceptions for urgency or seniority.
- Alerts on new inbox rules, forwarding and MFA method registration.
- DMARC at quarantine or reject on your own domains, to stop direct spoofing.
Evidence expected
For the incident record and any insurance or regulatory follow up, keep: sign in logs showing the attacker's sessions; audit log extracts of rules, forwarding and mail access; the phishing email with headers; payment records and bank correspondence; and the crime reference number.
Common mistakes
Common mistakes
- Password reset only, leaving the stolen session and inbox rules active.
- Verifying a bank detail change by replying to the same email thread.
- Waiting until the next working day to call the bank.
- Not checking other mailboxes that received the same phishing message.
Sources
- NCSC. Business payment fraud (opens in a new tab)
- Microsoft. Respond to a compromised email account in Microsoft 365 (opens in a new tab)
- City of London Police. Report Fraud (opens in a new tab)
- Report Fraud. Payment diversion fraud (opens in a new tab)