Unrequested support contact
A technician reaches out about a problem the employee did not report or a device alert they cannot independently confirm.
Tech Support Phishing Awareness
How to Recognize and Report Tech Support Phishing
Tech support phishing impersonates an internal or external support provider to obtain credentials, codes, remote access, software installation, payment, or sensitive device information.
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
Tech Support Phishing: a practical definition
Tech support phishing impersonates an internal or external support provider to obtain credentials, codes, remote access, software installation, payment, or sensitive device information.
The message may reference real technology or an ordinary support task. The durable control is a known service-desk route and an understood support process.
Source: CISA Phishing Guidance
02Recognition clues
Warning signs employees can check in a tech support 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.
Secrets or approvals requested
The person asks for a password, MFA code, recovery secret, repeated approval, or security-control exception.
Unfamiliar remote tool
The employee is directed to install software, share a screen, or allow remote control outside the approved support workflow.
03Safe response
Move from suspicion to a supported next step
| Moment | Employee action | Program preparation |
|---|---|---|
| Before acting | End the unexpected interaction and contact the known service desk through the company portal, directory, or saved support channel. | 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
Tech Support 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.
Support-ticket notice
Use an invented ticket and ask employees to check it through the authentic service portal.
Remote-access tabletop
Discuss how to respond when a caller requests an unfamiliar remote-control tool.
MFA support request
Practice rejecting a request to share a code or approve a sign-in for a supposed technician.
05Campaign workflow
Build the exercise around a decision employees can repeat
- 1
Define the behavior
Write down the tech support 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 tech support 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 can employees identify real IT support?
Publish the official contact routes and explain how support identifies itself and requests access. Employees should be able to reconnect through that known process.
Should support ever ask for a password?
Employees should follow organizational policy, but legitimate support should not require them to disclose a password or authentication code through an unexpected contact.
Can tech support 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. Do not install software, initiate remote access, generate authentication prompts, change device settings, or collect credentials and device data during the exercise.
How should tech support 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 tech support 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.