Help Desk Impersonation
Your help desk needs the authority to say no to you.
What Is Help Desk Impersonation?
Executive accounts are the most valuable to impersonate, and what a caller needs to sound like a leader is usually public. As a COO whose MFA was reset overnight by someone posing as you, you trace where each detail in the help desk ticket came from, judge which checks prove identity, remove the attacker's authenticator and re-enrol through Security. Then you decide a stricter executive verification policy and sign the clause that backs agents who refuse you.
What You'll Learn in Help Desk Impersonation
- Explain why executive accounts are prime targets for help desk impersonation
- Distinguish facts a caller can look up from checks that prove identity, such as a call-back to the number on file
- Respond to an unauthorised MFA reset: report it, remove the unknown method and re-enrol through a verified channel
- Choose executive verification policy clauses that resist impersonation and reject fast-track exceptions
- Give the help desk written authority to refuse senior staff, and respect it when it applies to you
Help Desk Impersonation — Training Steps
-
The Call About You
It is Wednesday morning. Alice is Chief Operating Officer at Halverick Brewing and has just landed back in Leeds from a trade fair in Lisbon. She slept through the night. Someone else spent part of it being her, on the phone to the IT help desk.
-
Open the Ticket
Every help desk call leaves a ticket. This one records exactly what the agent heard and what he accepted as proof.
-
How the Caller Sounded Like You
The caller had done some homework, which is how most vishing starts. Nothing they said was secret; it only sounded that way to an agent on a night shift.
-
Fourteen Minutes
From the first ring to a working authenticator on the caller's phone took fourteen minutes. The only thing that stopped the sign-in was a rule about where Alice had been.
-
Review the Agent's Checks
Security wants the COO's own judgement on the ticket. Mark each check by whether it actually proves who is calling. The page marks the ones you get wrong without saying what they should be.
-
The Two Checks That Were Skipped
The runbook already had the answer. The agent skipped it because the caller was senior and in a hurry, and nobody had told him he was allowed to say no to a COO. Social engineering works by making the rule feel like the obstacle.
-
Check Your Own Sign-ins
Alice's account still has the attacker's phone registered as its second factor. That comes first.
-
It Was Not You
The blocked sign-in is listed with a question. Security needs Alice's answer on record, because only she knows where she was.
-
Remove the Caller's Authenticator
The method added at 23:52 lives on a phone Alice has never held. While it is on her account as an MFA method, the attacker can approve sign-ins as her.
Security Framework Coverage
CIS Controls
- CIS 14.1 Establish and Maintain a Security Awareness Program
- CIS 6 Access Control Management
NIST CSF
- PR.AT-01 Personnel are provided with awareness and training so that they possess the knowledge and skills to perform general tasks with cybersecurity risks in mind
- PR.AA Identity Management, Authentication, and Access Control