By NHI Mgmt Group Editorial TeamPublished 2026-04-30Domain: AnnouncementsSource: Imprivata

TL;DR: Healthcare IAM must balance clinician speed with stronger assurance, role precision, and Zero Trust-aligned access governance, as Imprivata says its expanded Enterprise Access Management platform adds facial recognition, high-assurance identity verification, and AI-powered behavioural analytics to help NHS organisations strengthen access controls, support audit evidence, and reduce dependence on shared credentials.


At a glance

What this is: This is an independent look at Imprivata’s expanded NHS access management capabilities and the key finding that passwordless, high-assurance access is now being tied to compliance, auditability, and workforce friction reduction.

Why it matters: It matters because healthcare IAM teams must govern human access, shared devices, and privileged workflows under tighter assurance expectations without making clinical access unusable.

👉 Read Imprivata’s overview of expanded NHS access management and passwordless controls


Context

NHS identity governance is being pushed toward stronger authentication, tighter auditability, and less dependence on shared credentials at the same time that clinicians need fast access to shared and personal devices. In that environment, the primary problem is not authentication in isolation, but whether access control can satisfy compliance without slowing care delivery.

Imprivata’s announcement sits inside that tension: passwordless access, high-assurance identity verification, and behavioural analytics are being positioned as a way to support assurance frameworks such as the CAF-aligned DSPT and Spine Authentication. For healthcare IAM teams, the practical question is how to modernise access without turning every login into a workflow bottleneck.


Key questions

Q: How should healthcare teams reduce dependence on shared credentials without slowing clinicians down?

A: Start with the workflows that depend most on shared workstations, rapid handoffs, and repeated sign-ins. Replace reusable credentials with stronger authenticators and context-aware access paths, then test whether recovery and help desk processes still preserve accountability. The goal is not just stronger login, but faster access with clearer identity proof.

Q: Why do shared clinical devices create problems for standard IAM controls?

A: Shared devices weaken the assumption that one account maps cleanly to one person and one session. That makes audit trails, access reviews, and misuse detection less reliable unless the environment adds stronger identity verification and session controls. In practice, the access model must match communal use rather than individual ownership.

Q: What do security teams get wrong about passwordless authentication in regulated environments?

A: They often treat passwordless as a convenience layer instead of a governance control. If identity proofing, recovery, logging, and policy enforcement are weak, the organisation has only moved the risk elsewhere. In regulated settings, passwordless must support accountability and evidence, not simply remove a password prompt.

Q: How do you know if behavioural analytics are actually improving access security?

A: Look for whether the analytics change decisions, not just alert volume. A useful programme uses risk signals to drive step-up authentication, session restriction, or targeted review, and can show that those actions reduce exposure without disrupting care. If the signal never changes an access outcome, it is not doing control work.


How it works in practice

Passwordless authentication for shared clinical devices

Passwordless access shifts the authentication burden away from reusable secrets and toward stronger authenticators such as biometrics or device-bound methods. In healthcare, that matters because shared-workstation patterns often break the assumptions behind single-user credential ownership. The control challenge is not simply removing passwords, but proving who accessed what on a shared device without creating delay at point of care. Context-aware authentication adds another layer by using session or location signals to adjust assurance requirements. Practical implication: design passwordless flows around device sharing, not around the assumption of individual, persistent endpoints.

Practical implication: design passwordless flows around device sharing, not around the assumption of individual, persistent endpoints.

High-assurance identity verification and audit evidence

High-assurance verification is about making identity proofing and step-up checks defensible enough for onboarding, help desk recovery, and sensitive access changes. In regulated health environments, the evidence problem is as important as the access decision itself. Audit-ready controls depend on detailed logs, traceability, and policy enforcement that can survive toolkit submission or independent assessment. Role-based and attribute-aware policies help narrow access, but they only matter if the organisation can show why a user received that access at that moment. Practical implication: align verification, logging, and access justification so the audit trail matches the control outcome.

Practical implication: align verification, logging, and access justification so the audit trail matches the control outcome.

Behavioural analytics in zero trust access decisions

Behavioural analytics look for deviations in how users access resources, then feed those signals into policy decisions or investigations. In a Zero Trust model, access should be continuously evaluated rather than assumed safe after initial login. That makes behavioural telemetry useful, but only when it is tied to clear action paths, not just alerts. In healthcare, anomalies can signal compromise, misuse, or workflow drift on shared devices. The important architecture point is that analytics should inform access decisions without creating so much friction that clinicians bypass controls. Practical implication: treat behavioural signals as decision inputs, not as standalone security outcomes.

Practical implication: treat behavioural signals as decision inputs, not as standalone security outcomes.


NHI Mgmt Group analysis

Healthcare identity is still struggling with the shared-device problem. NHS environments cannot rely on identity patterns built for one person, one device, and one session. Shared-use workstations, fast handoffs, and urgent access to patient systems create a control environment where reusable secrets and slow sign-in flows are structurally weak. The implication is that healthcare IAM must be judged on how well it handles communal access, not just how well it protects a single user account.

