Phone-based MFA for owners and finance staff: what to change before an approval prompt gets abused
Push-approval fatigue and phone-number takeover are different attacks on the same phone. The settings to change for owners and finance staff, in order.
A contractor approves one request too many
Uber’s own security update (first posted September 15, 2022, updated September 19) describes how an attacker got in. A contractor’s personal device had been infected with malware, and the attacker likely bought the contractor’s corporate password on the dark web. The password alone was not enough, because Uber required a second step. The attacker tried to sign in repeatedly, and each attempt sent the contractor a two-factor approval request. Uber’s account says the contractor eventually accepted one, and the attacker logged in and reached other employee accounts and tools including G-Suite and Slack.
That is approval fatigue. The attacker needs only a password and a person who taps Approve. A different attack uses the same phone: moving the owner’s phone number to a SIM the attacker controls, so text-message codes arrive at the wrong device. The first attack targets the person. The second targets the carrier. Owners and finance staff are worth both, because their accounts can move money and change bank details.
Why approve-only prompts and text codes are weak
NIST’s current identity guideline, SP 800-63B-4, speaks to both. In its section on out-of-band authentication (source), it says that approval-only methods, which can enable “authentication fatigue,” are no longer considered acceptable. It also says verifiers that send push notifications should limit how many are sent since the last success. For codes sent over the phone network (SMS and voice), it classes them as a restricted authenticator and tells verifiers to weigh risk indicators such as a SIM change or number porting before sending a secret. It states that out-of-band authentication is not phishing-resistant.
You are the customer, not the verifier, so your job is to turn on the controls the platforms already offer.
What to change, in order
1. Require number matching on push prompts. Microsoft’s documentation (source) says number matching is enabled for all Authenticator push notifications. The user sees a number on the sign-in screen and must type it into the app, so a stray tap does nothing. Check that staff run the current Authenticator version, since Microsoft says older versions fail to authenticate.
2. Show where the request comes from. Microsoft’s additional context setting adds the application name and the sign-in’s geographic location to each prompt, and it can be enabled for a chosen group. A finance person who sees an unfamiliar app name and a city they have never visited has a reason to deny. Microsoft also notes that users can modify the location their phone reports, so treat it as a hint, not proof.
3. Move owners and finance staff to passkeys or security keys. Microsoft calls passkeys phishing-resistant and says they cannot be replayed to a look-alike site, and it recommends FIDO2 security keys for users with elevated privileges while noting the cost of equipment and lost-key recovery (source). Apple’s account page (source) says that with security keys turned on, signing in takes the password plus a physical key or nearby trusted Apple device, and that these are the only ways in. Google likewise offers security keys as a second step, and says keys added before May 2023 may need removing before a passkey can be created on them (source).
4. Remove text messages as a fallback. Switching to a stronger method achieves nothing if account recovery still sends a code by SMS. For each owner and finance account, open the sign-in and recovery options and delete the phone-number method once the stronger one works. Keep two registered keys or passkeys so a lost one does not lock the person out.
5. Lock the phone number at the carrier. Verizon’s page (source) describes Number Lock as free, enabled in the My Verizon app or website, and available only to the account owner or an account manager. It stops a port-out from being processed until the lock is switched off. Other carriers offer comparable locks under different names; ask each one for its port-out and SIM-change protections and have the account owner turn them on. The tradeoff is the same everywhere: the lock must be removed to move a number legitimately.
6. Teach one rule. An approval request nobody started is not a glitch. The person denies it and tells the administrator the same day, because whoever sent it probably already has the password. The administrator resets that password and checks recent sign-ins.
Who does what
| Who | Task |
|---|---|
| Owner | Approves the change, holds the carrier account, registers two keys |
| Administrator | Turns on number matching and context, removes SMS methods, sets the report-and-reset rule |
| Finance staff | Register a passkey or key, deny and report unexpected prompts |
Sources
- Uber, security update (September 15, 2022; updated September 19, 2022): https://www.uber.com/newsroom/security-update/
- NIST SP 800-63B-4, authenticators: https://pages.nist.gov/800-63-4/sp800-63b/authenticators/
- Microsoft Learn, number matching in MFA push notifications (page updated October 21, 2026): https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-mfa-number-match
- Microsoft Learn, additional context in Authenticator notifications (page updated June 15, 2026): https://learn.microsoft.com/en-us/entra/identity/authentication/how-to-mfa-additional-context
- Microsoft Learn, passkeys (FIDO2) in Entra ID (page updated June 15, 2026): https://learn.microsoft.com/en-us/entra/identity/authentication/concept-authentication-passkeys-fido2
- Apple Support, security keys for Apple Account: https://support.apple.com/en-us/102637
- Google Account Help, passkeys and security keys: https://support.google.com/accounts/answer/6103523
- Verizon, unauthorized port-outs and Number Lock: https://www.verizon.com/about/account-security/unauthorized-port-outs