A backup FIDO2 security key can preserve access when your usual authenticator is unavailable, but only if the service supports it and you register it before you need it. Buying a spare does not automatically connect it to your accounts. NIST’s authentication guidance recommends maintaining separate ways to authenticate and confirming that newly added authenticators work. NIST authenticator lifecycle guidance
The practical goal is straightforward: losing one device should not leave you discovering your recovery options for the first time.
A spare key is not automatically a copy
The FIDO Alliance distinguishes device-bound passkeys from synced passkeys. Device-bound credentials stay with their authenticator; synced credentials can become available through a passkey provider across devices. Security keys can provide an additional access option when supported and enrolled. FIDO Alliance passkey overview
For a typical device-bound security-key setup, plan to register each physical key separately with each service. Think of the backup as another approved way into the account, rather than a duplicated household key that starts working immediately after purchase.
Our recommendation is to begin with accounts whose loss would interrupt access to others: primary email, an identity provider, or an administrative account. Then expand the plan according to your needs. Do not assume that support for passkeys on a phone also means the service accepts your external key.
Separate backup authentication from account recovery
There are two different situations to plan for. In the first, an enrolled alternative still lets you authenticate. In the second, you have lost control of the authenticators needed for the required access and must use the provider’s recovery process.
NIST treats account recovery as a distinct lifecycle event. It may involve recovery codes, recovery contacts, or renewed identity proofing, depending on the service and assurance requirements. Recovery can also involve delays and notifications. These are standards-level concepts, not a promise that every consumer website offers all of them. NIST recovery guidance
That distinction changes the question you should ask. “Can I recover this account?” is useful, but “Can I still sign in with an independently available authenticator?” may reveal a simpler route before recovery becomes necessary.
Build a small account-access inventory
Our recommended inventory does not contain passwords, PINs, private keys, or recovery codes. It records the operational facts you need:
- Which important accounts accept more than one authenticator?
- Which physical key or passkey provider is registered with each account?
- Where is the backup stored, and can you reach it when needed?
- When did you last verify the backup?
- Where are the service’s official recovery instructions?
- For a work account, which team owns access restoration?
Use neutral labels such as “daily key” and “backup key” where the service permits naming. A clear label helps when reviewing registered authenticators, especially after loss or replacement.
Consider a hypothetical traveler whose laptop and daily key are in the same stolen bag. A second key in that bag adds little availability. The lesson is to plan around shared loss scenarios, not simply count the number of devices purchased.
Verify the backup without creating a lockout
We recommend enrolling and checking the backup while the primary method is still available. Follow the service’s official process to add it, then use a fresh sign-in session to confirm that the backup itself can complete the intended authentication.
Be attentive to what actually authorizes the login. A pre-existing session, a phone approval, or a different saved credential may make a test appear successful without demonstrating that the spare key works.
Do not remove a functioning primary credential just to simulate a loss. Instead, keep it available while deliberately selecting the backup where the interface allows. Record the test date and account outcome, then store the backup separately.
For organizations, include the relevant application and device type in the check. A backup that works on a home computer may not answer the question of access from a managed workstation.
What should happen after a key is lost?
Use an available approved method or the provider’s recovery process to regain access, then follow its instructions for removing the missing authenticator. Google’s account guidance, for example, tells users to remove a passkey associated with a lost or stolen device from their account. Its instructions also distinguish manually created passkeys from automatically created Android credentials. Google’s passkey management guidance
Treat this as an example of why provider-specific instructions matter. Avoid assuming that deleting a local credential alone revokes every associated account session. Follow the service’s device and session guidance, and consult your organization’s security team for a work account or suspected compromise.
Once access is stable, our recommendation is to enroll a replacement, verify it, and update the inventory. Restoring access and restoring your backup arrangement are two separate completion steps.
Choose a backup around a tested workflow
Thetis FIDO2 security keys are options to evaluate when your service and devices support a physical authenticator. Confirm model capabilities, connections, and account policies before purchase or enrollment.
The useful outcome is not simply owning two keys. It is having two appropriately protected, registered, and tested access paths, with a clear next step if one becomes unavailable.
Sources checked October 1, 2026. This is a standards-informed practical guide with editorial recommendations, not a guarantee of recovery for every account.
