Skip to content
Start with Identity
Authentication

Number Matching

Number matching is a push MFA design in which the sign-in screen shows a short number and the user must type that number into the authenticator app to approve, instead of tapping a plain Approve button. It stops blind approval of prompts the user did not start, which is the mechanism behind MFA fatigue and push bombing (MITRE ATT&CK T1621).

Microsoft documents that number matching is now enabled for all Microsoft Authenticator push notifications, including MFA, self-service password reset and the AD FS and NPS integrations, and it is not supported on wearable devices. The limit is important: number matching is still phishable. A real-time phishing proxy shows the victim the genuine number from the real sign-in page, and the victim types it in. NIST SP 800-63B-4 says authenticators that involve manual entry of an output "SHALL NOT be considered phishing-resistant", so number matching is an interim control on the way to passkeys or security keys. The 2022 Uber incident in the Identity Breach Database is the case usually cited for why plain push approval was not enough.

See also: MFA fatigue and push bombing, phishable MFA, phishing-resistant MFA, Microsoft Authenticator, MFA matrix

Last reviewed By SWI Community TeamSuggest a correctionHow we research