Seven attack techniques
In each of these seven techniques, the control that ran got a real or ordinary answer: a genuine sender, a clean link, a real Microsoft sign-in, a token that had already passed MFA. See what the control saw, what the person saw, and the recommended steps for Microsoft 365 and Google Workspace.
What the control said. Reported by researchers, or inferred.
Inside the report
Each page gives the verdict, the attack chain and links to the original research.
Get the report →FAQ
Security and IT teams on Microsoft 365 or Google Workspace who want to check their own settings against the seven techniques in the report.
By type: 8 reviews, 7 changes, 3 questions for your email security vendor and 3 staff briefings. One example: in Entra ID > Conditional Access, confirm the policy that blocks device code flow is On, not Report-only. In Report-only, device code sign-ins are logged but not stopped.
Three verdicts are reported by the researchers: the Dell order emails, the replayed session tokens and the Teams chats. The other four are inferred from how a standard control works, and those pages say what the inference rests on. None of the seven cases was replayed through AegisAI for this report.
Yes. AegisAI connects to Microsoft 365 or Google Workspace by API, starts in read-only monitoring mode and runs beside your current tools. Book a demo to start.
A five-day scan of your own mail.
Book a demo →About five minutes to connect · no MX change · you keep the findings report