SmaiID
V1 · AAL2
SH

Devices

Device trust is earned, time-limited and revocable. A trusted device reduces friction; it never replaces authentication.

Registered devices

Every device that has held a SmaiID session.

Studio Laptop

SID-DEV-1A4C · Windows 11 · last seen Active now · trust expires in 24 days

Bound keyTrusted

Pixel — Personal

SID-DEV-88BE · Android 16 · last seen 2 hours ago · trust expires in 11 days

Bound keyTrusted

Hardware key (Konsmik ops)

SID-DEV-7710 · FIDO2 · last seen 5 days ago

Bound keyTrusted

Unrecognised Linux browser

SID-DEV-02F9 · Ubuntu · last seen Yesterday

Untrusted

Not yet enforced: Device registration, attestation and revocation require the device trust service.

How a device becomes trusted

Explicit, evidenced, expiring.

  1. 1Authenticate at AAL2 or higher on the device.
  2. 2Bind a credential to the device (passkey or hardware key).
  3. 3Confirm the device explicitly — trust is never assumed.
  4. 4Trust expires on a schedule and must be renewed.
  5. 5Any risk signal downgrades trust immediately.

Device-bound assurance

AAL3 requires a credential that cannot leave the device.

Synced passkeys satisfy AAL2. Device-bound passkeys and hardware keys satisfy AAL3 and are required for entity administration, wallet linking and recovery approval.