Detection: Multiple Okta Users With Invalid Credentials From The Same IP

REMOVED DETECTION

This detection has been removed from the Splunk Threat Research content library and is no longer maintained or supported.

Reason: Detections updated to use the new search logic and field names due to the TA update

Removed in version: 5.2.0

Replacement: Okta Multiple Users Failing To Authenticate From Ip

If you have any questions or concerns, please reach out to us at research@splunk.com.

Updated Date: 2026-05-13 ID: 19cba45f-cad3-4032-8911-0c09e0444552 Author: Michael Haag, Mauricio Velazco, Rico Valdez, Splunk Type: TTP Product: Splunk Enterprise Security

Description

DEPRECATION NOTE - This search has been deprecated and replaced with Okta Multiple Users Failing To Authenticate From Ip. This analytic identifies multiple failed logon attempts from a single IP in a short period of time. Use this analytic to identify patterns of suspicious logins from a single source and filter as needed or use this to drive tuning for higher fidelity analytics.

Search

1`okta` eventType=user.session.start outcome.result=FAILURE 
2| rename client.geographicalContext.country as country, client.geographicalContext.state as state, client.geographicalContext.city as city 
3| stats min(_time) as firstTime max(_time) as lastTime dc(src_user) as distinct_users values(src_user) as users by src_ip, displayMessage, outcome.reason, country, state, city 
4| `security_content_ctime(firstTime)` 
5| `security_content_ctime(lastTime)` 
6| search distinct_users > 5
7| `multiple_okta_users_with_invalid_credentials_from_the_same_ip_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name	Value
okta	`eventtype=okta_log OR sourcetype = "OktaIM2:log"`
multiple_okta_users_with_invalid_credentials_from_the_same_ip_filter	``

multiple_okta_users_with_invalid_credentials_from_the_same_ip_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK

+ Kill Chain Phases

+ NIST

+ CIS

- Threat Actors

ID	Technique	Tactic
T1078.001	Default Accounts	Initial Access
T1110.003	Password Spraying	Persistence

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Setting	Value
Disabled	true
Cron Schedule	`N/A`
Earliest Time	`N/A`
Latest Time	`N/A`
Schedule Window	`N/A`
Creates Finding (Notable)	No
Creates Intermediate Finding (Risk Event)	No

TTP detections generate a Finding (Notable) and may generate Intermediate Findings (Risk Events) for associated entities.

Implementation

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

Suspicious Okta Activity

References

Detection Testing

Test Type	Status	Dataset	Source	Sourcetype
Validation	Not Applicable	N/A	N/A	N/A
Unit	Not Applicable	N/A	`N/A`	`N/A`
Integration	Not Applicable	N/A	`N/A`	`N/A`

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: 6