Identity & Access Management

Multi-Factor Authentication (MFA)

Add a second proof of identity to sign-in, favoring phishing-resistant passkeys and security keys, with risk-based prompts and safe account recovery.

  • Phishing-resistant factors

    Passkeys and hardware security keys based on the WebAuthn standard, which bind sign-in to the real site.

  • Authenticator apps

    Time-based one-time passwords and push approvals for broad device compatibility.

  • Step-up authentication

    Extra verification for sensitive actions such as changing bank details or exporting data.

  • Risk-based prompts

    Fewer prompts on known devices, more when sign-in looks unusual.

  • Secure recovery

    Backup factors and verified reset processes that do not become a back door.

  • Central or in-app

    MFA enforced at your identity provider, or built into the application where no provider is used.

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.

Frequently asked questions

Are SMS codes good enough?

SMS codes are better than a password alone, but they can be intercepted or redirected through SIM swapping. We recommend passkeys, security keys or authenticator apps and keep SMS only as a fallback where needed.

Should MFA live in our app or our identity provider?

For staff applications, enforce MFA at the identity provider so one policy covers everything. For customer-facing apps without an external provider, we build MFA into the application.

Will MFA annoy our users?

Passkeys are often quicker than typing a password, and remembering trusted devices reduces prompts. We tune the policy so friction appears where risk is highest.

What if a user loses their phone?

Users enroll a backup factor up front, and a verified recovery process covers the rest. We design that process as carefully as sign-in itself.

Let's build something great together

Ready to talk about custom software? Tell us about your project requirements and we will get back to you.