TL;DR: Deepfakes and AI agents are exposing the limits of one-time login checks, because static authentication points no longer capture trust changes across a customer journey, according to Prove Identity. Continuous identity verification shifts fraud and identity decisions to ongoing signal evaluation rather than a single gate.
Editorial analysis by NHI Mgmt Group, based on content published by Prove Identity: “Deepfakes, AI Agents, and the Collapse of Traditional Identity Security”.
Key questions
Q: What breaks when identity assurance stops at the human login flow?
A: The programme misses delegated and downstream access paths.
Q: Why do deepfakes make traditional authentication weaker?
A: Deepfakes weaken traditional authentication because they imitate the human signals that many approval processes still trust, including voice and video.
Q: How should teams decide which trust signals matter in continuous verification?
A: Teams should prioritise signals that change quickly, are hard for attackers to fake, and correlate with real risk in their own environment.
Practitioner guidance
- Redesign identity assurance around the full journey Map the points after login where trust can change, including device shifts, transaction changes, and unusual interaction patterns.
- Define continuous risk signals for customer identity Select the behavioural and contextual signals that are actually predictive in your environment, then document which combinations trigger step-up or denial.
- Separate entry authentication from ongoing trust Review policies that assume a passed login equals a trusted session.
Bottom line: One-time login checks no longer capture the full identity risk picture once sessions, devices, and transaction context can change after entry.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
One-time identity checks now represent a governance assumption, not a control boundary. They assume the trust decision made at login remains valid for the full customer journey. That assumption fails when identity proof can be spoofed, replayed, or socially engineered after entry. The implication is that identity assurance must be managed as a continuous state, not a single event.
A few things that frame the scale:
- Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How do IAM and fraud teams work better together on identity proofing?
A: They need shared policy for evidence quality, risk scoring and escalation. IAM controls decide what access is granted, while fraud controls surface suspicious patterns before or after issuance. When those teams operate separately, weak proofing can look compliant even while fraud risk is increasing.
👉 Read our full editorial: Continuous identity verification is replacing one-time login checks