The problem
Business e-mail compromise usually starts quietly: a phished password, then a forwarding rule or a hidden rule that deletes replies, then a changed bank account on an invoice. The signs are spread across Outlook, the Microsoft 365 admin centre, Entra sign-in logs and PowerShell, and most small businesses have no one who looks. Microsoft's own detection lives in Defender plans the business does not have.
Features
- One scan, one page: forwarding rules (visible and hidden), SMTP forwarding on the mailbox, delegates, Full Access and Send As, OAuth app consents, mailbox auditing state, MFA state, recent sign-ins by country and client, registered devices and app passwords
- Attack patterns, not just settings: rules that delete or move mail from the bank, IT or the boss; rules keyed on 'invoice', 'payment' or 'password'; forwarding to look-alike domains; consents to mail-reading apps; sign-ins from two countries in an hour
- Clean-up checklist in the right order: revoke sessions, reset password, remove rules and forwarding, revoke consents, re-register MFA, check sent items and deleted items for what the attacker did, warn contacts; each step done from the screen or handed to the administrator
- Evidence pack for the bank, insurer or police: timeline, rule contents, sign-in records and the exact changes made
- Scheduled re-check with alerts, and a tenant-wide version for administrators that watches every mailbox
How it works
Sources
- Graph: mailbox settings, message rules, auditLog sign-ins, OAuth2 permission grants, devices
- Exchange Online PowerShell: forwarding, delegates, permissions, audit status, hidden rules via Rules Manager
- Entra: MFA registration, risky sign-ins where the licence exposes them
Patterns
- Rule and forwarding patterns from published BEC cases, kept as a local list the user can extend
- Geography and client heuristics explained in plain words, never as a verdict on their own
Who it is for
Bookkeeper
The changed bank details
A customer paid a fake invoice. The check finds a rule moving the customer's replies to RSS Feeds, a sign-in from another continent and a consent to an unknown mail app; the clean-up and the evidence pack take twenty minutes.
MSP technician
The monthly check
Fifty client mailboxes scanned on the first of the month; two new forwarding rules found and removed before anyone lost money.
Solicitor
The suspicious password prompt
After a convincing phishing page, the scan shows no rules or sign-ins yet; the password reset and session revoke close the door anyway.
Benefits
- One page that answers whether someone else is in the mailbox
- Clean-up in the right order, from the screen
- An evidence pack ready for the bank and the insurer
Built to be trusted
- Read-only scan; every clean-up step is confirmed and logged
- Evidence is kept locally with hashes
- Findings explain why they matter and what is normal
Good to know
Sign-in history and risk detections depend on the tenant's licences: the free Entra tier keeps seven days of sign-ins, and risky sign-in detail needs Entra ID P2. Mailbox auditing must be on to see what an attacker read. An administrator role is needed for the tenant-wide version. The check finds the common patterns; a careful attacker can avoid them, which is why the scheduled re-check exists.
Under the hood
For technical readers
- Microsoft Graph (rules, settings, sign-ins, consents, devices)
- Exchange Online PowerShell
- Local pattern list; Reports; Security Nudge