Beyond Passwords a plain-language security briefing

✧ A plain-language security briefing ✧

Beyond Passwords

Why passwords fail, why MFA matters, why SMS codes stopped being safe, and how passkeys and security keys fix it.

β†’ or Space next Β· ← back Β· F fullscreen Β· B blank screen Β· presenter clickers work too

A password is a shared secret

You know it. The website keeps a copy (scrambled, if you are lucky). Anyone who learns it, becomes you.

How accounts actually get taken

🎣

Phishing

A convincing copy of a login page. You type, they collect. Still the number one way in.

♻️

Credential stuffing

Passwords leaked from one site get tried on every other site by bots. Reuse turns one breach into many.

πŸ€–

Guessing at scale

Not your dog's name. Automated lists: Summer2026!, Azerty123…

🦠

Malware

A keylogger on an infected machine records everything typed, passwords included.

Almost none of this is aimed at you personally. It is automation, running at internet scale, looking for the easiest doors.

MFA: one proof is not enough

Multi-factor authentication means proving who you are with two different kinds of proof.

🧠

Something you know

Password, PIN

πŸ“±

Something you have

Phone, security key

πŸ‘€

Something you are

Fingerprint, face

A password plus a security question is not MFA: that is the same kind twice. The point of MFA: a stolen password alone no longer opens the account.

>99.9% of automated account-takeover attempts are blocked by having MFA on (Microsoft, 2019)
100% of automated bots, bulk phishing and targeted attacks in Google's study were stopped by security keys (Google & NYU, 2019)

Not every second factor is equal

πŸ”

Security keys & passkeys

Phishing-resistant by design. The domain check is done by cryptography, not by your eyes.

πŸ”’

App codes (TOTP) & push prompts

No phone-network risk. But codes and prompts can still be phished and relayed in real time.

πŸ“©

SMS & voice-call codes

Better than nothing. But the number can be stolen, the network can be tapped, and the code can be relayed.

Every rung beats no MFA at all. The jump that matters is the top one.

SIM swap: your number can be taken over

A phone number is not really something you have. It is something the phone company lends you. And they can be talked into lending it to someone else.

  1. Collect. The attacker gathers your details from leaks and social media.
  2. Impersonate. They call your carrier: β€œLost my phone, please move my number to this new SIM.” Sometimes it is a bribed insider instead.
  3. Take over. Your phone drops to β€œno service”. Theirs now receives your calls and texts.
  4. Cash in. β€œReset password via SMS”. Every code now flows to the attacker.

Also: cancelled numbers get recycled and handed to strangers, along with any account still tied to them.

The network behind SMS was never built for secrets

SMS still beats having no MFA at all. But it is the floor, not the goal.

The attack that beats most MFA: the live relay

Everything is forwarded live, in both directions.

The fix: stop sending secrets at all

Security keys and passkeys use a key pair instead of a shared secret.

πŸ”‘

Private key

Created and kept inside your device. It never leaves. Not even you can read it out.

πŸ”“

Public key

Given to the website. It can only verify, never sign in. Like a bouncer holding a photo of your face: enough to recognise you, useless for becoming you.

  1. The site sends a fresh, one-time challenge.
  2. Your device signs it with the private key.
  3. The site checks the signature with the public key. Done.

Nothing reusable crosses the wire. Nothing secret sits on the server. A breached site spills keys that can only ever check, never open.

Why phishing simply stops working

Phishing works because humans check domains with tired eyes.
Passkeys check them with cryptography, which never skims, never rushes, and is not impressed by a convincing logo.

Security keys: the dedicated tool

Passkeys: the same protection, no extra hardware

Side by side

Rows starting with + keep the password and add a second factor on top. Only the last row removes the password entirely.

Method Phishing-resistant No shared secret on the server Immune to SIM swap & SS7 Nothing to remember
Password only βœ— βœ— n/a βœ—
+ SMS code βœ— βœ— βœ— βœ—
+ App code (TOTP) βœ— βœ— βœ“ βœ—
+ Push prompt βœ— ** βœ— βœ“ βœ—
+ Security key βœ“ ~ * βœ“ βœ—
Passkey (no password) βœ“ βœ“ βœ“ βœ“

* not the key's doing: a security key shares no secret itself. The ~ points at the password still sitting next to it on the server. Use the same key without a password (it then holds a passkey) and the bottom row applies.   ** number matching stops push bombing, but not the live relay.

What to do, starting today

  1. Turn on MFA everywhere. Any MFA beats none. Attackers pick unlocked doors first.
  2. Prefer passkeys wherever they are offered: Google, Microsoft, Apple, GitHub, PayPal…
  3. No passkey option? Use an authenticator app, not SMS.
  4. Keep SMS as a last resort only, and where possible remove your phone number as a recovery method. Recovery is the back door.
  5. Password manager plus a unique password for every site that still needs one.
  6. Protect the mailbox above everything. Email resets all other accounts. It deserves a passkey or a security key.
  7. Admins and likely targets: two hardware security keys and phishing-resistant MFA as policy, not as a suggestion.

Honest limit: passkeys stop phishing, they do not stop malware already on your machine. Updates still matter.

The whole story in three lines

Questions?

Sources: Microsoft identity security research (2019) Β· Google & NYU account-hygiene study (2019) Β· NIST SP 800-63B Β· documented SS7 banking attacks, Germany (2017) Β· Uber breach post-mortems (2022) Β· FIDO Alliance / W3C WebAuthn specifications.