Comwil

Security

Passkeys, MFA and passwords: what small companies need

Passwords alone no longer protect accounts. How multi-factor authentication works, why passkeys resist phishing, and a practical rollout plan for small companies.

Published 8 November 20266 min readSecurity

Key takeaways

  • Turn on multi-factor authentication everywhere you can, starting with email, administrators and remote access.
  • Not all second factors are equal: text messages are the weakest, authenticator apps are better, passkeys and security keys resist phishing best.
  • Passkeys replace the password with a cryptographic key tied to a device and a fingerprint, face or PIN.
  • Plan recovery for lost phones and keep a password manager for what still needs a password.

Why passwords fail

People reuse passwords, choose guessable ones and type them into fake sites that look real. Attackers buy leaked passwords and try them on other services. A password on its own proves only that someone knows a secret, not that it is the right person.

Second factors, from weakest to strongest

  • Text message or voice codes. Better than nothing, but they can be intercepted or redirected through SIM swapping.
  • Email codes. Only as safe as the mailbox they go to.
  • Authenticator app codes. Much stronger, but a code can still be typed into a fake site.
  • App approvals with number matching. Harder to trick than a simple “approve” button, which people tap by habit.
  • Passkeys and security keys (FIDO2). Strongest against phishing, because they only work on the real website.

What passkeys are

A passkey is a pair of cryptographic keys. The private key stays on your device and never leaves it, or is synced through your platform account in encrypted form. The website stores only the public key. You unlock the private key with a fingerprint, face or device PIN.

Because a passkey is bound to the real website address, a fake site cannot use it. There is no shared secret to steal from a server or to type into a phishing page. Support is now common in major services, browsers and operating systems, though not yet everywhere.

A rollout plan that works

  • Step 1: require MFA for administrators, email and remote access.
  • Step 2: extend MFA to all staff with an authenticator app.
  • Step 3: offer passkeys or security keys where your services support them, starting with administrators and finance.
  • Step 4: provide a company password manager for everything that still uses passwords, and ban shared spreadsheets of passwords.
  • Step 5: define recovery: how someone who lost a phone proves who they are, and how access is restored.
  • Step 6: retire text-message codes where better options exist.

What to watch out for

  • Prompt bombing. Attackers trigger repeated approval requests until a tired user taps yes. Number matching helps.
  • Help desk impersonation. Attackers phone the support line pretending to be an employee. Verify identity before resetting anything.
  • Shared accounts. MFA works best when each person has their own account.
  • Lost or replaced devices. Keep an up-to-date list and remove old devices from accounts.

MFA is the first step of the plan in zero trust for mid-sized companies: the first 90 days. Our security services and IT support can help with the rollout.

Let’s talk about your IT

Tell us what you need. We will come back with a clear proposal and a named contact.