Passwordless access is an assurance model, not just a usability feature. In clinical settings, the real value of passwordless is that it can reduce credential reuse while preserving access speed under pressure. But the control only works if identity proofing, device trust, and recovery paths are equally strong. Otherwise, the organisation has simply moved risk from passwords to fallback processes and help desk identity recovery.

Shared-credential reduction: This announcement points directly at the failure mode where multiple staff members still depend on credentials that cannot prove individual accountability. That control gap matters because auditability, misuse detection, and access review all weaken when identity is shared at the point of use. Practitioners should read this as a governance problem first and a technology problem second.

Behavioural analytics matter most when they are tied to access governance. Risk signals become useful only if they change access outcomes, such as step-up verification, session restriction, or help desk verification paths. In healthcare, that makes the difference between noise and operational control. The field is moving toward access systems that must explain and defend every authentication decision, not just authenticate faster.

CAF-aligned evidence will increasingly shape access architecture decisions. The announcement reflects a broader market shift in which identity controls are evaluated for their reporting and audit evidence as much as for their user experience. That means NHS and adjacent healthcare organisations should expect authentication, access logging, and policy enforcement to converge into a single governance conversation. Practitioners should plan for evidence-ready access design, not bolt it on later.

From our research:

  • Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
  • That visibility gap matters because 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools.
  • For the broader breach context, see 52 NHI Breaches Analysis for how compromised identities turn into repeated access failures.

What this signals

Shared-device access will keep exposing the limits of conventional IAM if governance cannot prove who acted, when, and under which policy. NHS organisations should expect passwordless and high-assurance verification to become part of evidence production, not just user experience. The access stack has to support both operational speed and defensible accountability.

Identity assurance is becoming inseparable from workflow design. If clinicians must work around security, they will route around it. Teams should watch for sign-in friction, weak recovery paths, and policy exceptions that quietly recreate shared secret behaviour under a different name.

With only 5.7% of organisations reporting full visibility into their service accounts, the broader identity lesson is that control gaps often begin where the programme cannot see its accounts clearly. Ultimate Guide to NHIs provides the baseline governance lens, while 52 NHI Breaches Analysis shows how unseen identity sprawl becomes operational risk.


For practitioners

  • Map shared-device access paths first Identify where clinicians and support staff share devices, then document where current sign-in patterns depend on reusable credentials or weak fallback recovery. Use that map to prioritise passwordless flows and session controls where accountability is currently blurred.
  • Tie verification to audit evidence Make sure onboarding, help desk recovery, and access changes produce logs that explain who was verified, what policy applied, and why access was granted. If the evidence cannot survive external review, the control is not mature enough for regulated healthcare.
  • Use behavioural signals to change outcomes Define in advance which anomalous behaviours should trigger step-up checks, session restriction, or case review. Behavioural analytics should support an access decision, not sit as a passive monitoring layer.
  • Review role and attribute policies for clinical edge cases Test whether role-based and attribute-aware rules still work during shift changes, emergency access, and shared workstation handoffs. The goal is to keep access precise without forcing clinicians into workarounds.

Key takeaways

  • NHS access modernisation is really an accountability problem, because shared devices and clinical urgency weaken assumptions built into conventional IAM.
  • Passwordless authentication only reduces risk when proofing, recovery, logging, and policy enforcement work together as one governance model.
  • Behavioural analytics and Zero Trust controls matter when they change access outcomes and produce evidence that can stand up to audit.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0, NIST Zero Trust (SP 800-207) and NIST SP 800-63 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0PR.AC-1Passwordless and role-aware access support identity and access governance in healthcare.
NIST Zero Trust (SP 800-207)PR.AC-4Zero Trust access and contextual verification are central to the announcement.
NIST SP 800-63IAL2High-assurance identity verification aligns with stronger proofing expectations for sensitive access.

Map NHS authentication controls to PR.AC-1 and prove access decisions are logged and explainable.


Key terms

  • Passwordless Authentication: An authentication method that removes reusable passwords and replaces them with stronger factors such as biometrics, device binding, or cryptographic credentials. In regulated environments, the control only works when recovery, logging, and policy enforcement are equally strong, so accountability is preserved rather than shifted elsewhere.
  • High-Assurance Identity Verification: A stronger identity check used when access decisions need more confidence than a basic login can provide. It is common in onboarding, help desk recovery, and sensitive workflow changes, where the organisation must prove that the right person was verified under the right conditions.
  • Behavioural Analytics: The analysis of how a user or device normally behaves so that unusual access patterns can be detected and acted on. The value is not in the alert itself but in whether the signal changes access outcomes, such as step-up checks, session restriction, or case review.
  • Shared-Device Access: An access pattern where multiple users authenticate through the same endpoint or workstation, often seen in healthcare and operational environments. It weakens simple one-user, one-device assumptions and requires stronger identity proofing, session control, and audit evidence to preserve accountability.

Deepen your knowledge

Passwordless authentication, shared-device access, and audit-ready identity controls are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are modernising healthcare access under compliance pressure, it is worth exploring.

This post draws on content published by Imprivata: advanced access management and passwordless authentication for NHS security and compliance challenges. Read the original.

NHIMG Editorial Note
Published by the NHIMG editorial team on 2026-04-30.
NHI Mgmt Group — the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org