Synced Passkey
A synced passkey is a passkey that a passkey provider, such as a platform keychain or password manager, copies across the user's devices through a cloud service; a device-bound passkey never leaves the single device or security key that created it. These are the FIDO Alliance's terms for the two when the distinction matters.
Both kinds are phishing-resistant, because both are bound to the site's origin. The difference is custody: a synced passkey survives a lost phone and follows the user to a new device, which is what drives consumer adoption (the FIDO Passkey Index 2026 found passkeys in 36% of sign-ins at participating services), but its security also depends on the sync account and every endpoint the key lands on, as Unit 42's research extracting Google synced passkey keys showed. FIDO says device-bound passkeys on hardware security keys offer the highest assurance and meet the most stringent compliance requirements, so the usual split is synced passkeys for customers and most staff, and device-bound passkeys for administrators and regulated access, in line with NIST SP 800-63B-4, which accepts syncable authenticators at AAL2 but requires non-exportable keys at AAL3.
See also: passkey, phishing-resistant MFA, AAL, implementing passkeys in the enterprise
Related on Start with Identity
- GlossaryWebAuthn
A W3C standard browser API for public-key authentication. WebAuthn is the protocol used by passkeys and FIDO2 security keys. The relying party server stores the
- CVEStrongKey FIDO Server credential-type confusion, passkey bypass
StrongKey FIDO Server 4.10.0-4.15.0 confused discoverable and non-discoverable credentials. An attacker can complete passkey authentication as the victim. High.
- GlossaryFederation Assurance Level (FAL)
NIST 800-63C levels describing how strongly a federated login protects the assertion an identity provider (IdP) sends to a relying party (RP). FAL1: the IdP sig
- GlossaryFIDO2
FIDO2 is a set of specifications from the FIDO Alliance plus W3C. It combines WebAuthn (the browser API) with CTAP (the client-to-authenticator protocol) to ena
- CVEWindows stores WebAuthn assertions in cleartext event logs
The Windows Event Logging Service wrote WebAuthn assertions in the clear, readable by unprivileged or remote users. SpecterOps / Grafnetter chained it at Black
- GuideIdentity Federation Implementation Guide: Protocols, Trust, and Cross-Domain SSO
A step-by-step guide to implementing identity federation covering SAML, OIDC, and WS-Federation protocols, trust relationship configuration, attribute mapping,