Topic starter
24/06/2026 8:57 pm
TL;DR: Gartner’s 2025 Identity Verification report and recent fraud cases show that false or compromised identity checks now create operational, safety, and liability risk across workforce onboarding, access, and service workflows, according to 1Kosmos. Traditional verification models are no longer enough when attackers combine social engineering, hiring fraud, and identity abuse to bypass trust gates.
Editorial analysis by NHI Mgmt Group, based on content published by 1Kosmos: “1Kosmos Takes the Lead in Workforce Identity Verification”.
By the numbers:
- 1Kosmos says customers have reduced identity fraud by more than 40% within six months of deployment.
- 1Kosmos says its global platform processes over one billion daily authentications for 75+ million users.
Key questions
Q: What breaks when remote identity verification is too weak in regulated onboarding?
A: Weak remote verification breaks the chain of trust between the claimed identity and the person or business being onboarded.
Q: Why do strong passwords or biometrics not solve identity fraud?
A: Strong passwords and biometrics improve authentication, but they do not prove that the person was correctly enrolled in the first place.
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
- Strengthen identity proofing before account creation Require higher-assurance checks for roles that can reach sensitive workflows, service desks or privileged access paths.
- Separate verification from authentication design Review whether your current controls assume that a strong login method proves the person was correctly enrolled.
- Map trust inheritance across workforce workflows Identify which systems assume the onboarding record is accurate, then test the operational impact when that assumption is wrong.
Bottom line: Identity verification has become a security boundary because false enrolment can propagate trust into every downstream access and workflow decision.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 5:52 am
Identity verification has become a security control, not an onboarding formality. The control now decides whether an individual is allowed to enter workforce, service, and privileged access workflows at all. When attackers can present convincing but false identity evidence, the problem is no longer authentication strength alone. Practitioners should treat verification as part of the security boundary that governs trust admission.
A question worth separating out:
Q: How should IAM teams respond when hiring fraud becomes a security risk?
A: Treat hiring fraud as an identity governance problem, not just an HR issue. Tighten proofing for sensitive roles, align verification with privileged access controls, and test whether workforce onboarding could admit a person who should never become a trusted digital identity.
👉 Read our full editorial: Identity verification is becoming the front line of enterprise security