WARNING THIS IS A EXPERIMENTAL object
We have not been able to test, simulate, or build datasets for this object. Use at your own risk. This analytic is NOT supported.
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
Kill Chain Phase
- CIS 16
1 2 3 4 5 6 7 `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`
The SPL above uses the following Macros:
Note that multiple_okta_users_with_invalid_credentials_from_the_same_ip_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.
How To Implement
This search is specific to Okta and requires Okta logs are being ingested in your Splunk deployment.
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.
Associated Analytic story
source | version: 2