TL;DR: Helpdesk impersonation can turn trust into access faster than organisations can verify it, according to Valimail. Recovery, support and federation workflows need tighter identity checks because attackers can use legitimate processes to drive resets, re-enrolment and privileged exceptions.
Editorial analysis by NHI Mgmt Group, based on content published by Valimail: “9 ways to protect yourself from social engineering attacks”.
Key questions
Q: Why do vishing and MFA fatigue still work against organisations with MFA?
A: They work because the attacker targets the human and the recovery process, not the MFA factor itself.
Q: How can security teams know whether social engineering defences are working?
A: Look for fewer successful impersonation attempts, fewer unauthorised resets, stronger reporting of suspicious requests and shorter time-to-containment when a deceptive message is reported.
Q: What breaks when social engineering is not governed as an identity risk?
A: When social engineering is treated as a user problem only, attackers can still drive password resets, MFA re-enrolment, payment approvals, and privileged exceptions through legitimate workflows.
Practitioner guidance
- Tighten help desk verification steps Require out-of-band confirmation, callback verification and step-up checks before any password reset, MFA reset or account recovery action.
- Harden email authentication controls Move domain authentication to enforced DMARC policies and monitor for spoofing patterns that could support phishing and brand impersonation.
- Reduce privilege on recovery and support roles Review who can approve identity changes, reset access or modify federation settings, then remove standing access that is not operationally necessary.
Bottom line: Social engineering succeeds when organisations allow trust to be converted into access faster than it can be verified.
Glossary terms: Social Engineering, Phishing, Helpdesk impersonation, Identity verification
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Social engineering is an identity governance failure before it is a human mistake. The central weakness is not that employees are careless, but that organisations still allow trust to be converted into access too easily. Recovery workflows, help desk resets and delegated approvals are all identity checkpoints, and when those checkpoints are weak the attacker does not need malware. Practitioners should treat social engineering as a governance design flaw, not an awareness-only problem.
A question worth separating out:
Q: What should organisations do when a suspicious social engineering request is detected?
A: Pause the transaction, verify the request through an independent channel, and preserve the details for follow-up investigation. If the request involves funds, access, or account recovery, treat it as a potential identity event and notify the relevant business owner before any action is taken.
👉 Read our full editorial: Social engineering exposes the limits of technical trust controls