TL;DR: Support-layer identity proofing is the weak point Trusona highlights, because MGM Resorts’ 2023 breach showed how reset workflows can turn impersonation into access. Recovery steps need stronger verification, separation and logging when every password or MFA change can become a takeover event.
Editorial analysis by NHI Mgmt Group, based on content published by Trusona: “Prevent the Next $100M MGM-Style Breach”.
By the numbers:
- The MGM Resorts breach cost the company roughly US$100 million.
Key questions
Q: Why do social engineering attacks still bypass strong MFA programs?
A: Strong MFA can still fail if attackers can reset the factor through support channels or exhaust users with push prompts.
Q: What are the warning signs that account recovery is becoming a takeover path?
A: Repeated reset requests, urgent caller behaviour, requests involving device loss or number changes, and resets for high-value users are all signals that recovery is being targeted.
Q: What breaks when help desk recovery uses security questions and uniform reset scripts?
A: Recovery becomes the weakest authentication path in the environment.
Practitioner guidance
- Harden identity proofing for account recovery Require recovery steps that verify the caller through stronger evidence than security questions, especially for privileged and high-risk accounts.
- Separate privileged recovery workflows Use stricter approval, callback, or multi-party validation for administrators, finance users, and other sensitive identities instead of one common reset script.
- Log and review every password and MFA change Track who requested the reset, which agent approved it, the channel used, and whether the change matched expected access patterns.
Bottom line: Help desk social engineering can bypass MFA by attacking recovery workflows rather than the authentication protocol itself.
Glossary terms: Help Desk Social Engineering, Recovery Path, Phishing-Resistant MFA, Support-Layer Identity Proofing
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Support-layer identity proofing is now part of the authentication boundary. The MGM-style breach pattern shows that organisations are not only authenticating users at login, they are authenticating them again whenever a help desk resets credentials or MFA. That means the recovery flow is a privileged identity event with its own assurance requirements. Practitioners should treat help desk verification as an access control, not an admin convenience.
A question worth separating out:
Q: How should organisations structure help desk controls for privileged accounts?
A: They should require stronger proofing, secondary approval, and separate recovery steps for privileged identities rather than applying the same script to every user. Privileged recovery should be treated as a PAM-adjacent control because a bad reset can instantly create high-impact access. The question is not speed alone, but whether the workflow matches the account’s risk.
👉 Read our full editorial: Help desk social engineering bypasses MFA in MGM-style breaches