Relevant detail with an unusual ask
The message references a real role, project, event, or contact but asks for an action outside the normal workflow.
Spear Phishing Awareness
How to Recognize and Report Spear Phishing
Spear phishing is a targeted phishing attempt tailored to a particular person, role, team, organization, or business relationship.
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
Spear Phishing: a practical definition
Spear phishing is a targeted phishing attempt tailored to a particular person, role, team, organization, or business relationship.
The attacker uses context to increase credibility. That context may be public, inferred, stolen, or obtained from a compromised account; accurate details do not prove the request is legitimate.
Source: CISA Phishing Guidance
02Recognition clues
Warning signs employees can check in a spear phishing 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.
Narrowly targeted urgency
The recipient is told they were selected, trusted, or required to act privately because of their specific position.
Plausible sender, changed destination
The relationship seems familiar, but the reply address, shared file, sign-in route, or payment instruction differs.
03Safe response
Move from suspicion to a supported next step
| Moment | Employee action | Program preparation |
|---|---|---|
| Before acting | Confirm the request through the known project owner, directory, application, or approval process rather than relying on the accurate personal or business details in the message. | 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
Spear Phishing 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.
Role-specific document
Use a fictional project and document that matches the audience's work while avoiding actual names, customers, or confidential details.
Conference invitation
Practice verifying an invented event request through the known calendar owner or public event route.
Privileged-team scenario
Use a separately approved exercise for administrators that reinforces the exact change and identity process they follow.
05Campaign workflow
Build the exercise around a decision employees can repeat
- 1
Define the behavior
Write down the spear phishing 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 spear phishing 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.
How is spear phishing different from bulk phishing?
Spear phishing is tailored to a specific audience or relationship, while bulk phishing is distributed more broadly. Both still require context-aware verification and reporting.
Should simulations use real employee details?
Use role-level, fictional context wherever possible. Relevance does not require private personal data, and any personalization should be approved, proportionate, and documented.
Can spear phishing 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 the minimum fictional context needed for relevance. Do not mine private employee data, imitate personal relationships, expose confidential projects, or target an individual for embarrassment.
How should spear phishing 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 spear phishing 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.