Three settings to help protect against MFA fatigue attacks

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Workforce Identity Articles
2 min read
L4 Transporter
No ratings
If you are using the Idira Identity mobile app for authentication and you do not have FIDO2 authentication options configured, here are three settings to help protect against MFA bombing or MFA fatigue attacks.
 

Steps

Enable Number Matching in the Idira Identity mobile app

Go to Endpoint Policies > Common Settings > Mobile Settings > Security Settings > Require number matching for mobile authenticator to prevent accidental approvals and select Yes.
This setting will help prevent the user from accidentally allowing access to an attacker. The user will be presented with three numbers to click. The correct number to click on the phone must match the number displayed on the login screen.
https://docs.cyberark.com/Product-Doc/OnlineHelp/Idaptive/Latest/en/Content/CoreServices/UsersRoles/...

ka3Ht000000Ul6jIAC__eid=ka3Ht000000Ul6j&feoid=00N2J000009R3kv&refid=0EMHt0000061L31.png

Enable CAPTCHA

Go to Settings > Authentication > Security Settings > CAPTCHA Settings

Set the number lower than the lockout threshold, like 2. So, after two failed or denied login attempts, the user will be prompted with a CAPTCHA challenge to help block programmatic attacks.
https://docs.cyberark.com/Product-Doc/OnlineHelp/Idaptive/Latest/en/Content/CoreServices/Authenticat...
 

Set a temporary lockout threshold

  1. Go to Core Services > Policies and select the relevant policy. Then go to User Security Policies > Password Settings > Capture Settings.
  2. For Maximum consecutive failed login attempts allowed within window, enter a number that is:
    1. Higher than the CAPTCHA threshold,
    2. High enough to give the end user a chance to login in event of accidental failed login attempts.
    3. But low enough to minimize the risk of MFA attack success.
  3. Select the serial button Count all failed login attempts to include denied push notifications and other failed MFA challenges. Click Save.
Once this threshold has been reached, the user will still receive notifications, but the Idira Identity mobile app will temporarily lock and prevent the user from acknowledging further push notification attempts.
                  ka3Ht000000Ul6jIAC__eid=ka3Ht000000Ul6j&feoid=00N2J000009R3kv&refid=0EMHt0000061L4S.png

https://docs.cyberark.com/Product-Doc/OnlineHelp/Idaptive/Latest/en/Content/CoreServices/UsersRoles/...

Expected results when:
CAPTCHA is set to 2.
Temporary lockout is set to 3.

Attempt 1 > User clicks Deny
Attempt 2 > User clicks Deny
Attempt 3 > Attacker receives CAPTCHA > User clicks Deny
Attempt 4 > Attacker receives CAPTCHA > User’s mobile app is temporarily locked
 

Use FIDO2 Authentication methods

The best way to prevent against MFA bombing attacks so the user does not receive any 2FA/MFA challenges at all and can’t be social engineered into granting access to an attacker.
Enable FIDO2 enrollment https://docs.cyberark.com/Idaptive/Latest/en/Content/CoreServices/Authenticate/U2FAuth.htm
Instructions for end users to enrolling FIDO2 https://docs.cyberark.com/Idaptive/Latest/en/Content/UserPortal/UseU2FAuth.htm

 
Rate this article:
  • 1042 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 12:00 PM
Updated by: