Identity and request do not fit
The claimed person or organization makes a request outside the usual role, timing, channel, or relationship.
Impersonation Attacks Awareness
How to Recognize and Report Impersonation Attacks
An impersonation attack presents the attacker as a trusted person or organization to obtain information, money, access, or another action.
Use this guide to turn the threat into a clear employee decision, a safe practice scenario, and a reporting step your organization can support.
Plain-English definition • Warning signs • Safe simulation ideas • Reporting practice
01Understand the threat
Impersonation Attacks: a practical definition
An impersonation attack presents the attacker as a trusted person or organization to obtain information, money, access, or another action.
Impersonation can occur through email, calls, chat, text, video, websites, and documents. A familiar name, logo, voice, or account is a cue—not complete authorization.
Source: CISA Phishing Guidance
02Recognition clues
Warning signs employees can check in a impersonation attacks message
No single clue proves that a message is malicious. Teach employees to combine the request, sender, business context, destination, and available verification route before acting.
Verification is discouraged
The requester pushes secrecy, urgency, or a new contact method and resists normal confirmation.
Authority is asserted, not demonstrated
The message relies on a title, brand, or personal detail but does not follow the required business process.
03Safe response
Move from suspicion to a supported next step
| Moment | Employee action | Program preparation |
|---|---|---|
| Before acting | Confirm the person's identity, authority, and business purpose through the known directory, account owner, or approved workflow. | Publish the authentic contact, application, or reporting route somewhere employees can reach without using the message. |
| When uncertain | Pause the request and report it through the approved channel with enough context for review. | Explain what the response team needs and how employees will know that their report was received. |
| After an interaction | Stop, contact the responsible team promptly, and describe the action taken without hiding the mistake. | Provide a well-known response route and avoid communications that discourage early reporting. |
Source: NIST: Recognizing, verifying, and reporting phishing
04Practice safely
Impersonation Attacks simulation and discussion ideas
Choose one learning objective per exercise. Use fictional people, organizations, accounts, payments, documents, and events, and test the reporting route before sending to employees.
Colleague request
Use a fictional employee identity to practice checking an unexpected access or document request.
Customer identity
Discuss how support staff follow the established customer-verification process without using real customer records.
Service-provider notice
Ask employees to open the known service rather than act through an unexpected branded message.
05Campaign workflow
Build the exercise around a decision employees can repeat
- 1
Define the behavior
Write down the impersonation attacks clue being practiced, the expected action, the authorized audience, and the owner of follow-up.
- 2
Confirm the real process
Test the independent verification route, message-reporting option, response handoff, and employee support path from a representative account.
- 3
Pilot the scenario
Check delivery, links, landing content, accessibility, event records, automated inspection, stop conditions, and the explanation employees will receive.
- 4
Review in context
Reconcile intended recipients, successful deliveries, unique employee events, verified reports, response handling, and completed follow-up before drawing conclusions.
Source: NIST SP 800-50 Rev. 1: Building a Cybersecurity and Privacy Learning Program
06Useful measurement
Evaluate recognition, reporting, and the surrounding process
Record actual counts and denominators for delivery, unique recipient events, reports, and follow-up. Separate automated email inspection and repeat events where the available evidence supports doing so.
A impersonation attacks exercise samples one scenario under one set of conditions. It does not establish an employee's intent, overall security awareness, or likelihood of responding the same way to a real attack.
Use findings to improve the real workflow: clearer verification instructions, easier reporting, faster response handling, better role-specific training, or a business control that reduces reliance on email alone.
Common questions
Common questions about Phishmake's features, onboarding, and support, answered to help you get started with confidence.
What should employees verify?
Verify who is making the request, whether they have authority for it, and whether the stated business purpose matches a known workflow.
Is a known account enough proof?
No. Accounts can be compromised and visible identity details can be copied. Consequential requests should follow the established verification and approval process.
Can impersonation attacks be used in a phishing simulation?
It can be practiced when the scenario is authorized, proportionate, and tied to a real reporting or verification process. Use fictional or explicitly approved identities. Avoid personal crises, disciplinary messages, customer emergencies, public authorities, or scenarios that could damage a real relationship.
How should impersonation attacks simulation results be measured?
Review successful delivery, unique employee events, reports, response handling, and completed follow-up. Include scenario difficulty and operating context, and do not treat a click or report as a complete measure of employee risk.
Sources & further reading
Published by Phishmake · Updated
Keep building your program
All resourcesPut it into practice
Turn impersonation attacks awareness into a repeatable response.
Use Phishmake to run controlled employee simulations, review campaign activity, assign relevant training, and keep follow-up records in one workflow.