What it is
Multi-factor authentication (MFA) requires users to prove their identity with more than one kind of evidence: something they know (a password), something they have (a phone or security key) or something they are (a fingerprint or face check on their device). Stolen passwords alone are then not enough to take over an account.
Not all factors are equal. One-time codes sent by SMS or shown in an app can still be phished: a fake site asks for the code and relays it in real time. Passkeys and hardware security keys, built on the WebAuthn and FIDO2 standards, are phishing-resistant because the browser only releases a signed response to the genuine site.
When you need it
- Your application holds personal, financial or business-critical data.
- Staff access administrative functions or production systems.
- Customers, insurers or auditors expect MFA as a baseline control.
- You have seen credential stuffing or account takeover attempts.
How we approach it
We first decide where MFA should live. For workforce applications, enforcing it at the identity provider, such as Microsoft Entra ID or Okta, gives one consistent policy. For customer-facing applications, we build it into the application’s own sign-in.
We then choose factors by user group: passkeys or security keys for administrators, passkeys or authenticator apps for most users, and SMS only as a fallback where nothing else is practical. Enrollment is designed to be quick, with a prompt to register a second factor straight away.
Step-up authentication protects sensitive actions. A user who signed in earlier may be asked to verify again before changing payout details or adding a new administrator. Risk signals, such as a new device or an unusual location, can trigger extra checks.
Common pitfalls to avoid
- Weak recovery. If support resets MFA after a quick email, attackers will target support. Recovery needs identity verification.
- Exempting administrators. The accounts with the most power often get exceptions “for convenience”. They should have the strongest factors.
- Prompt fatigue. Constant push approvals train users to tap yes. Number matching and fewer, smarter prompts help.
- Forgetting non-browser access. Legacy protocols and API keys can bypass MFA entirely unless they are disabled or controlled.
- No logging. Failed and reset MFA events are valuable security signals and should be recorded and reviewed.