How Do You Stop Executive Impersonation and Whaling Attacks?
Published 2026-11-14 · Reviewed 2026-11-14 · 6 min read · By the Ingenious AI team
Is someone impersonating your domain right now?
Run the free DomainGuard scan: lookalike registrations, MX-armed variants, certificate-transparency and CAA checks for your domain, in one report.
Run my free DomainGuard scanThe short answer
You stop executive impersonation by defending the two channels it uses: the inbox, with DMARC enforcement, external banners, and display-name anomaly flagging; and the hierarchy, with a rule that money and credentials never move on an emailed instruction alone — whatever name is on it. Whaling works because the forged message borrows real authority and manufactures urgency ('handle this quietly, I am in a meeting'). Technical controls reduce how many fakes arrive convincingly; the verification culture decides whether the ones that arrive get obeyed.
Why the executive costume is the attacker's best one
Ordinary phishing asks a stranger to trust a brand. Executive impersonation asks an employee to obey a boss — a reflex organisations train deliberately and reward daily. The message needs no links and no attachments, so most technical filters find nothing to catch: a short, plain text from 'the CEO' asking finance to prepare a confidential payment, sent at a plausible moment, from a domain one letter off, or from a free mailbox wearing the executive's display name. The entire payload is social.
Attackers prepare the costume with public material: leadership pages, press releases announcing deals (which explain confidential payments beautifully), social posts placing the executive at a conference — the 'I am travelling, handle this discreetly' framing writes itself. Finance staff are the primary audience, but executive assistants, HR (payroll diversions, employee data), and IT help desks (credential resets) all receive versions tuned to what each can give.
The three delivery shapes
Shape one is the lookalike domain: your company's near-name, fully authenticated for itself, indistinguishable on a phone preview. Shape two is the spoofed exact domain, which DMARC at p=reject eliminates entirely — one reason enforcement matters even for companies whose customers are never phished. Shape three is display-name spoofing from a free or unrelated address: the name reads as your CEO, the address is a random mailbox, and it works because mobile clients show names large and addresses barely at all.
Each shape has a matched control, and none of the controls is optional if the others are missing. DMARC enforcement kills shape two. Gateway lookalike and display-name flagging exposes shapes one and three — many gateways can specifically banner mail where an executive's display name arrives from outside the organisation. Monitoring finds shape one's domains at registration and MX-arming, days before the message. Layered, the costume stops fitting; unlayered, any single gap is the whole attack.
The rule that ends the con: verify out of band
Publish one norm and rehearse it until it is culture: no payment, bank change, payroll change, or credential reset is actioned from email alone, regardless of sender, urgency, or confidentiality claims. Verification means a call or message on a channel and number already known — and the norm must explicitly protect the verifier. Staff should hear, from the real executive, in person and in writing: 'I will never ask you to skip verification, and anyone claiming I did is the attack.'
That last step — the executive publicly disowning urgency — is what separates policies that hold from posters that fade. Whaling leans on the victim's fear of disobeying; only leadership can retire that fear, by making verification the loyal act and blind obedience the risky one. Companies that run one live-fire simulation with leadership's blessing usually find the culture flips within a quarter: reporting a suspicious 'CEO' message becomes a story staff tell with pride.
Protect the executives themselves
Whaling also targets the top directly: fake board-member messages to the CEO, forged investor or lawyer approaches, and credential phishing dressed as finance or legal portals. The same verification norm protects them, supported by unglamorous hardening — hardware-key or app-based MFA on executive mailboxes, a separate published channel for genuinely urgent approvals, and assistants briefed as a security control, because the assistant's inbox is where executive impersonation most often lands first.
Reduce the raw material too. Leadership pages need names and roles, not personal email formats and direct numbers; deal announcements can be celebrated without narrating payment timelines; executives' social posts about travel are lovely and also an alibi factory for 'I am unreachable, wire it now' messages. None of this requires hiding — just editing the public record with the attacker's reading of it in mind, once a year, as part of the same audit rhythm as DNS.
When an attempt lands: the quiet drills
Treat every detected impersonation as a free rehearsal with real ammunition. Preserve the message and headers; check whether the sending domain was known and armed (and if not, why monitoring missed it); confirm nobody actioned anything, by asking the reachable humans rather than assuming; and feed the domain into takedown and gateway blocklists the same day. If the impersonation used your exact domain, the aggregate reports and gateway logs will show whether it was an isolated attempt or a campaign.
Report attempts back to staff in aggregate — 'three executive-impersonation attempts this quarter, all caught' — because visible, blameless reporting is the metric of a healthy culture here. The dangerous quarter is the silent one: whaling attempts are continuous at most companies of any profile, so zero reports usually means zero detection, not zero attacks. DomainGuard's monitoring contributes the outside half of that visibility, flagging the lookalike domains built to wear your executives' names before the messages are ever written.
Five actions to take today
- Enforce DMARC at p=reject to eliminate exact-domain executive spoofing outright.
- Enable gateway flagging for external mail carrying executives' display names or near-match domains.
- Adopt and rehearse the out-of-band rule: money and credentials never move on emailed instruction alone.
- Have executives state publicly, to staff, that they will never ask anyone to skip verification.
- Log every detected attempt, feed its domain to blocklists and takedown, and report quarterly counts back to staff.
Worked example: Harbor Lane Accounting's three caught attempts
Harbor Lane Accounting, a fictional firm monitoring 6 domains, recorded 3 executive-impersonation attempts in one quarter. The first arrived from a lookalike registered 8 days earlier — flagged by its MX alert — and was recognised by the finance lead who had seen the warning. The second used the managing partner's display name on a free mailbox and was bannered by the gateway's display-name rule. The third, the best crafted, asked for a confidential client payment; the clerk verified by phone in 4 minutes and heard the partner, in a meeting next door, deny it entirely. Three different shapes, three different layers, zero payments — the outcome the layered model promises.
FAQ
Why does whaling use plain text with no links?
Because there is nothing for filters to catch and nothing for the victim to inspect except the instruction itself. The absence of technical payload is the technique; the defense is procedural, not scanning.
Should executives be exempt from verification rules for speed?
Never — that exemption is precisely the hole whaling exploits. Design a fast verification path for genuine urgency (a known number, a code word for true emergencies) rather than a bypass.
Can we stop display-name spoofing technically?
Gateways can banner or hold external mail whose display name matches internal executives, which covers most cases. The remainder is culture: staff checking the actual address on any consequential request.
What public information helps attackers most?
Leadership names and roles, email address formats, deal and expansion announcements, and executives' travel posts. You cannot hide a leadership team, but you can stop publishing its operational details.
An employee already complied. What now?
Move at banking speed: recall request immediately, preserve everything, notify insurers and law enforcement, and run the debrief blamelessly. The employee was the last layer to fail, not the only one — fix the layers above them.