Azure AD possible MFA fatigue attack followed by successful login
Set up the azure integration.
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、
お気軽にご連絡ください。
Goal
Detects when multiple Azure AD multi-factor authentication (MFA) push notifications have been rejected or not responded to by a user, followed by a successful login.
Strategy
This rule allows you to monitor Azure AD sign-in logs and detect when multiple MFA push notifications have been rejected or not responded to by a user, followed by a successful login. Attackers may attempt to bypass MFA mechanisms and gain access to accounts by generating MFA requests sent to users. Bombarding users with MFA push notifications may result in the user finally accepting the authentication request.
Triage and response
- Speak with the user
{{@usr.id}} to understand the context of push rejections, and whether or not the push notifications were initiated by the user. - If the user did not initate the push notifications:
- Filter for the specific
@usr.id and @properties.status.additionalDetails:("MFA denied; user declined the authentication\" OR "MFA denied; user did not respond to mobile app notification") to highlight failed push notifications. Compare previous geo-locations, user-agents, and IP addresses for the user to determine if this is abnormal activity. - If it is believed to be malicious activity then disable the user, invalidate any active sessions, and rotate their credentials.
- Begin your organization’s incident response process and investigate.
