| Passkeys render two‑factor authentication unnecessary | 1.125 |
| Device‑provided security prevents users from leaking passkey secrets, even if they misunderstand how it works | 0.863 |
| Phishing resistance of passkeys is achieved by scoping credentials to a domain | 0.813 |
| FaceID or fingerprint biometrics can be used with passkeys to log in without remembering anything across all devices in the same ecosystem | 0.688 |
| Chrome’s password manager and Apple’s ecosystem tightly integrate passkeys, enabling seamless use across a user’s devices | 0.625 |
| A default login method must be able to function when a user's phone is dead or stolen; passkeys currently may not meet that requirement. | -0.500 |
| When a passkey is lost or a user needs to recover an account, most websites still provide a password or SMS code as a fallback, so the presence of these weak fallback mechanisms undermines the phishing‑resistance that passkeys claim to offer and means users maintain both strong and weak authentication methods simultaneously, adding complexity without eliminating the weak link. | -0.500 |
| Passkeys use biometric authentication (face‑ID or fingerprint scanning) that users recognize from Apple Pay or unlocking their phone, making the authentication experience familiar | 0.250 |
| Magic links can serve as a fallback authentication method but carry serious security risks | -0.250 |
| Magic links should ideally be combined with two‑factor authentication when a shared secret is required for security | -0.250 |
| The WebAuthn protocol has had a few iterations and is ready for deployment | 0.250 |
| Passkeys are tied to specific hardware or a vault that syncs across devices, so loss of that device can lock a user out. | -0.250 |
| A passkey can be considered equivalent to using a secure hardware token like YubiKey | 0.250 |