TL;DR: Phishing, stolen passwords, and account recovery abuse are converging with generative AI to make authentication attacks easier and more effective, according to Axiad and the cited Verizon and FIDO findings. Passwordless and phishing-resistant MFA help, but recovery workflows are now the softer target.
Editorial analysis by NHI Mgmt Group, based on content published by Axiad: “Three Authentication Predictions for 2024”.
By the numbers:
- Passwords are the root cause of 80% of data breaches, according to the FIDO Alliance cited by Axiad.
Key questions
Q: How should organisations implement passwordless IAM without weakening recovery controls?
A: Treat passwordless as an assurance program, not a user-experience feature.
Q: Why do passwordless programmes still get compromised through recovery paths?
A: Because passwordless improves the login step, not every way identity is re-established.
Q: What are the signs that account recovery is the weakest part of authentication?
A: Common signs include heavy help-desk involvement, reliance on knowledge-based questions, inconsistent verification steps, and recovery channels that differ from primary authentication policy.
Practitioner guidance
- Strengthen account recovery assurance Require recovery methods that match the assurance level of the primary authentication policy and remove low-trust fallback paths such as easily guessed knowledge questions.
- Redesign help desk verification Limit support-agent discretion in reset workflows and replace informal verification steps with auditable, policy-driven recovery checks.
- Harden phishing-resistant MFA Use phishing-resistant MFA for primary sign-in so recovery abuse cannot be paired with weak login controls to complete account takeover.
Bottom line: The core problem is no longer just stolen passwords, but weaker recovery paths that can bypass stronger sign-in controls.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Account recovery is now part of the authentication perimeter: Passwordless adoption does not eliminate authentication risk; it relocates it. The organisation still has to prove identity when users lose access, and that proving step is often weaker than the login step it replaces. The implication is that IAM governance must treat reset, recovery, and help-desk approval as first-class authentication controls, not operational exceptions.
A question worth separating out:
Q: How should organisations adapt security awareness training for generative AI phishing?
A: Security teams should move from static annual training to continuous, behaviour-focused reinforcement. Use short exercises, phishing simulations, reporting drills, and manager-supported reminders that train employees to verify requests through a second channel. The goal is not perfect detection of every message. It is faster hesitation, better escalation, and fewer successful credential captures.
👉 Read our full editorial: Authentication is shifting from passwords to recovery attack paths