The Case for Local-First Authentication

Technical Introduction

Authentication architecture generally falls into two paradigms: cloud-synchronized and local-first. Over the past decade, the industry heavily favored cloud-synchronization for convenience, allowing users to access Time-Based One-Time Passwords (TOTP) and vault contents from any device. However, this convenience relies on expanding the trust boundary to include third-party infrastructure.

Problem Framing

When a credential manager syncs to the cloud, it inherently creates a single point of failure. While the data is (usually) encrypted locally before transit, the ciphertext resides on external servers. If those servers are compromised, the attacker acquires the encrypted vault. The attacker can then execute offline brute-force attacks against the derivation function without rate-limiting or detection.

Architectural Explanation

A local-first architecture fundamentally restricts the trust boundary to the physical device.

In a local-first system, the cryptographic vault is generated, encrypted, and stored entirely within the device's persistent storage. Decryption keys are derived on the device's processor, often protected by hardware-backed storage like a Secure Enclave or Keystore. The application does not require a persistent network connection, ensuring offline survivability—meaning authentication cannot fail due to network partitioning or DNS attacks.

Real-World Risks

The primary risk in a cloud-synchronized model is the mass-exfiltration of ciphertext. In a local-first model, the primary risk shifts to physical device compromise or catastrophic data loss.

If a user loses a local-first device and has not created an encrypted backup, the credentials are unrecoverable. This shifts responsibility to the user, who must manage their own disaster recovery. For enterprise deployments, this tradeoff is often preferred, as it ensures corporate credentials cannot be exfiltrated via the authenticator's network layer.

Glossary Concepts

• TOTP (Time-Based One-Time Password): An algorithm that computes a one-time password from a shared secret key and the current time.
• Ciphertext: Encrypted text transformed from plaintext using an encryption algorithm.
• Local Trust Boundary: An architectural concept where security assumptions do not extend beyond the physical hardware of the host device.
• Key Derivation Function (KDF): A cryptographic hash function that derives one or more secret keys from a master value, designed to be computationally expensive to thwart brute-force attacks.