Multifactor authentication (MFA)
Reviewed 2026-11-10
Sign-in that requires two or more kinds of proof, such as a password and a phone prompt. Not all MFA is phishing-resistant. Keep identity, access policy and resource permission separate. Check the source before choosing a control for your applications.
How it works
Sign-in that requires two or more kinds of proof, such as a password and a phone prompt. Not all MFA is phishing-resistant.
Identify the actor, the resource and the decision this term describes. Record which system makes that decision and which system enforces it.
A sign-in event, a policy decision and an application permission are not interchangeable. Test the relevant boundary rather than relying on a product label.
What Okta and Entra ID call it
This is a technical term, not a promise that both vendors use identical labels. The cited documentation supplies the terminology for its own implementation.
Use the linked comparison to locate the relevant product scope. Do not infer a vendor capability from a similar name alone.
Example
Consider an application access review as an illustrative exercise, not a customer story. Identify the person or service involved, the resource requested and the evidence needed.
Locate where multifactor authentication (mfa) affects that decision. Ask what would change if the identity, device or permission changed.
Write down the expected result before testing. Keep the observation separate from a vendor's description of the feature.