AegisAI Perspectives · 067
Choose email security for AI-generated spear phishing by how it judges sender history and the request, flags lookalikes and pulls mail after delivery.

The best email security for AI-generated spear phishing judges the request against the sender's history, not the wording. IC3 logged more than 22,000 AI-related complaints in 20251. AegisAI investigates every email for what it is trying to do22. The criteria below hold on Microsoft 365, Google Workspace or both, and they name no vendor.
AI-generated spear phishing is a targeted email written or researched with a language model, aimed at one person or one role. The FBI says criminals use AI-generated text to appear believable to a reader in spear phishing and other fraud schemes5. Its 2025 report adds that chat generators can quickly create official-sounding emails that mimic a company's CEO, with phishing links or directions to wire funds3.
Businesses reported losses over $30 million to BEC scams involving AI in 20252.
In one study with 101 participants, fully AI-automated phishing emails reached a 54% click-through rate, on par with human experts and against 12% for the control group17. The information the AI gathered about each target was accurate and useful in 88% of cases18.
Legacy filters look for known bad links and known bad senders, and they also lean on broken language. Criminals use generative AI for translation to limit grammatical or spelling errors6.
An attacker can register a domain, set up SPF for it and send with a From address in a different domain, because SPF validates only the MAIL FROM domain11. A lookalike domain with valid DNS records can pass SPF, DKIM and DMARC7.
The FBI describes CEO-style emails that carry only directions to wire funds.
Ask what the product compares the message with. Microsoft 365 itself adds sender and recipient history plus behavioral analysis to its authentication checks12, so ask what a new tool reads beyond that.
Question to ask a vendor: when a known name asks for a wire transfer in plain text, with no link or file, what does your product compare that request with?
Built-in protection on every cloud mailbox does not include impersonation protection; Defender for Office 365 adds user and domain impersonation protection8. Each anti-phishing policy protects at most 350 named users, and by default none are configured10.
Mailbox intelligence uses AI to learn user email patterns with frequent contacts9. Ask whether a tool does the same for every mailbox, without a list to maintain.
Question to ask a vendor: do you flag a first message from a domain one letter away from a regular contact's domain, for every user instead of a named list?
Run this test on your own mail during a trial. Take a past thread with a supplier, then ask the vendor how its product scores a reply in that thread that changes payment details. The FBI's own advice for these requests is to verify changes in account information through a secondary channel or two-factor authentication19.
Question to ask a vendor: show me the verdict on a reply inside a real thread from a known sender that asks to change where money goes.
Zero-hour auto purge in Microsoft 365 searches only the last 48 hours of delivered email, and users are not notified when it moves a message13. A link that was clean on delivery and weaponized later can still phish a user when rewriting is off and the client does not support Safe Links14.
Ask for the median time from arrival to verdict and from verdict to removal, measured on your mail. Ask whether removal covers forwards and every mailbox that received a copy.
Question to ask a vendor: what is your median time from arrival to removal, and does a removal reach every mailbox the message reached?
For sign-in, a Conditional Access policy in Microsoft Entra can require the built-in Phishing-resistant MFA strength, which allows a FIDO2 security key15. For payment, verify every change of account details on a second channel.
For your own domain, publish DMARC with p=reject, so receivers reject mail that fails DMARC in your name16.
Question to ask a vendor: when your product flags a payment request, who sees the flag, and does it reach the approver before the payment runs?
The approaches that stop AI-generated attacks read the request and the sender relationship, and they remove mail after delivery.
| Criterion | API-based | Gateway | Built-in platform controls | Managed service |
|---|---|---|---|---|
| Plain text request, no link or file | Reads the message and the mailbox history after delivery | Reads each message in the mail path before delivery | Adds sender and recipient history to authentication | Depends on the tools the provider runs |
| Lookalike or impersonated sender | Can compare every sender with each user's contacts | Checks sender domains in transit | Impersonation lists, at most 350 users per policy | Depends on the provider's rules |
| Compromised known sender | Can compare a reply with the earlier thread | Sees the single message, not the mailbox | Authentication passes; history signals only | Depends on the access you grant |
| Removal after delivery | Removes mail from mailboxes through the platform API | Needs a separate mailbox connection | Zero-hour auto purge, last 48 hours | Depends on the provider's tools |
| Mail routing | No MX change | MX record change; mail passes through it | Inside the platform | Set by the provider's tools |
Evaluate it on your own mail with a yes or no checklist, and ask for evidence on each line.
Does a plain text payment request from a known name get its own check?
Does the tool compare a message with the sender's past mail to that recipient?
Does it flag a domain one letter away from a regular contact's domain, for every user?
Does it flag a reply that changes payment details inside a real thread?
Is the median time from arrival to removal measured on your mail?
Does a payment flag reach the approver before the payment runs?
Do your admins and finance approvers sign in with phishing-resistant MFA?
Is DMARC set to p=reject on every domain you send from?
Illustrative example, figures are fictional. A message arrives from a domain one letter away from its law firm's domain, signed by the partner the finance lead emails every month. It asks to move a $72,000 settlement payment to a new account today. Email authentication passes for the attacker's domain. Tool B flags it: first message from this domain, a payment change the thread never mentioned, a deadline set in the same email.
AegisAI catches fake executives, vendors and payment requests, even with no link or file to scan23. When authentication passes, it does not rely on it; the verdict rests on what this sender has sent you before and on the request itself24. It opens every link, file and QR code in a sandbox, follows it to the end, and judges what it finds there20. It reads mail through the API, reaches a verdict in 1.9 seconds at the median, and removes a convicted message within seconds21. Every verdict comes with its reason in plain language25, and you can see it on your own tenant.
Track three numbers from the first day of the trial.
The best one judges the request against the sender's history. It flags lookalike or compromised senders that pass authentication, then removes the mail after delivery. IC3 logged more than 22,000 AI-related complaints in 2025. Test any shortlist on your own mail with the checklist above.
Criminals use generative AI to limit grammatical and spelling errors, and AI-automated emails matched human experts at 54% click-through in one study.
A lookalike domain with valid DNS records can pass every authentication check. DMARC at p=reject asks receivers to reject mail that fails DMARC for your own domain.
Impersonation protection needs Defender for Office 365, each policy protects at most 350 named users, and zero-hour auto purge searches only the last 48 hours of mail. The page on stopping AI phishing that gets past Microsoft Defender covers the settings.
Use a second channel. The FBI advises verifying changes in account information through secondary channels or two-factor authentication. Call the person on a number you already hold, never one given in the email.
In Microsoft Entra, Conditional Access can require the Phishing-resistant MFA strength, which allows a FIDO2 security key.