Topic starter
06/11/2026 6:40 pm
TL;DR: Deepfake risk in identity verification is driven less by whether a fake can be spotted than by whether presentation and injection attacks can be stopped at the point of introduction, according to Daon. NHI Mgmt Group’s view is that detection-only procurement leaves the real trust failure unaddressed.
Editorial analysis by NHI Mgmt Group, based on content published by Daon: “Deepfake Defense Starts Before Detection: Here’s What to Take Away from the Latest Gartner Report”.
Key questions
A: Use multi-layer detection that evaluates face, device, camera, and behavior signals together, rather than relying on a single liveness check.
A: Teams should treat face biometric defence as a two layer problem.
Q: What should teams do first when deepfake fraud is targeting identity verification?
A: Start with the highest-risk recovery and escalation paths, because those flows often accept weaker proof than initial login.
Practitioner guidance
- Define separate test cases for presentation and injection attacks Assess whether the verification stack can withstand camera-facing artefacts and stream-bypass manipulation as distinct control failures.
- Require independent PAD and IAD evidence before procurement Make ISO/IEC 30107-3 testing and injection attack validation part of acceptance criteria, with no contract award on unverified accuracy claims.
- Add contextual risk signals to every remote verification flow Use device, location, velocity, and interaction signals to challenge suspicious enrolment or login events even when the biometric check appears clean.
Bottom line: Deepfake defence fails when teams focus on content recognition instead of the full identity workflow that admits the content.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
Deepfake defence is a verification governance problem, not a detection race. The control failure is usually not that the organisation lacks an AI model capable of spotting synthetic content. The failure is that it has not governed the identity path well enough to stop fraudulent media from entering the process in the first place. That means assurance belongs in capture integrity, channel integrity, and contextual decisioning, not only in model scoring. The practitioner conclusion is to treat deepfake resistance as an identity workflow control, not a standalone security feature.
A question worth separating out:
Q: What should teams do first when deepfake fraud is targeting identity verification?
A: Start with the highest-risk recovery and escalation paths, because those flows often accept weaker proof than initial login. Remove knowledge-based prompts, review call-centre scripts, and require stronger step-up checks wherever an attacker could socially engineer a support agent into resetting access.
👉 Read our full editorial: Deepfake defence depends on verification controls, not detection claims