Why the default is flipping
Passkeys remove the shared-secret problem at the root: the private key never leaves the user's device, and phishing gains little because the credential is bound to the relying party id. With cross-platform sync now stable, products can make passwordless the first-choice flow rather than an advanced setting.
Rollouts still fail in familiar ways. The two classics are blocking users whose device support is poor — never ship passkeys without a conventional fallback — and treating account recovery with a whole different trust model than sign-in.
A responsible rollout sequence
- Ship passkeys as opt-in for existing users while new accounts get passwordless first.
- Keep one canonical identity server flow; do not fork logic between the password and passkey paths.
- Define recovery before launch: verified recovery contacts now reset a passkey, not just a password.
- Track sign-in success rates per device class and expand autopromotion only when support is high.
Operationally, the change is small. The standards work in the browser vendors' WebAuthn implementations and the server libraries that verify WebAuthn assertions have matured to the point that a two-sprint engineering team can bring production passkey support end to end.MDN Web Authentication API documentation
Further reading
Building a product in this space?
MORE FROM THE NEWSROOM
Related news
CybersecurityMalicious Optimizely Scripts Reached 178 Organizations, Exposing Website Visitors to Data Theft
A malicious JavaScript campaign distributed through Optimizely Web reached visitors across 178 organizations, according to security researcher Scott Helme. The payload included cryptocurrency address substitution, payment-card skimming, cookie theft and iOS exploit delivery mechanisms, highlighting the security risks associated with trusted third-party website scripts.
CybersecurityUber Driver Information Exposed After Fireworks AI Vendor Breach, State Filings Reveal
Uber has confirmed that personal information belonging to drivers was accessed through compromised credentials at a third-party technology provider identified as Fireworks AI. Public breach notices and independent reporting identify at least 7,870 affected individuals across Massachusetts, South Carolina and Rhode Island, with additional state notifications still being assessed.
CybersecuritySignDrop Windows Zero-Day Exposes Local SYSTEM Privilege-Escalation Path; Microsoft Investigates
Security researcher Abdelhamid Naceri has disclosed SignDrop, a Windows privilege-escalation vulnerability involving the Common Log File System and Microsoft Defender. A public proof of concept demonstrates a path from an existing local user account to SYSTEM privileges, although Microsoft says Defender detects and blocks the associated exploit behavior and that it has not observed exploitation in the wild.
