Name:Okta Account Lockout Events id:62b70968-a0a5-4724-8ac4-67871e6f544d version:3 date:2024-10-17 author:Michael Haag, Rico Valdez, Splunk status:deprecated type:Anomaly Description:**DEPRECATION NOTE** - This search has been deprecated and replaced with `Okta Multiple Accounts Locked Out`. The following anomaly will generate based on account lockout events utilizing Okta eventTypes of user.account.lock.limit or user.account.lock. Per the Okta docs site, this event is fired when a user account has reached the lockout limit. The account will not auto-unlock and a user or client cannot gain access to the account. This event indicates an account that will not be able to log in until remedial action is taken by the account admin. This event can be used to understand the specifics of an account lockout. Often this indicates a client application that is repeatedly attempting to authenticate with invalid credentials such as an old password. Data_source:
search:`okta` eventType IN (user.account.lock.limit,user.account.lock) | rename client.geographicalContext.country as country, client.geographicalContext.state as state, client.geographicalContext.city as city | stats count min(_time) as firstTime max(_time) as lastTime values(src_user) by displayMessage, country, state, city, src_ip | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `okta_account_lockout_events_filter`
how_to_implement:This analytic is specific to Okta and requires Okta logs to be ingested. known_false_positives:None. Account lockouts should be followed up on to determine if the actual user was the one who caused the lockout, or if it was an unauthorized actor. References: -https://developer.okta.com/docs/reference/api/event-types/#catalog -https://developer.okta.com/docs/reference/api/event-types/?q=user.account.lock drilldown_searches:
: tags: analytic_story: - 'Suspicious Okta Activity' asset_type:Infrastructure confidence:50 impact:50 message:The following user $src_user$ has locked out their account within Okta. mitre_attack_id: - 'T1078' - 'T1078.001' observable: name:'src_ip' type:'IP Address' - role: - 'Attacker' product: - 'Splunk Enterprise' - 'Splunk Enterprise Security' - 'Splunk Cloud' required_fields: - '_time' - 'displayMessage' - 'client.geographicalContext.country' - 'client.geographicalContext.state' - 'client.geographicalContext.city' - 'src_ip' - 'src_user' risk_score:25 security_domain:access
