Skip to main content

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.

Use case
Updated

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

  1. Count denials

    The detection reads Okta System Log events stored in Cotool, counts denied pushes per user over 10 minutes, and emits users with 5 or more.[1]

  2. Check device and network

    The agent checks the user's enrolled devices and where the pushes came from. In Cotool's example, one enrolled device on a hotel network made the alert a false positive.[2]

  3. Look for an accepted push

    The agent looks for a successful sign-in, such as a user.session.start event, after the denials.[3][6]

  4. Respond

    If an attacker got in, the agent proposes revoking the user's Okta sessions and waits for approval.[2][4]

  5. Tune the threshold

    Cotool's GitOps example raises the threshold from 3 to 5 denials and excludes service accounts, with a 30-day backtest among the pull request checks.[1]

Example

MFA push fatigue over Okta logssql
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 >= 5

The 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

  • Revoking a user's Okta sessions is a state-changing action that can require approval in the app or in Slack.[4]
  • Threshold changes ship as a reviewed pull request.[1]

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

  1. Detection engineering (Cotool Detect) · accessed November 16, 2026
  2. Respond to every signal (Cotool Respond) · accessed November 16, 2026
  3. Changelog (Cotool docs) · accessed November 16, 2026
  4. AI SOC (Cotool) · accessed November 16, 2026
  5. Multi-Factor Authentication Request Generation, T1621 (MITRE ATT&CK) · accessed November 16, 2026
  6. Event types (Okta Developer) · accessed November 16, 2026

Related use cases

All use cases

Related reading

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo