Push Notification-Based MFA
You'll learn how push-based authentication works, how to prevent MFA fatigue attacks, and why adding number matching strengthens approval flows.
How Push-Based Authentication Works
Push notification MFA sends an approval request directly to your authenticated device (usually a mobile app). When you try to log in, the server sends a push notification asking "Is this you?" You tap "Approve" or "Deny" in the app, and the authentication completes without typing codes.
The flow:
- You enter username/password on a website
- Server sends push notification to your registered phone
- You review the request in your authenticator app
- You approve or deny the login attempt
- Server grants or blocks access based on your response
The convenience factor: Unlike TOTP codes that expire in 30 seconds, push notifications let you authenticate with a single tap. No typing, no code rotation—just instant approval.
MFA Fatigue Attacks
The problem: Attackers with stolen passwords spam victims with dozens of push notifications, hoping you'll approve one by accident or just to stop the notifications. This social engineering tactic exploits notification overload and user frustration.
Number Matching and Context
Modern defenses add friction to prevent accidental approval:
-
Number matching: The login screen displays a 2-3 digit number. Your push notification asks you to select that same number from multiple choices. You must actively match numbers, not just tap "Approve."
-
Context display: The notification shows login details—location, IP address, browser type, timestamp. You can verify "Is this really me trying to log in from New York on Chrome?"
-
Rate limiting: Limit push notifications to prevent spam attacks (e.g., max 3 attempts per 10 minutes)
Key Takeaway: Push notification MFA provides excellent user experience, but must include number matching and contextual information to prevent MFA fatigue attacks where attackers overwhelm users with approval requests.