TL;DR: CEO impersonation still slips past native Microsoft 365 filters because attackers lean on lookalike domains, display-name spoofing, and behavioural mimicry, IRONSCALES says. Mailbox intelligence and impersonation controls have to work with authentication to catch trust-based abuse.
Editorial analysis by NHI Mgmt Group, based on content published by IRONSCALES: “How to Stop CEO Impersonation in Microsoft 365 in 7 Steps (2026)”.
Key questions
Q: Why do lookalike domains remain effective even when email authentication is in place?
A: Lookalike domains work because SPF, DKIM, and DMARC validate legitimacy for the domain being used, not for visually similar domains that attackers register themselves.
Q: What are the signs that impersonation protection is too narrow?
A: If only exact spoofing is blocked while first-time senders, executive display names, and partner-domain lookalikes still reach inboxes, the control set is too narrow.
Q: What breaks when executive impersonation is trusted inside normal workflows?
A: The break is not only fraud, but governance.
Practitioner guidance
- Protect high-value executives first Add CEOs, CFOs, and other wire-transfer authorities to impersonation protection before expanding the policy to lower-risk users.
- Quarantine impersonation detections by default Set user impersonation, domain impersonation, and mailbox intelligence detections to quarantine so suspicious messages do not reach inboxes while analysts review them.
- Align SPF, DKIM, and DMARC records Publish and test authentication records with a quarantine or reject policy so exact-domain spoofing fails and attackers are forced into harder-to-execute impersonation techniques.
Bottom line: Executive impersonation succeeds by abusing identity trust and conversational urgency, not by carrying obvious malware.
Glossary terms: Business email compromise, Mailbox Intelligence, Domain Impersonation, Display Name Spoofing
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
CEO impersonation is an identity governance failure, not just an email hygiene issue. The attack succeeds by abusing organisational trust in executive identity, then using that trust to bypass approval discipline. That means the relevant control question is not whether a message looked spammy, but whether the organisation can verify who is actually requesting action. Practitioners should treat impersonation as a governance gap at the point of decision.
A few things that frame the scale:
- Impersonation fraud accounted for over 85% of all fraud attacks in 2025.
A question worth separating out:
Q: How should security teams respond when a CEO impersonation email is discovered?
A: Contain the message across the tenant, review who received it, and determine whether any payment, credential, or approval action was taken. Then tighten the executive protection list, verify authentication coverage, and review mail flow rules so the same pattern is blocked earlier next time.
👉 Read our full editorial: CEO impersonation in Microsoft 365 exposes the limits of native filters