Skip to content
IT security

Multi-Factor Authentication (MFA)

Updated

Multi-factor authentication (MFA) requires evidence from more than one type of authentication factor, such as possession of an authenticator plus a PIN or biometric verification. It makes stolen passwords less useful. MFA methods differ substantially, and phishing-resistant methods offer stronger protection against deceptive sign-in flows than reusable codes or approval prompts.

watch icon 2 min. read

What do I need to know about Multi-Factor Authentication (MFA)?

  • Adding a second password is not the same as adding a different authentication factor.
  • Unexpected approval prompts should be denied and reported; repeated prompts can be an attack signal.
  • Recovery procedures and fallback methods can weaken an otherwise strong deployment.
  • Account security also depends on devices, sessions, application permissions, and administrative practices.

An illustrative example

A user receives an approval prompt while not signing in. Instead of approving it to stop the interruption, the user reports it. The identity team checks attempted access and recovery settings. The event becomes a useful detection signal because the organization made reporting easier than dismissing the problem.

Practical checks

  • Inventory accounts and workflows, prioritizing administrative access and sensitive business roles.
  • Deploy supported phishing-resistant authentication where feasible and test enrollment and recovery.
  • Monitor unexpected prompts and method changes, and document how lost authenticators are replaced securely.

Five FAQs about Multi-Factor Authentication (MFA)

Is any MFA better than a password alone?

In general, MFA improves protection, but methods offer different resistance to phishing and interception. Choose the strongest supported method and evaluate recovery paths too.

Are passkeys phishing-resistant?

Properly implemented FIDO/WebAuthn passkeys are designed to bind authentication to the legitimate service. Security still depends on the account’s broader configuration, recovery, and device protection.

Should I approve an unexpected prompt?

No. Deny it and report it through your organization’s process. Do not approve a request simply because someone calling you claims to be IT support.

Does MFA prevent malicious app consent?

Not by itself. A user may authenticate legitimately and then grant an unsafe application permissions. Application-consent policies address a different decision.

What if a service does not support strong MFA?

Document the gap, reduce exposure through supported compensating controls, and plan an upgrade or alternative. Do not silently treat that service as equally protected.

Sources and further reading

CISA: Require multifactor authentication · CISA: Implementing phishing-resistant MFA

Related terms

Account Takeover (ATO) · Adversary-in-the-Middle (AiTM) Phishing · Credential Phishing