TL;DR: Identity proofing and passwordless authentication are moving into the security perimeter, while autonomous AI use raises the stakes for verified identity controls, according to 1Kosmos. 1Kosmos says its $57M Series B, bringing total funding to $72M, follows 3x revenue growth, FedRAMP High authorization, NIST 800-63-3 certification, and a Microsoft partnership for external authentication methods.
Editorial analysis by NHI Mgmt Group, based on content published by 1Kosmos: “Founders and Team Members Are Investing Their Own Personal Capital in the Series B”.
Key questions
Q: How should IAM teams use identity proofing in high-risk access flows?
A: Treat identity proofing as an upstream trust signal that must influence later access decisions, not a one-time onboarding checkbox.
Q: Why do passwordless systems still need identity governance?
A: Passwordless systems still need identity governance because authentication strength does not answer lifecycle questions.
Q: What breaks when identity assurance is not propagated into access policy?
A: The proofing decision becomes a dead signal.
Practitioner guidance
- Define assurance tiers for verified identity Map user populations, transaction types, and access paths to explicit assurance levels so proofing strength matches business risk.
- Bind authentication to enrolment confidence Ensure the access policy consumes proofing outcomes, so a weak enrolment cannot later receive high-risk privileges without re-verification.
- Stress-test impersonation resistance Evaluate whether synthetic voice, deepfake, and social engineering scenarios can bypass your current identity checks and step-up controls.
Bottom line: Verified digital identity is becoming a governance issue for IAM teams because weak proofing and weak authentication now create the same trust problem.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Verified identity is becoming the new trust boundary for access governance. When passwords become easier to replay, phish, or socially engineer, the point of assurance shifts to identity proofing and strong authentication. That changes the job of IAM from credential administration to trust establishment across the identity lifecycle. Practitioners should treat verified identity as a foundational access control, not an adjacent onboarding step.
A question worth separating out:
Q: How should financial services teams balance identity verification security with user experience?
A: Use risk-based verification so low-risk users pass quickly while higher-risk cases trigger stronger document, biometric, or manual review steps. The goal is not to remove friction everywhere, but to place friction where it changes risk. Track abandonment, fraud rates, and exception handling together so you can see whether the flow is protecting both conversion and trust.
👉 Read our full editorial: 1Kosmos funding signals rising demand for verified digital identity