ID | Technique | Tactic |
---|---|---|
T1078 | Valid Accounts | Defense Evasion |
T1078.001 | Default Accounts | Initial Access |
Detection: Okta Account Lockout Events
DEPRECATED DETECTION
This detection has been marked as deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported. If you have any questions or concerns, please reach out to us at research@splunk.com.
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.
Search
1`okta` eventType IN (user.account.lock.limit,user.account.lock)
2| rename client.geographicalContext.country as country, client.geographicalContext.state as state, client.geographicalContext.city as city
3| stats count min(_time) as firstTime max(_time) as lastTime values(src_user) by displayMessage, country, state, city, src_ip
4| `security_content_ctime(firstTime)`
5| `security_content_ctime(lastTime)`
6| `okta_account_lockout_events_filter`
Data Source
No data sources specified for this detection.
Macros Used
Name | Value |
---|---|
okta | eventtype=okta_log OR sourcetype = "OktaIM2:log" |
okta_account_lockout_events_filter | search * |
okta_account_lockout_events_filter
is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
Annotations
Default Configuration
This detection is configured by default in Splunk Enterprise Security to run with the following settings:
Setting | Value |
---|---|
Disabled | true |
Cron Schedule | 0 * * * * |
Earliest Time | -70m@m |
Latest Time | -10m@m |
Schedule Window | auto |
Creates Risk Event | True |
Implementation
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.
Associated Analytic Story
Risk Based Analytics (RBA)
Risk Message | Risk Score | Impact | Confidence |
---|---|---|---|
The following user $src_user$ has locked out their account within Okta. | 25 | 50 | 50 |
References
-
https://developer.okta.com/docs/reference/api/event-types/#catalog
-
https://developer.okta.com/docs/reference/api/event-types/?q=user.account.lock
Detection Testing
Test Type | Status | Dataset | Source | Sourcetype |
---|---|---|---|---|
Validation | Not Applicable | N/A | N/A | N/A |
Unit | ✅ Passing | Dataset | Okta |
OktaIM2:log |
Integration | ✅ Passing | Dataset | Okta |
OktaIM2:log |
Replay any dataset to Splunk Enterprise by using our replay.py
tool or the UI.
Alternatively you can replay a dataset into a Splunk Attack Range
Source: GitHub | Version: 3