MFA fatigue detection
How an AI SOC detects MFA push fatigue: count denied Okta Verify pushes per user, then check the device, network, and any sign-in that followed.
The short answer
MFA fatigue detection looks for repeated push prompts meant to wear a user down until they approve one. Cotool's example detection counts denied Okta Verify pushes per user over 10 minutes and flags users with 5 or more, and a response agent investigates each hit.[1][5]
The problem
Adversaries holding valid credentials may repeat login attempts to bombard a user with MFA pushes, SMS messages, and calls until the user accepts.[5]
Okta logs this differently by pipeline: classic orgs log user.mfa.okta_verify.deny_push, while Identity Engine orgs log user.authentication.auth_via_mfa with reason INVALID_CREDENTIALS.[6]
How an AI SOC handles it
Example
SELECT actor_id, COUNT(*) AS denies
FROM cotool_logs.okta
WHERE event_type = 'user.mfa.okta_verify.deny_push'
AND ts > now() - INTERVAL 10 MINUTE
GROUP BY actor_id
HAVING denies >= 5The query behind Cotool's example detection. Identity Engine orgs should match user.authentication.auth_via_mfa with reason INVALID_CREDENTIALS instead.[1][6]
What people approve
How Cotool handles it
- Cotool maps its detection suite onto MITRE ATT&CK, prioritizes coverage gaps, and creates new detections for missing techniques.[1]
Integrations used
Sources
- Detection engineering (Cotool Detect) · accessed November 16, 2026
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- Changelog (Cotool docs) · accessed November 16, 2026
- AI SOC (Cotool) · accessed November 16, 2026
- Multi-Factor Authentication Request Generation, T1621 (MITRE ATT&CK) · accessed November 16, 2026
- Event types (Okta Developer) · accessed November 16, 2026


