I. Overview

%%{init: { 'theme': 'base', 'themeVariables': { 'edgeLabelBackground': '#fff' }}}%%
flowchart LR
    A["Password-based\nauthentication"] -- "Biometrics and public-key cryptography" --> B["Convenient, strong\nauthentication"]
    style A fill:#f9f9f9,stroke:#333,stroke-width:3px
    style B fill:#e1f5fe,stroke:#01579b,stroke-width:3px

Definition: FIDO (Fast IDentity Online) is an authentication standard that replaces password-based login with device-held biometric verification and public-key cryptography.

Features:
( Stronger Security ) Replaces passwords, which risk exposure, with biometric-based, public-key authentication — cutting off phishing and account-takeover attacks at the source
( Privacy Protection ) Biometric data is never sent to the server; it stays only within the device’s secure storage area, preventing leakage
( User Convenience ) Authenticates quickly through a simple action such as a fingerprint or facial scan, with no complex password to type

II. Mechanism & Components

A. FIDO Authentication Process (Registration & Authentication)

sequenceDiagram
    participant User as User (Client)
    participant Device as Authenticator
    participant Server as FIDO Server

    Note over Device: [Registration Phase]
    User->>Device: Provide biometric input
    Device->>Device: Generate private key, store in secure area (TEE)
    Device->>Server: Send and register public key

    Note over Device: [Authentication Phase]
    Server->>Device: Send challenge (random value)
    User->>Device: Provide biometric input
    Device->>Device: Sign challenge with private key (response)
    Device->>Server: Send signature value
    Server->>Server: Verify signature with registered public key

Detailed steps:

  • Registration: After biometric authentication on the device, the resulting public key is registered with the server (the private key stays in the device’s secure area, the TEE)
  • Authentication: The device signs the challenge sent by the server using the private key and returns the response
  • Verification: The server verifies the signature with the registered public key to confirm authentication success

B. Key Differences Across FIDO Standard Versions

CategoryFIDO 1.0 (UAF / U2F)FIDO 2.0 (WebAuthn)
Primary TargetMainly mobile app environmentsWeb browser and PC environments
UAFLogin using biometrics alone (Passwordless)-
U2FAn added security key on top of ID/PW (2nd Factor)-
Core TechnologyRequires a dedicated client appWebAuthn (W3C standard API), CTAP
ExtensibilityTied to a specific OS / deviceGeneral-purpose, browser-based authentication

III. Advanced Topics & Comparison

CategoryDetailsExpected Benefit
Biometric Data ProtectionBiometric data is never sent to the server and stays on-deviceBiometric data cannot leak even if the server is breached
Phishing PreventionDomain-binding technology blocks authentication on fake sitesBlocks man-in-the-middle (MitM) attacks and phishing at the source
PasskeySyncs FIDO credentials across multiple devicesSeamless authentication experience even after a device change

Last updated 18 Aug 2026, 00:00 UTC. history