Topic starter
11/07/2026 8:48 pm
TL;DR: Growing demand for API-driven CIAM and passwordless authentication that fits existing identity stacks is reflected in KuppingerCole’s Rising Star recognition for Authsignal, with FIDO2, biometrics, and policy-based orchestration called out in the report. The real issue is not the rating itself, but the move toward modular identity fabrics that reduce friction without weakening access control.
Editorial analysis by NHI Mgmt Group, based on content published by Authsignal: “Authsignal recognized as a KuppingerCole Rising Star in CIAM and passwordless authentication”.
Key questions
Q: How should teams introduce passwordless authentication without replacing their whole CIAM stack?
A: Start by integrating passwordless methods into the existing identity provider and orchestration layer rather than rebuilding customer identity from scratch.
Q: Why do modular identity fabrics matter for customer authentication programmes?
A: They let organisations combine passwordless methods, MFA orchestration, and policy enforcement without forcing every application to adopt the same implementation pattern.
Q: When does passwordless authentication create new governance risk?
A: Passwordless becomes risky when organisations focus only on the happy path and ignore enrolment, device binding, fallback recovery, and support-mediated reset flows.
Practitioner guidance
- Map authentication services to an identity fabric model Identify which customer authentication functions can be separated into reusable services, then define where policy enforcement and orchestration must remain central across applications and channels.
- Review fallback methods for controlled access Document every non-password path, including SMS, email, push, and wallet-based credentials, and make sure each is governed by assurance rules rather than convenience alone.
- Align passkey rollout with existing identity providers Use current identity providers as the integration anchor so passwordless adoption adds capability without creating a parallel identity estate that is harder to govern.
Bottom line: Passwordless CIAM is shifting from a feature discussion to an architecture discussion about how authentication services fit into existing identity stacks.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/07/2026 9:14 pm
Modular authentication is becoming the practical bridge between legacy identity stacks and passwordless adoption. The article shows that organisations want stronger customer authentication without rewriting their entire CIAM estate. That makes modular, API-driven orchestration more relevant than standalone factor innovation. The field should read this as a sign that integration capability is now part of identity security maturity, not just a deployment convenience.
A few things that frame the scale:
- eBay's passkey data shows 55-60% of passkey adoption happens on mobile, against around 20% on desktop.
A question worth separating out:
Q: How should IAM teams use an identity fabric without creating more sprawl?
A: Treat identity fabric as a coordination layer, not another control plane to administer in isolation. The goal is to standardise lifecycle, authentication, authorisation, and audit decisions across systems so that policy intent survives each handoff. If the fabric adds another set of exceptions, it is increasing complexity instead of reducing it.
👉 Read our full editorial: Passwordless CIAM recognition shows demand for flexible identity fabrics