Signal desk

Tracking the forces shaping technology

distribution

Passkeys protect the login. Check your recovery route before losing your phone

A stronger sign-in method still needs a practical recovery plan. Know where your passkeys are kept, protect the account behind them and check each service's fallback before changing devices.

Android Credential Manager offering stored passkeys in Google Password Manager and Bitwarden, a QR-code option and a password-manager link.

Media credits, sources and reuse details ↓

You can unlock your phone in seconds. If it vanished tomorrow, which device or recovery route would let you back into your important accounts? That is a useful question to answer while the phone is still in your hand, not a reason to avoid a stronger way to sign in.

In its 23 April assessment, the UK's National Cyber Security Centre recommends passkeys where services support them, with two-step verification where they do not. That is the NCSC's security assessment, not a PING test or a promise that every part of an account is invulnerable.

Understand what you are keeping

The NCSC's public guide describes passkeys as a way to authenticate using your device's usual unlock method, such as a fingerprint or PIN. A credential manager creates and stores them and can synchronise them across trusted devices. Check your own manager's behaviour rather than assuming every passkey is available on every device you own.

Make a short account inventory: the service, the credential manager or device holding its passkey, and the official recovery instructions. This is a map of where to look, not a document for passwords, PINs or recovery codes. Keep sensitive recovery material only through the secure storage method appropriate to that service.

Protect the account behind the convenience

The NCSC identifies authentication protecting the synchronisation account as an important control. That means your planning should include the account used by your credential manager, not just the website you are trying to enter. Check its official security and recovery settings while you can still sign in.

Keep a borrowed device out of the setup

Google tells users to create passkeys only on devices they personally own and use. Its warning is specific: someone able to unlock that device can access the Google Account through the passkey, even after sign-out. Do not create one on a shared computer merely to make today's login easier.

For a work or school account, check the administrator's instructions before changing sign-in arrangements. Google notes that Workspace administrators may not permit a passkey-only sign-in. A personal-account tutorial is not permission to change an employer's controls, and this article does not tell you to bypass them.

Check the fallback before you need it

Google's lockout-prevention guide describes recovery information and additional sign-in options, including backup codes for two-step verification. It recommends a recovery email different from the Google sign-in address. Newly changed authentication or recovery factors can take up to seven days to take effect; setting something up is not proof that it is ready immediately.

Before replacing or resetting a phone, follow the provider's instructions to confirm the replacement sign-in route works. Keep the current trusted device available during that check. Do not delete every existing password, key or recovery method as a demonstration that you have moved on. If the result is unclear, stop and use the official support route rather than escalating changes.

For a lost device holding a Google passkey, Google's passkey help says to sign in from a device you can access and remove the lost device's passkey. Its 'Try another way' option returns to earlier sign-in choices. Other services have their own procedures; do not assume these exact controls exist everywhere.

Plan around your actual journey

For someone moving between the UK and an African country, include the practical questions: will you have the trusted device, can you reach the recovery address, and can your recovery number receive the messages your provider requires? Do not assume an office computer or borrowed phone is an equivalent substitute. This checklist establishes no country-specific service availability.

The useful finish is one account with an understood sign-in and recovery route, not a rushed reset of everything. Keep passwords and two-step verification where passkeys are unavailable, as the NCSC advises. For more on the systems that keep people connected, visit PING's Networks desk.

Sources and disclosures
Disclosure
Documentation-based personal-account guide, checked 8 October 2026, with AI-assisted research and drafting. PING has not accessed reader accounts, tested an account-recovery flow or measured security outcomes. Provider instructions take precedence; work and school accounts may have administrator restrictions. This is not an account-specific recovery service. Sources rechecked 2 November 2026; historical first-check dates remain as recorded.
Declared media rights
Licensed use; creator retains rights
Sources and method
The NCSC blog is published 23 April 2026; its CYBERUK announcement is discussed without inventing a separate event day. The NCSC public guide and two Google Help pages display no publication/update date in the retrieved content. All four sources were actually retrieved on 8 October. This is a current practical guide based on existing documentation, not a new passkey launch. NCSC security comparisons are attributed to its assessment, not PING testing. Sync behaviour and recovery depend on the credential manager and service; Google instructions are explicitly Google-specific. No universal recovery guarantee, unhackable-account claim or instruction to discard all passwords is made. We did not sign in, change authentication factors, create keys, submit recovery forms or inspect private data. The internal Networks link is a coverage destination, not an external factual authority. Rechecked 2 November 2026: the current NCSC guide/assessment and both Google Help pages were retrieved in full; their historical 8 October access receipts remain retained. No account, recovery-flow or security-outcome test was performed. Cover is an actual Android Credential Manager example captured 13 August 2025, not current recovery settings or a PING account. Source file: https://commons.wikimedia.org/wiki/File:Android_Credential_Manager_Conditional_UI_on_Android_screenshot_(cropped).webp ; licence: https://www.apache.org/licenses/LICENSE-2.0 . Screenshot is unchanged; Android Open Source Project software and VulcanSphere screenshot credit retained. The separate original video plan remains unrendered and unattached. Android Open Source Project; screenshot by VulcanSphere / Wikimedia Commons, Apache License 2.0. Unchanged. Cover: An Android Credential Manager example captured on 13 August 2025. It illustrates choosing a stored passkey, not a Google recovery-settings screen or a PING account test. Software: Android Open Source Project; screenshot: VulcanSphere / Wikimedia Commons, Apache License 2.0.

Reader comments

Comments are not open yet. When available, submissions will require free sign-in and editorial approval before appearing. PING does not promise a response.

Privacy information