TL;DR: Password managers now have to address friction, passkeys, AI-driven attacks, and the mix of human and agent identities as credential use keeps expanding, according to Bitwarden. The governance problem is no longer storage alone; identity teams have to plan for trust, usability, and lifecycle control together.
At a glance
What this is: This is a Bitwarden perspective on how password management is expanding into passkeys, AI-driven threats, and agent identity governance.
Why it matters: It matters because IAM teams now have to treat credential tooling as a broader trust and lifecycle control surface across human and non-human identities.
Context
Credential management is no longer just about storing passwords in a vault. As organisations adopt passkeys and encounter AI-driven attacks, the control surface expands from human login convenience into broader identity governance for both people and machine-driven access patterns.
This article frames Bitwarden's current direction through a practitioner lens: reducing friction, preserving trust, and supporting the shift from password-only thinking to mixed credential estates. For IAM teams, the practical question is how to govern that transition without creating new usability failures or lifecycle blind spots.
Key questions
Q: How should security teams roll out passkeys without breaking account recovery?
A: Start with low-risk journeys, then define recovery as a controlled identity workflow rather than a convenience feature. Use step-up verification, help-desk approval, and audit logging for resets. The goal is to keep passwordless sign-in simple while making fallback paths stricter than the primary login path. That is where most account abuse begins.
Q: Why do credential tools fail when they create too much friction for users?
A: Because users do not only evaluate security, they evaluate whether a control fits their work. If a password manager or authentication workflow slows them down, they route around it, reuse weaker habits, or delay adoption. In practice, usability failures become governance failures because the control no longer governs real behaviour.
Q: How should organisations separate human and agent credential governance?
A: Use different ownership, issuance, and offboarding rules for people and agents. Human credentials map to employment or access roles, while agent credentials map to workload, workflow, or task boundaries. If both sit in the same inventory without distinction, revocation, review, and accountability become unreliable.
Q: What should teams look for when credential security depends on open source trust?
A: Look for transparency, auditability, and deployment control that let security teams verify behaviour instead of relying on marketing claims. In identity tooling, trust is not abstract. Teams need to know how the software is built, what can be inspected, and how much operational control they retain over sensitive credential workflows.
Technical breakdown
Why passkeys change the credential control model
Passkeys reduce reliance on reusable passwords by shifting authentication toward cryptographic, device-bound credentials. That changes the control model because the risk is no longer only secret theft. It becomes about enrolment, device trust, recovery paths, and whether the organisation can govern the full lifecycle of a credential that is easier to use but harder to explain in legacy policy language. For IAM teams, passkeys are not just another login option; they alter how identity assurance is created and maintained.
Practical implication: map passkey adoption to enrolment, recovery, and fallback controls before treating it as a password replacement.
How AI-driven attacks pressure credential workflows
AI-driven attacks matter here because they reduce the value of static user education and increase the speed and scale of credential abuse. In practical terms, phishing, social engineering, and automated guessing all become more efficient when attackers can adapt content and timing. That makes the control problem less about storing secrets securely and more about reducing the opportunity window in which a credential can be captured and reused. Identity teams should read this as a shift toward continuous resistance, not one-time hardening.
Practical implication: tighten detection and recovery around credential abuse patterns rather than relying on user awareness alone.
What changes when agent identity enters the password manager boundary
Agent identity changes the governance boundary because not every identity interacting with a credential platform is a person. An agent may need secrets, tokens, or delegated access to complete tasks, but its access pattern is operational rather than human. That breaks assumptions embedded in user-centric password management, where onboarding, approval, and revocation are often designed around employment status and human behaviour. The management challenge is to distinguish human ownership from machine execution and apply different lifecycle logic to each.
Practical implication: separate human credential governance from machine and agent credential governance in policy, inventory, and offboarding.
Breaches seen in the wild
- Bitwarden CLI npm compromise 2026: A malicious Bitwarden CLI on npm, linked to the Checkmarx campaign, targeted GitHub, npm, cloud and CI secrets from developers for 90 minutes.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Credential management is becoming an identity governance problem, not a storage problem. Once a platform handles passwords, passkeys, secrets, and agent access, the control boundary shifts from vaulting to lifecycle governance. That means the real question is not whether credentials are stored securely, but whether their issuance, recovery, and retirement are aligned to the identity type using them. Practitioners should treat the platform as part of the identity control plane, not a simple utility.
Passkey adoption exposes the limits of password-era policy language. Password policies assume reusable secrets, user memory, and predictable fallback paths. Passkeys break that model by moving trust into devices, keys, and recovery mechanics that are easy to misuse if the surrounding governance is not updated. The implication is that identity programmes need new operating assumptions for assurance, recovery, and support workflows, not just a new authentication option.
Agent identity introduces an ownership problem that human IAM does not solve cleanly. Human credential processes assume a person can be trained, challenged, and offboarded. Agent access can be delegated, copied, or embedded into workflows that outlive the operator's intent. That means the governance model has to answer who owns the credential, who can retire it, and what accountability looks like when execution is machine-driven. Practitioners should separate operator responsibility from execution authority.
Friction is a security control issue because adoption failure becomes governance failure. The article is right to treat usability as a prerequisite for durable security behaviour. If controls are too hard to use, users route around them, which creates shadow processes and weakens assurance. The practical lesson for identity teams is that control design and user experience are not competing priorities; they are the same governance problem viewed from different angles.
Open source trust changes the procurement question for identity tooling. Auditability, self-hosting, and verification matter because credential systems sit inside the most sensitive parts of the identity stack. For practitioners, that means evaluating not only features but also transparency, deployment control, and the ability to prove what the software is doing. In this category, trust is an operational requirement, not a brand attribute.
What this signals
Password-era governance is giving way to mixed credential governance. Teams now have to manage passwords, passkeys, secrets, and agent access as one control surface with different lifecycle rules. The important shift is not the removal of passwords, but the need to govern several credential types at once without collapsing them into a single policy.
Usability now sits inside the security model. When controls create friction, users abandon them and the programme loses visibility into real behaviour. That makes adoption, recovery, and support flow design part of the security architecture rather than post-deployment cosmetics.
For practitioners
- Define credential governance by identity type Split policy for human users, service accounts, and agents so that onboarding, recovery, and offboarding are handled by the right lifecycle model.
- Review passkey recovery paths Document what happens when a device is lost, a user changes roles, or a credential must be reassigned, then test whether those paths preserve assurance.
- Inventory agent access separately Track where agents use secrets, tokens, or delegated credentials so that machine-driven access does not disappear into human credential inventories.
- Reduce abandonment risk from friction Measure where users bypass the tool, fall back to unsafe habits, or resist enrolment because the workflow adds too much effort.
Key takeaways
- Credential management is expanding beyond password storage into passkeys, secrets, and agent access governance.
- Friction remains a primary reason security tools fail to stick with users, which turns usability into an identity control issue.
- IAM teams need separate lifecycle rules for human and non-human access if they want credential governance to scale.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and OWASP Agentic AI Top 10 address the attack and risk surface, while NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-04 — Insecure Authentication | The article centres on how credential workflows change as passkeys and agent access enter the stack. |
| NHI-10 — Human Use of NHI | Agent identity and delegated access create pressure to distinguish human use from machine execution. | |
| Recommendation — Review authentication workflows that span passwords, passkeys, and delegated access for weak assurance paths. Separate human credential use from non-human execution paths in policy, inventory, and offboarding. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | The piece is fundamentally about lifecycle control of credentials, authenticators, and recovery paths. |
| Recommendation — Apply authenticator lifecycle controls to issuance, recovery, rotation, and revocation processes. | ||
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | The article argues that identity teams must govern who or what can use credentials across multiple identity types. |
| Recommendation — Align credential access decisions with identity type and entitlement boundaries. | ||
| OWASP Agentic AI Top 10 | ASI03 — Identity & Privilege Abuse | Agent identity introduces delegated access and privilege boundaries that can be misapplied at runtime. |
| Recommendation — Bound agent privileges to the task and verify that delegated access cannot be reused outside scope. | ||
Key terms
- Passkey: A passkey is a passwordless credential based on public key cryptography. A private key stays on the user’s device, while a public key is stored by the service. During login, the device signs a challenge after local unlock, which reduces phishing and eliminates shared secret reuse.
- Agent Identity: An agent identity is the set of attributes, credentials and permissions assigned to an autonomous software entity. It is treated as a non-human identity because it can authenticate, act on systems and accumulate access over time, which creates governance, audit and lifecycle obligations similar to other production identities.
- Credential Lifecycle: Credential lifecycle is the process of issuing, rotating, expiring, and revoking secrets, certificates, and tokens across their usable life. For non-human identities, lifecycle discipline is the core control that separates temporary access from persistent exposure.
- Authentication Friction: The delay, confusion, and support burden created when users cannot complete sign-in cleanly. In IAM programmes, friction is a governance signal because it drives resets, exceptions, and workarounds. If users routinely hit the recovery path, the authentication design is not yet operationally stable.
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.
Published by the NHIMG editorial team on July 8, 2026.
Updated on October 11, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org