Topic starter
11/07/2026 1:55 pm
TL;DR: Identity verification platforms now have to be measured against synthetic media and capture-layer abuse, not legacy fraud assumptions, according to Incode. The company says its identity verification platform met government-defined goals in DHS S&T’s RIVR Track 2 for liveness detection, document verification, and injection attack resistance, a controlled test focused on deepfakes, fraudulent documents, and bypass attempts.
Editorial analysis by NHI Mgmt Group, based on content published by Incode: “Incode Ranks Among Top Performers in DHS S&T RIVR Track 2 Document Validation”.
Key questions
Q: Why do deepfake and injection attacks create such a high risk for identity verification programmes?
A: They create risk because they attack different points in the identity flow and defeat single control assumptions.
Q: Why do synthetic media and capture bypass methods create more risk for IDV?
A: They reduce the cost of presenting convincing evidence while increasing the attacker’s ability to automate attempts at scale.
Q: What are the signs that identity verification is failing as a control?
A: Common signs include onboarding exceptions, repeated manual overrides, inconsistent document checks, service desk approvals without revalidation, and fraud cases discovered after access has already been granted.
Practitioner guidance
- Test against synthetic media and replay Build evaluation cases for 2D spoofs, 3D artifacts, video replays, and tampered documents so your acceptance criteria reflect current fraud tooling rather than historical spoof patterns.
- Harden the capture path Review whether your IDV workflow can detect injected imagery or substituted streams before model scoring begins, then require controls that validate source integrity as part of the session.
- Define assurance thresholds for regulated onboarding Set explicit pass-fail criteria for liveness, document verification, and injection resistance so procurement and risk teams can compare platforms against the same threat model.
Bottom line: Identity verification now has to withstand active adversarial input, not just compare documents and faces.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/07/2026 2:06 pm
Remote IDV now has a capture-integrity problem, not just a matching problem. The article shows why conventional document and face checks are no longer sufficient when attackers can generate believable inputs or insert them into the stream. The meaningful control question is whether the verification path can prove the signal came from a real, live, untampered capture session. Practitioners should treat that as a governance requirement, not a model tuning issue.
A question worth separating out:
Q: How should businesses detect deepfake fraud in remote onboarding and authentication flows?
A: Businesses should combine liveness checks, AI-based anomaly detection, and step-up verification for high-risk actions. Deepfakes are designed to defeat human judgment, so controls must look for manipulated image artifacts, duplicate identities, and suspicious behavioral patterns. The most effective approach is layered: verify identity, validate session risk, and require stronger checks when confidence drops or the transaction is unusually sensitive.
👉 Read our full editorial: Identity verification under AI attack: what RIVR Track 2 showed