TL;DR: Only 7% of organizations are more than moderately prepared to detect or prevent AI-powered fraud, Trusona and the ACFE and SAS Anti-Fraud Technology Benchmarking Report says. Identity verification has to do more than spot patterns after the fact when attackers can impersonate people in real time.
Editorial analysis by NHI Mgmt Group, based on content published by Trusona: “Only 7% of organizations are ready for AI-powered fraud. Here's what the other 93% are missing.”.
By the numbers:
- Only 7% of organizations say they are more than moderately prepared to detect or prevent AI-powered fraud.
Key questions
Q: Why do AI-powered fraud programmes need IAM and fraud teams to work together?
A: Because the attack often happens at the identity decision, while the fraud team may only see the outcome later.
Q: How do organisations know whether identity reset controls are actually stopping impersonators?
A: Organisations should look for a lower rate of risky resets reaching approval, fewer MFA re-registrations from unusual devices, and better separation between normal employee behavior and anomalous requests.
Q: What breaks when organizations rely on knowledge-based verification for AI-powered fraud?
A: Knowledge-based verification breaks because the answers are often guessable, breached, or publicly available, especially when attackers use AI to sound convincing in real time.
Practitioner guidance
- Replace knowledge-based verification Remove security questions, partial personal data checks, and other memory-based methods from high-risk reset and account-change workflows because they can be sourced or guessed.
- Bind verification to live transactions Require proofing methods that tie the person, device, and request together so a copied code, forwarded link, or replayed session cannot satisfy the process.
- Harden help-desk approval paths Separate routine support from privileged actions such as MFA bypasses, password resets, and recovery changes, with stricter approval for identity recovery events.
Bottom line: AI-powered fraud is increasingly an identity verification problem because attackers succeed when they impersonate a real person at the moment a request is made.
Glossary terms: Impersonation Detection, Activation Trust Gap, Live Identity Proofing, Transaction binding
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Identity impersonation is now the primary control problem in AI-powered fraud. The article shows that organisations are trying to detect fraud faster while attackers are winning the verification step itself. That shifts the governance question from signal quality to proof of personhood, especially in service desk and call-centre workflows. Practitioners should treat identity verification as a live control plane, not an administrative formality.
A few things that frame the scale:
- U.S. fraud losses are projected to reach $40 billion by 2027.
A question worth separating out:
A: Yes. If identity fraud is occurring at the front door, stronger identity verification should come before broader blocking tactics because it improves trust without automatically adding friction everywhere else. The best approach is layered: verify identity earlier, use risk-based controls for exceptions, and reserve hard blocks for clear abuse. That reduces false positives while addressing the source of the problem.
👉 Read our full editorial: AI-powered fraud readiness lags because identity impersonation wins