Cap MFA push bombing. An attacker with a user's password triggers repeated second-factor prompts, hoping the user approves one to stop the noise. Lidar's mfa_fatigue monitor surfaces this against a single subject so you can step in before a prompt is approved.
What you use
- The Lidar
mfa_fatiguemonitor (detection:mfa_fatigue challenges:>4 window:30m), correlated by subject. - Optional: Bot protection v3 on
mfa_verifyto add a silent score to the challenge step.
Setup
- Confirm Lidar access is approved for the environment.
- Under Lidar > Monitors, enable
mfa_fatigue. The defaultchallenges:>4 window:30mis a starting point; lowerchallenges:for sensitive accounts or raise it if your UX legitimately retries MFA several times. - If you want a bot score on the challenge itself, enable reCAPTCHA v3 on
mfa_verifyunder Authentication > Add-ons. v3 only;mfa_verifycannot render a visible checkbox.
Verify
- In dev, trigger MFA for one user more times than the
challenges:floor within the window: a Signal appears against that subject, deduped byai:mfa_fatigue:<subject>:<windowStart>. - Confirm a user retrying MFA two or three times does not fire; the monitor keys on volume, not single retries.
- Triage the Signal in Lidar > Signals; suspending the user or rotating keys invalidates outstanding sessions on the next
userinfocheck.
Related
- MFA: the TOTP second factor this recipe protects.
- Lidar concepts: subject-keyed correlation and dedup.
- Security: session revocation and key rotation.