Join our Newsletter — 33% off our NHI Course

What would it take for Crucial Facial Group to work in shared-device access?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: Facial biometrics still need lifecycle governance, Imprivata argues, because enrolment, fallback, retention and audit remain necessary even when passwords fall away. Shared-device access still needs defined recovery paths and exception handling, or passwordless rollout fragments assurance across users and legacy apps.

Editorial analysis by NHI Mgmt Group, based on content published by Imprivata: “Face authentication: Crucial insights and the Imprivata advantage”.

Key questions

Q: Why do facial biometrics create different governance issues from passwords?

A: Passwords are revoked and rotated as shared secrets, while facial biometrics introduce enrolment, template storage, consent, and liveness concerns.

Q: What breaks when passwordless is rolled out to only part of an application estate?

A: Users and support teams end up operating under two authentication models at once.

Q: How should security teams implement facial biometrics in passwordless IAM?

A: Start by limiting facial biometrics to environments where the application stack, device posture, and fallback controls are already defined.

Practitioner guidance

  • Define the passwordless scope first Map which user groups, shared devices, and application types will use facial biometrics, then separate native support from integration workarounds.
  • Standardise fallback authentication paths Document what happens when biometric capture fails, device trust is unavailable, or a user needs an alternate method so the access model remains governable.
  • Inventory legacy application constraints Identify systems that still depend on keyboard-based login or older protocols and classify them as exceptions before rollout expands.

Bottom line: Facial biometrics can reduce password friction, but they do not remove the need for lifecycle governance across enrolment, fallback, retention, and audit.

Glossary terms: Facial Biometrics, Passwordless Authentication, Shared-Device Access, Authenticator Lifecycle Management

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 7 days ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20712
 

Passwordless does not eliminate identity governance debt, it relocates it. Facial biometrics can reduce password friction, but the programme still has to govern enrolment, consent, retention, fallback authentication, and exception handling. If those controls remain fragmented, organisations simply move risk from password compromise to inconsistent identity policy. The practitioner conclusion is that passwordless must be governed as an identity lifecycle change, not a point technology upgrade.

A question worth separating out:

Q: Should organisations prioritise device trust or user convenience in passwordless access?

A: They need both, but device trust must come first because the authenticator becomes the centre of the control model. Convenience matters for adoption, yet it should not override enrolment assurance, loss handling, and reissue rules that keep passwordless access governable at scale.

👉 Read our full editorial: Facial biometrics still depend on lifecycle governance


This post was modified 7 days ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.