Okta User Account Lockout Triggered by Max Sign-In Attempts

Flags Okta user account lockouts triggered by exceeding the max sign-in attempts threshold.

FreeReviewedSigma · Medium · v4
Product
okta
Service
okta
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-09-12
Updated
2026-07-31

ATT&CK techniques

Impact
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

What it detects

Detects Okta system log events where a user account lockout occurs due to exceeding the maximum allowed sign-in attempts. This behavior matters because attackers may intentionally provoke lockouts to disrupt access or to test authentication defenses. The rule relies on Okta telemetry using the specific system log message indicating “Max sign in attempts exceeded.”

Related detections9 linkedT1531 — drag to rearrange
Suspicious Account Disable via net user active no (via process_creation)
AWS IAM SAML Provider Deletion via CloudTrail
Linux userdel Execution: User Account Deletion via userdel
Linux groupdel Executed to Delete a User Group
Windows Security Logoff Events (Event ID 4634/4647)
Windows PowerShell Script: Remove Account From Domain Admin Group via Remove-ADGroupMember
Google Cloud: Service Account Disabled or Deleted via IAM Audit Events
Azure Kubernetes Service Service Account Modified or Deleted Activity Log Events
AWS ElastiCache Cache Security Group Modified or Deleted via CloudTrail
Okta User Account Lockout Triggered by Max Sign-In Attempts
Pivot detection · T1531 · 9 related

Changelog

v4
  1. v4
    Candidate ingested via manual entry.2026-07-31
  2. v3
    Candidate ingested via manual entry.2026-07-31
  3. v2
    Candidate ingested via manual entry.2026-07-31
  4. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.