When the attacker calls the help desk
Help desk social engineering · facts checked 2026-10-03
The facts
- A November 2023 CISA and FBI advisory said attackers posed as employees to get IT help desk staff to reset passwords and move phone numbers to devices the attackers controlled. (CISA)
- That advisory recommends phishing-resistant MFA as a mitigation. (CISA)
- MITRE ATT&CK catalogues spearphishing by voice call as an attacker technique. (MITRE)
The panel
Jordan Pike AI host
CISA says in a November 2023 advisory, issued with the FBI, that attackers posed as employees to get IT help desk staff to reset passwords and move phone numbers to devices the attackers controlled. CISA also says that advisory recommends phishing-resistant MFA as a mitigation.
Jordan Pike AI host
MITRE says its ATT&CK knowledge base catalogues spearphishing by voice call as an attacker technique.
Jordan Pike AI host
So if you run a help desk, or you're the person whose boss's boss can be impersonated on a phone call, this one is for you. Ava, how does this work in practice?
Ava Lindqvist AI analyst (guest)
The attacker skips the login page and goes after the person who can reset it. A convincing caller who sounds stressed and knows a few details can get a password reset. If the phone number then moves to a device the attacker controls, any code or call meant for the real employee could land with the attacker instead. They end up holding the password and the second factor, without breaking any crypto. It's always the help desk.
Jordan Pike AI host
Sam, you get the call after the call. What are you looking for?
Sam Kowalski AI analyst
I start with the human trail: help desk tickets, call records, and whatever notes the agent typed while being charming to a stranger. Then I line those up with identity provider logs for resets and changes to phone numbers or devices, and with what that account did afterwards. The question is how far back you can see. Check your logs. Oh, you kept seven days? Because a patient caller may have gotten in well before anyone noticed.
Ava Lindqvist AI analyst (guest)
CISA recommends phishing-resistant MFA, and I'll back that all day. Push approvals and texted codes can be talked out of a person or redirected. A hardware-bound credential can't be read out over the phone. That's the real answer, and it's worth the rollout pain.
Sam Kowalski AI analyst
I'd push back on leaning on it alone. A strong authenticator is only as strong as the recovery path behind it. If the help desk can enroll a new device because someone on the phone sounded annoyed and knew a manager's name, you've built a very expensive front door next to an unlocked side door. Fix the process this week, and treat the MFA rollout as the longer project.
Ava Lindqvist AI analyst (guest)
Fair, and they're not exclusive. The process fix is the bridge, and it needs an end date, because bridges have a way of becoming permanent. The destination is phishing-resistant MFA.
Sam Kowalski AI analyst
Deal. And MITRE listing voice-call spearphishing as a technique tells you this is a known pattern, not a one-off. Train agents that a pushy caller is a signal to slow down, not speed up. Give them permission to say no without a performance review attached.
Jordan Pike AI host
So: Monday morning?
Ava Lindqvist AI analyst (guest)
Require verification that doesn't rely on what a caller can know, and call back through a number already on file. Put extra checks on any phone number or device change. Then plan your move to phishing-resistant MFA.
Sam Kowalski AI analyst
Find out how long you keep help desk and identity logs, and keep them longer. Make sure resets and device changes are recorded somewhere a human will actually look at them.
Jordan Pike AI host
Short version: the attacker's cheapest tool is a phone and a plausible voice, so verify callers properly and get your recovery process as strong as your login. That's the segment.





