Executive social engineering exploits authority, urgency and knowledge of business relationships. An attacker may impersonate a leader or target that leader's assistants and advisers. Protect the decision process: verify unusual requests through a trusted independent channel before changing payments, releasing confidential material or granting account access.
01
Recognize the pressure pattern
A request may refer to a real meeting, acquisition rumor or supplier to sound credible. NIST's phishing guidance emphasizes verifying suspicious communications rather than trusting appearance alone. A message becomes especially concerning when it demands secrecy, bypasses normal approval or asks the recipient to use a new contact route immediately.
02
Build verification into routine operations
Agree on how the team confirms sensitive instructions when a leader is traveling or unavailable. Use existing directory details, established approval systems and a second responsible person where appropriate. Do not make assistants decide whether a voice sounds convincing enough. A process should still work when an attacker knows the executive's schedule and writing style.
- Verify changes to payment details outside the requesting message.
- Never share recovery codes or approve unexplained access prompts.
- Keep sensitive itineraries and personal contacts out of public posts.
- Give staff a clear way to pause suspicious instructions.
03
Example of a confidential document request
Someone posing as a director asks an assistant to send a confidential file to a new adviser before a meeting. The assistant checks through the existing internal channel and confirms the adviser's authorization. If verification fails, the file stays restricted. This protects the organization without requiring the assistant to accuse the apparent sender of fraud.
Frequently asked questions
Is a familiar voice enough to authorize a transfer?
No. Voices, accounts and contextual details can be imitated or compromised. Follow the established approval procedure, especially when the request changes payment or access arrangements.
Should leaders be exempt from verification rules?
No. Exceptions based on seniority create exactly the shortcut an impersonator wants. Leaders should support staff who follow the process and document legitimate emergency alternatives in advance.
Continue with your next step
Related guides on this topic
Sources and policies
Check the current policy before submitting a request.
You do not have to figure out the next step alone.
Share the URLs and explain your concern. We will review the context and explain which options are worth assessing.
Request a confidential reviewOr call (307) 429-2531Educational information, not legal advice. Outcomes depend on the facts and decisions made by third parties.