Free — no signup required

Introduction: Why Passwords Must Die

3 min read

The Weakest Link

Think of a password like a secret handshake you share with a bouncer. The problem is you have to use the same handshake at hundreds of different clubs, you write it on a sticky note so you don't forget, and every club keeps a copy of it in a filing cabinet. If any one of those clubs gets robbed, the thief now knows your handshake everywhere.

For 50 years, the "Username + Password" model has been the dominant authentication standard. It is also the single biggest security liability in modern computing. The failure modes are structural, not behavioral — no amount of user education fully fixes them:

  • Credential reuse: Studies consistently show the majority of users reuse passwords across multiple services. When one service is breached, attackers run "credential stuffing" attacks — automatically trying the stolen username/password pair against banks, email providers, and corporate VPNs.
  • Phishing: If a user types their password into a convincing fake website, the attacker has it. The password is a shared secret — once the user reveals it, the attacker has everything they need. There is no cryptographic protection.
  • Server-side breaches: Servers must store something to verify your password — typically a salted hash. When a server is compromised, millions of these hashes are stolen and cracked offline using GPU clusters. The 2012 LinkedIn breach exposed 117 million password hashes; most were cracked within days.
  • Phishing-resistant 2FA is rare: SMS-based two-factor authentication (2FA) is better than nothing, but it is vulnerable to SIM-swapping attacks (where an attacker convinces a carrier to transfer your phone number) and real-time phishing proxies that relay the OTP before it expires.

The Passwordless Revolution

Modern Authentication is not a minor improvement to the password model — it is a replacement. The goal is to remove the shared secret entirely and replace it with cryptographic proof that only your physical device can produce.

This movement is driven by the FIDO Alliance (Fast Identity Online), a consortium founded in 2012 and now including Google, Apple, Microsoft, Amazon, and hundreds of other organizations. The FIDO Alliance produces open standards that define how devices and servers can authenticate users without ever transmitting a secret. The result is authentication that is simultaneously more secure and more convenient — users tap a fingerprint sensor instead of typing a 16-character password.

The key insight is that modern consumer hardware — every iPhone since 2013, every Android flagship, every laptop with Windows Hello — already contains a dedicated security chip capable of generating and protecting cryptographic keys. FIDO2 and WebAuthn are the standards that put that hardware to work for authentication.

Interview Tip

Interviewers frequently ask: "What's the difference between FIDO2, WebAuthn, and Passkeys?" A strong answer: FIDO2 is the overarching standard from the FIDO Alliance. WebAuthn is the W3C web API specification that is part of FIDO2 — it defines how browsers talk to authenticators. Passkeys are a specific implementation of FIDO2 credentials that adds cloud sync, solving the lost-device problem. They are layered: Passkeys build on WebAuthn, which implements FIDO2.

This is one of 18 chapters

Every chapter is free — Kubernetes, Terraform, SRE, distributed systems, and more — with fast daily review built in.

Sign up free