⚠️ WARNING THIS IS A EXPERIMENTAL DETECTION
We have not been able to test, simulate or build datasets for it, use at your own risk!
This search detects Okta login failures due to bad credentials for multiple users originating from the same ip address.
- Type: TTP
- Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud
- Last Updated: 2020-07-21
- Author: Rico Valdez, Splunk
- ID: 19cba45f-cad3-4032-8911-0c09e0444552
|T1078||Valid Accounts||Defense Evasion, Persistence, Privilege Escalation, Initial Access|
|T1078.001||Default Accounts||Defense Evasion, Persistence, Privilege Escalation, Initial Access|
`okta` outcome.reason=INVALID_CREDENTIALS | rename client.geographicalContext.country as country, client.geographicalContext.state as state, client.geographicalContext.city as city | stats min(_time) as firstTime max(_time) as lastTime dc(user) as distinct_users values(user) as users by src_ip, displayMessage, outcome.reason, country, state, city | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | search distinct_users > 5 | `multiple_okta_users_with_invalid_credentials_from_the_same_ip_filter`
Associated Analytic Story
How To Implement
This search is specific to Okta and requires Okta logs are being ingested in your Splunk deployment.
Kill Chain Phase
Known False Positives
A single public IP address servicing multiple legitmate users may trigger this search. In addition, the threshold of 5 distinct users may be too low for your needs. You may modify the included filter macro
multiple_okta_users_with_invalid_credentials_from_the_same_ip_filter to raise the threshold or except specific IP adresses from triggering this search.
source | version: 2