Help-desk impersonation: which verification drill should your service desk run, and should you test it in-house or hire an outside firm?
Quick answer, Nov 19, 2026As of 19 November 2026, treat a caller who wants a password reset and a new MFA device on one call as account recovery, not a routine ticket. CISA's Scattered Spider advisory describes callers posing as employees to get both. Drill one verification step with the help desk, then test it in-house or through a vetted outside assessor.
What the call looks like
CISA's joint advisory AA23-320A, last revised 29 July 2025, describes a group that "targets large companies and their contracted information technology (IT) help desks" ("Summary"). Its "Overview" lists, "According to public reporting", callers who "Posed as employees to convince IT and/or helpdesk staff to provide sensitive information, reset the employee's password, and transfer the employee's MFA to a device they control".
The calls are staged. Under "Reconnaissance, Resource Development, and Initial Access", the advisory says the first calls are "designed to first learn what steps are needed to conduct password resets from helpdesks". Later calls collect "password reset specific information of a targeted employee", and the attempts are "enriched by access to personal information derived from social media". A caller who knows an employee number and a manager's name has proved very little.
Training staff to spot deepfake impersonation covers the caller who reaches a payment approver. This page covers the caller who reaches the help desk. The prize there is an account, not a wire.
Six drills for the help desk
| Drill | What the help desk does | Where it is written |
|---|---|---|
| 1. A caller asks for a password reset and a new MFA device on one call | Handles it as account recovery under a written procedure, never as a courtesy | NIST SP 800-63B-4 (July 2025), section 4.2 "Account Recovery" and 4.2.1 "Account Recovery Methods" |
| 2. The caller knows personal details | Treats details anyone could research as no proof at all | AA23-320A, "Reconnaissance, Resource Development, and Initial Access" |
| 3. The account is privileged | Applies the strictest check to administrator accounts | NCSC, Incidents impacting retailers – recommendations from the NCSC (4 May 2025), "So what?" |
| 4. A new authenticator is bound | Tells the real user through a channel the caller does not control | SP 800-63B-4, section 4.1.2.1 "Binding an Additional Authenticator"; section 4.2.3 "Account Recovery Notification" |
| 5. "IT" calls an employee and asks them to install a remote access tool | Staff hang up and call the help desk on the number they already hold | AA23-320A, "Overview"; "Mitigations" (allowlisting remote access programs) |
| 6. A contracted provider runs your help desk | Asks the provider, in writing, how it verifies your staff before a reset | AA23-320A, Table 6 "Initial Access", T1199 "Trusted Relationship" |
For rows 2, 5 and 6, the cited passage describes the technique; the action is this page's reading of it. NCSC's "So what?" section tells organisations to "review helpdesk password reset processes, including how the helpdesk authenticates staff members credentials before resetting passwords, especially those with escalated privileges".
NIST names the weak point. SP 800-63B-4 section 6.3, "Authenticator Recovery", says it is "the process followed when a subscriber loses control of one or more authenticators", and that "To the extent that authenticator recovery is human-assisted, social engineering attacks also pose risks." Section 4.2 says "an account recovery event always causes one or more notifications to be sent to the subscriber". SP 800-63B-4 is written for credential service providers. Applying it to an internal help desk is this page's reading, not a NIST instruction.
AA23-320A's "Mitigations" recommends FIDO/WebAuthn or PKI-based MFA, "not susceptible to push bombing or SIM swap attacks". The same section adds: "Organizations should continue to perform diligent employee training against vishing and spearphishing."
Drill it in-house, or hire an outside tester?
| Option | What it tests | What to check first | Where it is written |
|---|---|---|---|
| In-house tabletop or simulated vishing call | Whether staff know the procedure | Whether you have the subject-matter expertise and the time | NIST SP 800-50r1 (September 2024), section 2.7.2 "Experiential Learning"; section 2.10.1 "Establishing a CPLP Budget" |
| Outside social-engineering test | Whether the procedure holds when a stranger calls | Vetting, a signed assessment plan, and who handles the data | NIST SP 800-115 (September 2008), section 5.3 "Social Engineering"; section 6.4.1 "Assessor Selection and Skills"; section 6.5 "Assessment Plan Development" |
| Testing against the advisory's techniques | Whether controls catch the calls the advisory maps | Which ATT&CK technique to start with | AA23-320A, "Validate Security Controls" |
SP 800-50r1 section 2.10.1, "Establishing a CPLP Budget", lists example questions for planning the budget, including "Is it more cost-effective to develop the material in-house versus outsourcing?" and "Does the organization have the subject-matter expertise to provide content for the training?"
SP 800-115 names this exact test. Section 5.2, "Penetration Testing", gives the example of "calling the help desk posing as a user and asking for a password to be reset". Table 5-1 in section 5.4, "Summary", says social engineering "allows testing of both procedures and the human element". Section 5.3 says its results should be used "to improve the security of the organization and not to single out individuals". The final report should identify "both successful and unsuccessful tactics used".
Section 6.4.1 says that in some cases third parties offer "an independent view and approach that internal assessors may not be able to provide". They "should be properly vetted". Section 6.5 says each assessment should be addressed in an assessment plan "regardless of the scope, level of intrusiveness, or party performing the test (i.e., internal, third party)". Section 7.2, "Assessing", adds that many organisations run "occasional unannounced assessments to supplement their announced assessments".
The order that follows: write the procedure, drill it in-house, then have someone who has never met the help desk call it.
Before you book a tester
Will they script calls around your real reset process, including any contracted help desk? Will the plan be signed before the first call? Will the report name tactics and gaps, not people?
If your provider runs the help desk, the third-party questions are in third-party risk after a provider-led breach. To rehearse the response, see which exercise to run; for who sits in a tabletop room, see the developer-tool tabletop. For a drill, a social-engineering test of your help desk, or a response firm on retainer, brief an advisor and we arrange a partner firm.
Questions
Does phishing-resistant MFA make this drill unnecessary? No. AA23-320A says FIDO/WebAuthn and PKI-based MFA resist push bombing and SIM swaps ("Mitigations"). The help desk still decides who gets a new authenticator, which is the step the advisory's callers aim for.
Will a test stop the next caller? No test guarantees that. SP 800-115 section 5.3 frames the result as a report of what worked and what did not. Closing the gaps is a separate decision.
Is this legal advice? No. This page is a procedural guide drawn from the public record. Counsel decides what your contracts and your regulator require.