Before anyone resets a password over the phone
Some of the most damaging attacks of recent years started with a phone call to a helpdesk. The caller sounded like an employee, knew a few details, and asked for a reset.
The 2023 attack on MGM Resorts began with a phone call to the IT service desk. The caller impersonated an employee, using details found on LinkedIn, and asked for help with their account. The same approach has been used repeatedly since, against retailers, insurers and the outsourced helpdesks that serve them.
No technical control was bypassed. The helpdesk did what helpdesks are for.
Why it works
Helpdesk staff are measured on resolving problems quickly, and a distressed caller who is locked out before a client meeting is exactly the problem they exist to solve. Name, job title, manager and staff ID are easy to find or guess. If those are the verification questions, they verify nothing.
A password reset alone is often not enough for an attacker, because the account still has MFA. So the request is usually for both: a new password and the old authenticator removed, because the caller has a new phone.
What verification should look like
Call the person back on the phone number in the HR record or the directory, never the number they are calling from. Or confirm through a second channel the attacker does not control: a Teams message to the manager, who checks with the person directly.
For MFA resets, the bar should be higher than for passwords. Removing someone's authenticator is the step that actually hands over the account, so it should need either the call-back or a manager's confirmation, every time, including for senior staff in a hurry. Senior staff are the people attackers most often impersonate.
Instead of reading a new password over the phone, issue a Temporary Access Pass that expires within hours and makes the person register a fresh authenticator. Then check the sign-in log for that account over the next day.
Fewer calls in the first place
Self-service password reset, with MFA required to use it, removes most of the routine reset calls. The calls that remain are the unusual ones, which is when a helpdesk should be slowing down.
Ask your provider
If your IT is outsourced, ask what they check before resetting a password or MFA method on one of your accounts, and whether it is written down. It is a fair question, and the answer should be specific. Ours is a call-back to the number on record, plus manager confirmation for any MFA change.
Microsoft also offers Verified ID with Face Check, which matches the caller against a photo ID. It is a sound control for large helpdesks. For a 30-person business, a written call-back rule that everyone follows achieves most of the same thing at no cost.