TL;DR: A survey of more than 200 healthcare IT and security leaders found that 42% say passwords raise breach risk, 46% see risky password workarounds in daily operations, and only 7% have fully adopted passwordless access, according to Imprivata. The problem is not just credential theft but the way password-dependent workflows now undermine both security and clinical operations.
At a glance
What this is: This is a healthcare survey on why password dependence continues to create security, workflow, and care-delivery risk even where MFA and biometrics are in place.
Why it matters: It matters because healthcare identity programmes must reduce password reliance without breaking clinical access, auditability, or help desk operations across human, NHI, and adjacent workflow controls.
By the numbers:
- 46% reported risky password-related workarounds occurring in daily operations.
- Only 7% have fully adopted passwordless access across their organizations.
👉 Read Imprivata’s research on passwordless authentication in healthcare
Context
Healthcare identity security is still too often built around passwords, even though those credentials are brittle in fast-moving clinical environments. Shared workstations, urgent care workflows, and repeated logins create conditions where authentication becomes both a security control and an operational bottleneck.
The article’s core argument is that password dependence is no longer just a user inconvenience. It is a governance problem for IAM teams, because the same mechanisms that create friction for clinicians also expand help desk exposure, weaken attribution, and encourage risky workarounds that undermine policy enforcement.
Key questions
Q: How should healthcare organisations move away from passwords without disrupting clinical access?
A: They should replace passwords in the highest-friction workflows first, especially shared workstations, frequent logins, and urgent access paths. The key is to redesign authentication around clinical speed and session continuity, then harden recovery and fallback procedures so the organisation does not preserve password risk through the back door.
Q: Why do passwords remain a breach risk even when MFA is widely used?
A: Because MFA often sits on top of a password-dependent model rather than replacing it. Attackers can still target resets, recovery, and help desk processes, while users continue to create workarounds when access is slow. The risk is therefore distributed across the whole authentication lifecycle, not eliminated at the login screen.
Q: What do security teams get wrong about passwordless authentication in healthcare?
A: They often focus on the front-end login experience and ignore the support, recovery, and exception paths that determine whether passwordless actually reduces risk. If those paths still rely on weak manual verification or urgent overrides, the organisation has only moved the problem rather than solved it.
Q: Who should own passwordless governance in a healthcare organisation?
A: It should be shared across IAM, security operations, help desk leadership, and clinical application owners. Passwordless changes how people authenticate, how support teams recover access, and how clinicians work under pressure, so ownership must extend beyond a single technology team to include the workflows it changes.
Technical breakdown
Why passwords fail in clinical access workflows
Passwords break down in healthcare because the access pattern is high frequency, shared, and time constrained. Clinical users move between systems, devices, and locations, often under hygiene and speed constraints that make repeated credential entry impractical. That pressure pushes users toward reuse, sharing, and sticky sessions. Once those behaviours become normal, the password stops functioning as a meaningful proof of identity and becomes a friction point that the organisation works around instead of governing.
Practical implication: treat password reduction as a workflow redesign problem, not a policy reminder exercise.
Why MFA does not fully solve password dependency
The article shows a common control mismatch: MFA is added on top of password-centric access, but the underlying authentication model remains phishable and operationally fragile. If recovery, reset, and override flows still depend on password assumptions, attackers can target those adjacent processes instead of the login screen. Adaptive and risk-based authentication help, but only when they are designed to reduce the role of passwords rather than decorate the same weak foundation.
Practical implication: assess recovery and reset paths as first-class authentication controls, not back-office support processes.
How password resets expand the attack surface
Reset and recovery workflows create a second identity plane that attackers can manipulate through urgency and social engineering. In healthcare, help desks are under pressure to restore access quickly, so manual verification is often compressed. That means the real control boundary is no longer the login event, but the approval and recovery path around it. Every added reset step, vendor, or override path increases the number of places where identity can be impersonated without defeating the primary authentication stack.
Practical implication: harden recovery procedures with stronger verification and tighter privilege on help desk overrides.
NHI Mgmt Group analysis
Password dependence is now a governance failure, not just a usability problem. Healthcare organisations are no longer dealing with isolated bad passwords. They are managing an identity model that forces clinicians, help desks, and security teams to compensate for weak authentication with workarounds, overrides, and exceptions. That is a programme design issue, and it shows that password-centric access no longer fits the operational reality of care delivery. The implication is that IAM teams must stop treating passwords as the default control surface.
The real control gap sits in recovery, not login. If attackers cannot always steal the password, they target the paths created to recover it. Reset volume, manual verification, and support escalation all become identity decision points that were never designed for hostile pressure. This is where healthcare environments become especially exposed, because speed and safety requirements reduce the room for rigorous challenge. Practitioners should recognise that passwordless strategy fails if recovery remains password-shaped.
Workflow friction debt: repeated authentication burden creates the operational pressure that drives insecure behaviour. In healthcare, that debt accumulates when clinicians are forced to choose between access speed and policy compliance. The result is credential sharing, sticky sessions, and weaker attribution, all of which degrade auditability. That is not an edge case. It is what happens when identity controls are not aligned to the pace of clinical work. Practitioners should treat this as a measurable governance risk.
Passwordless is an access architecture decision, not a point product choice. The survey shows strong intent but low full adoption, which usually means organisations are trying to layer new methods onto old access patterns. That approach can reduce some friction while preserving the same weak recovery and exception logic. IAM, PAM, and clinical technology teams need a shared model for how authentication, session continuity, and fallback access work together. The implication is that governance must lead implementation.
From our research:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to The 2026 Infrastructure Identity Survey.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI, even as adoption accelerates across infrastructure and identity programmes.
- For the governance model behind those access decisions, see Ultimate Guide to NHIs , Lifecycle Processes for Managing NHIs.
What this signals
Passwordless adoption will succeed only if healthcare treats recovery as part of the authentication system. The next wave of programme failure will not come from login prompts alone, but from weak overrides, rushed verification, and support processes that preserve password-era assumptions. Teams should expect the real governance burden to shift into fallback paths, identity proofing, and help desk control design.
As authentication becomes more session-based and less password-centric, IAM teams will need tighter coordination with clinical operations and service desk leadership. That is especially true where access decisions affect patient throughput, auditability, and break-glass handling. The right programme question is no longer whether users like passwordless, but whether the organisation can govern it without creating new exceptions.
Workflow friction debt: in healthcare, accumulated authentication friction turns into measurable security and care-delivery risk, and that risk will only rise if access design lags operational reality. Organisations that do not measure reset volume, manual overrides, and login delays as governance signals will keep mistaking user frustration for a usability issue when it is actually a control failure.
For practitioners
- Map every password-dependent clinical workflow Identify where clinicians, support staff, and contractors still rely on passwords for login, reset, recovery, shared devices, and break-glass access. Prioritise the workflows that create repeated friction or frequent overrides, because those are the places where users are most likely to adopt insecure shortcuts.
- Harden recovery and help desk verification Review password reset, account recovery, and support override procedures as high-risk identity events. Limit who can approve them, require stronger verification for urgent cases, and remove any recovery path that can be socially engineered faster than it can be validated.
- Reduce credential sprawl across access channels Consolidate authentication methods across clinical, enterprise, cloud, and remote access systems so users are not forced to remember different credentials for different contexts. The fewer password paths you keep, the easier it becomes to remove insecure workarounds and improve auditability.
- Measure workflow pressure alongside security metrics Track reset volume, login failure rates, session reuse, credential sharing reports, and help desk workload together. If security metrics improve while operational pressure rises, the programme is probably pushing risk into the user experience instead of removing it.
Key takeaways
- Passwords are failing in healthcare because they no longer fit the pace, sharing patterns, and urgency of clinical work.
- The survey shows a wide gap between intention and execution, with only 7% fully deployed on passwordless access despite strong recognition of the risk.
- The most important next step is to redesign recovery, overrides, and fallback access so passwordless reduces risk instead of relocating it.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, NIST CSF 2.0 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Passwordless and MFA design map directly to digital identity assurance and authentication. | |
| NIST CSF 2.0 | PR.AC-1 | Access control policy and identity verification are central to the passwordless transition. |
| NIST Zero Trust (SP 800-207) | ID | Zero trust depends on stronger identity assurance than reusable passwords provide. |
Align authentication redesign with PR.AC-1 and review fallback access paths for weak verification.
Key terms
- Passwordless Authentication: An authentication approach that replaces reusable passwords with stronger methods such as biometrics, device-bound credentials, or hardware-backed tokens. In practice, it reduces phishing exposure and user friction, but only if recovery, fallback, and help desk processes are also designed to avoid reintroducing password-era weakness.
- Recovery Workflow: The set of steps used to restore access when a user cannot authenticate normally. These workflows matter because they often become the weakest point in the identity chain, especially when urgency, manual verification, and support overrides create opportunities for social engineering or policy bypass.
- Workflow Friction Debt: The cumulative operational risk created when authentication is so cumbersome that users adopt shortcuts, workarounds, and exceptions to keep work moving. In healthcare, this debt shows up as shared credentials, sticky sessions, reset overload, and weaker auditability, all of which erode control quality.
Deepen your knowledge
NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are responsible for identity security strategy or NHI governance in your organisation, it is worth exploring.
This post draws on content published by Imprivata: The state of passwordless authentication in healthcare, Ending password pain. Read the original.
Published by the NHIMG editorial team on 2026-01-21.
NHI Mgmt Group — the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org