Join our Newsletter — 33% off our NHI Course
Home› FAQ› Authentication, Authorisation & Trust› What happens when users lose all trusted devices…
Authentication, Authorisation & Trust

What happens when users lose all trusted devices but still need access to a passkey protected account?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: Authentication, Authorisation & Trust

If all trusted devices are lost, access depends on whether a recovery path was prepared in advance. Without one, the account can become difficult or impossible to unlock. A practical design includes optional recovery codes, secure storage instructions, and a documented restoration process so account continuity does not depend on a single device.

What changes when a passkey account is device-dependent?

Passkeys are not like a remembered password you can type from any browser. Depending on how they were set up, they may live on one device, sync through an account service, or rely on a security key. That means the real question is not whether the passkey exists, but whether a second trusted path was preserved before the device was lost.

When the only trusted device disappears, account access shifts from everyday sign-in to account recovery. If the passkey was synced, another enrolled device or the sync provider may restore access. If it was device-bound, the account usually needs a separate recovery method, such as backup codes, a second security key, or a help-desk or identity-check process that was prepared earlier.

For a clear overview of these recovery patterns, the Passwordless and Passkeys Guide explains how passkeys are stored, how recovery works, and where the design choices differ between synced and device-bound credentials.

How account recovery works when no trusted device is left

Recovery only works if the account owner has an alternate proof path that is separate from the lost device. That can include printed recovery codes, a second hardware security key, a pre-registered trusted device, or a documented restoration flow through the identity provider, password manager, or platform account holding the synced passkey.

The hardest failure mode is single-point dependency. If all access depends on one device and there is no recovery factor, the account may be effectively locked until an administrator, vendor, or support process can re-establish trust. That is why passkey rollout should be treated as an account continuity project, not only a sign-in upgrade.

The practical design question is whether the recovery route itself is durable, observable, and supportable. A good setup keeps recovery codes accessible but protected, and it avoids creating a weaker fallback that is easier to phish or social-engineer than the original passkey.

What should be prepared before the device is lost?

Recovery planning should happen while the account is still healthy. The most useful preparation is simple: enroll more than one authenticating factor where the platform allows it, store recovery codes offline or in a secure password manager, and document which provider owns the sync or restore process so the user does not have to rediscover it under pressure.

Teams supporting consumer or workforce accounts should also decide who can reset access, what evidence is required, and what happens after recovery. If the account protects email, finance, admin, or production access, restoration should be treated as a controlled event, not a casual reset.

For a broader view of passkey setup and lost-device scenarios, see the Passkeys for Everyone Guide. For the recovery design itself, the Passkey account recovery guide focuses on recovery codes, second keys, and avoiding phishable fallbacks.

Risk and Threat Considerations

Lost trusted devices create a recovery risk, because the same factor that made sign-in convenient can also become the only way back in. If the fallback path is weak, undocumented, or dependent on informal support decisions, an attacker may be able to exploit the recovery process instead of the passkey itself.

Failure mechanism: The account becomes unrecoverable when the last trusted device is gone and no independent restoration method exists, or the restoration method is easier to abuse than the original sign-in flow.

Impact: Users can be locked out of critical services, while poorly designed recovery paths can expose the account to takeover, social engineering, or excessive support intervention.

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, OWASP ASVS and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63N/A — Digital Identity GuidelinesPasskeys and recovery paths are governed by digital identity assurance and authenticators.
Recommendation — Use NIST SP 800-63B guidance to design phishing-resistant sign-in and secure recovery.
OWASP ASVSV6 — AuthenticationPasskey sign-in and recovery are authentication requirements, including fallback handling.
Recommendation — Verify authentication and recovery flows so lost-device cases do not break account access.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementRecovery codes, backup keys and restoration processes are authenticator lifecycle controls.
Recommendation — Manage authenticators so backup and recovery material is issued, stored and rotated safely.

Practitioner Guidance

What to verify: Confirm that every passkey-protected account has at least one recovery path that does not depend on the same lost device. Test the path before it is needed, because many recovery designs look complete until the first real restore attempt.

Decision rule: If the account protects anything operationally important, treat recovery codes, backup keys, and restore ownership as mandatory. If the account is low value, a simpler recovery flow may be acceptable, but it still needs to be documented and usable without guesswork.

Common mistake: Relying on a single platform sync path and assuming it is a full backup. Sync can preserve convenience, but it does not replace a documented restoration process when the whole device set is gone.

Practitioner takeaway: Passkeys reduce password risk, but they do not remove recovery risk, so the real control objective is resilient account restoration without reintroducing a weaker path than the one you replaced.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org