Topic starter
09/06/2026 11:48 pm
TL;DR: AI-generated deepfakes and virtual camera injection are turning video calls into a fraud entry point for hiring, onboarding, account recovery, and financial approvals, according to iProov. The core issue is not video quality but the assumption that a face on screen proves identity, which no longer holds in high-risk workflows.
Editorial analysis by NHI Mgmt Group, based on content published by iProov: “iProov Announces iProov Verified Meetings to Tackle Deepfake Risks in Video Calls”.
Key questions
Q: How should security teams handle identity verification in high-risk video calls?
A: Security teams should treat high-risk video calls as identity checkpoints, not just collaboration sessions.
Q: Why do deepfakes create such a problem for video-based approval processes?
A: Because they exploit a control assumption that was never designed for synthetic media.
Q: What breaks when video calls are used to confirm identity without additional assurance?
A: The workflow confuses presence with authenticity.
Practitioner guidance
- Map video-based trust points Identify where meetings are used to approve hiring, onboarding, account recovery, or financial actions, then classify each as a controlled identity decision point rather than a collaboration event.
- Add pre-join authentication checks Require authenticity checks before a participant can influence a high-risk workflow, especially where the host has authority to grant money, access, or employment decisions.
- Separate visual presence from identity assurance Update approval procedures so that a visible face on screen is never treated as sufficient proof of the person behind the session.
Bottom line: Video calls are becoming identity checkpoints in workflows that can trigger hiring, onboarding, account recovery, and payments.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
10/06/2026 2:18 am
Video identity trust has become an access-control problem, not a collaboration problem. The old assumption was that visual presence in a meeting implied a real person behind the screen. Deepfakes, virtual cameras, and AI-assisted impersonation have broken that premise, so the control boundary now sits inside the meeting workflow itself. IAM teams should treat video as part of the identity assurance chain, not as a separate communications layer.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- Another finding shows that 97% of NHIs carry excessive privileges, which broadens the attack surface when identity checks are weak.
A question worth separating out:
Q: How do you know if video identity verification is actually working?
A: You know it is working when high-risk decisions are consistently preceded by an explicit identity check and when virtual camera or deepfake attempts are flagged before approval. Measure whether the control is embedded in the workflow, how often it is triggered for sensitive cases, and whether suspicious sessions are escalated instead of accepted.
👉 Read our full editorial: Video call identity verification is becoming an IAM control
11/06/2026 1:18 am
Video identity trust has become an access-control problem, not a collaboration problem. The old assumption was that visual presence in a meeting implied a real person behind the screen. Deepfakes, virtual cameras, and AI-assisted impersonation have broken that premise, so the control boundary now sits inside the meeting workflow itself. IAM teams should treat video as part of the identity assurance chain, not as a separate communications layer.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- Another finding shows that 97% of NHIs carry excessive privileges, which broadens the attack surface when identity checks are weak.
A question worth separating out:
Q: How do you know if video identity verification is actually working?
A: You know it is working when high-risk decisions are consistently preceded by an explicit identity check and when virtual camera or deepfake attempts are flagged before approval. Measure whether the control is embedded in the workflow, how often it is triggered for sensitive cases, and whether suspicious sessions are escalated instead of accepted.
👉 Read our full editorial: Video call identity verification is becoming an IAM control
12/06/2026 2:53 am
Video identity now functions as an IAM control, not a communications convenience. Once hiring, onboarding, recovery, and approvals rely on video interactions, the meeting becomes part of the trust decision itself. That shifts governance from audiovisual quality to identity assurance, and practitioners should treat the pre-join step as a control boundary.
A question worth separating out:
Q: What should teams do when a host receives an amber or red authenticity result?
A: They should stop the workflow, move the interaction to a verified channel, and require stronger proof before any sensitive action continues. The result should be tied to the approval record so that exceptions are auditable. That prevents a risky session from silently becoming a trusted transaction.
👉 Read our full editorial: Video call identity verification is becoming an IAM control
This post was modified 2 days ago by NHI Mgmt Group