Discoverable credentials are stored on the FIDO2 device itself, so authentication can still work if the device is available. Non-discoverable credentials require a separate private key for use, which creates a stronger loss boundary but less recovery flexibility. For SSH, the choice affects how teams balance usability, device loss, and control over key material.
How SSH FIDO2 credential type changes recovery and loss handling
The practical difference is not just where the credential lives, but what happens when the token is unavailable. Discoverable credentials keep the usable credential state on the FIDO2 authenticator, which can reduce dependence on a separate file or key path. Non-discoverable credentials shift more of the recovery burden to the SSH side, so loss, replacement, and re-enrollment become more deliberate operational events.
That distinction matters because SSH access is often built around device continuity, not just successful sign-in. When the device is lost, replaced, or reset, discoverable credentials can be easier to recover if the authenticator and its stored credential remain intact, while non-discoverable credentials are usually easier to reason about as a tighter boundary around key material.
For teams comparing the two, the key question is which failure mode they want to optimize for: convenience after device loss, or stronger separation between the authenticator and the SSH key material used to prove possession.
What changes in SSH operations and key governance
In SSH, discoverable credentials tend to fit environments that want a more integrated user experience, especially where the same authenticator is expected to support repeated access with less manual key handling. Non-discoverable credentials fit environments that want the private key to remain separately controlled, which can be helpful when administrators want tighter handling of the SSH credential lifecycle.
That is why this choice is partly about governance. If the SSH credential is embedded in the FIDO2 device, the recovery process depends more on the device lifecycle and the authenticator's state. If the credential is non-discoverable, teams can enforce a clearer separation between the authenticator and the private key, but they also take on the need to manage that extra key material well.
For readers who want a broader view of the FIDO2 and SSH building blocks, FIDO2 and WebAuthn Internals Guide is useful for understanding the resident key and credential-model side of the comparison, while SSH Key and SSH Certificate Management Guide covers the surrounding SSH key and certificate governance concerns.
When one model is safer than the other
Neither model is universally better. Discoverable credentials usually improve usability and can reduce the friction of login and recovery, but they also make the authenticator itself a more important recovery dependency. Non-discoverable credentials usually create a stronger loss boundary because the SSH private key is not relying on discoverable state on the token, but that comes with more administrative overhead.
Teams should decide based on how they handle lost devices, break-glass access, and re-provisioning. If the operational environment assumes frequent replacement and fast restoration of access, discoverable credentials may be the better fit. If the environment values stricter separation and clearer control over where key material is held, non-discoverable credentials are often easier to govern.
That trade-off is also why SSH should not be treated as a generic passkey rollout problem. The SSH access path, host trust model, and recovery process all have to align with the credential type you choose.
Risk and Threat Considerations
SSH FIDO2 credential choice changes the blast radius of device loss and the way attackers may try to exploit recovery. Discoverable credentials can make stolen or misplaced authenticators more sensitive if the device can still satisfy authentication, while non-discoverable credentials can push risk into the separate private key path if that key is poorly protected or copied elsewhere.
Failure mechanism: The control fails when teams confuse convenience with resilience, or when they lose track of where the SSH private key actually lives. A discoverable credential can become a single point of dependency on the authenticator, while a non-discoverable credential can become a separate secret-management problem if the companion key is exported, reused, or left unrotated.
Impact: The likely result is either avoidable access loss after device replacement or avoidable exposure if the supporting key material is copied, cached, or recovered too broadly. In both cases, the operational weakness is not the FIDO2 token itself, but the mismatch between credential model and access recovery process.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST SP 800-63, OWASP ASVS and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | SSH credential choice changes authenticator and key lifecycle management. |
| IA-9 — Service Identification and Authentication | FIDO2-backed SSH access depends on authenticating a non-human or technical access path. | |
| Recommendation — Manage SSH credential issuance, replacement, rotation, and revocation explicitly. Use strong authenticators for machine and service access paths. | ||
| NIST SP 800-63 | Authenticator Assurance — Authenticator Assurance | FIDO2 SSH access is shaped by phishing-resistant authenticator properties and recovery choices. |
| Recommendation — Select phishing-resistant authenticators and align recovery with assurance needs. | ||
| OWASP ASVS | V6 — Authentication | The question is about authentication method behavior and recovery trade-offs. |
| Recommendation — Verify that authentication flows and recovery paths match the chosen credential model. | ||
| CIS Controls v8 | CIS-5 — Account Management | SSH credential handling affects account lifecycle, provisioning, and removal. |
| Recommendation — Inventory and remove SSH access paths when users or devices change. | ||
Practitioner Guidance
What to verify: Confirm whether your SSH implementation, client tooling, and recovery process actually support the credential model you intend to use. A design that looks cleaner on paper can fail in practice if help desk recovery, hardware replacement, or bastion access procedures still assume a different key lifecycle.
Decision rule: If device continuity is the primary concern, prefer the model that keeps sign-in simplest to restore. If tighter control over SSH key material is the primary concern, prefer the model that keeps the credential boundary clearer and place extra discipline on key storage, rotation, and replacement handling.
Practitioner takeaway: Choose the credential type by the failure mode you can tolerate best, then make recovery, replacement, and rotation procedures match that choice instead of treating SSH access and FIDO2 enrollment as separate decisions.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org