GitHub Repo

Detection: Okta ThreatInsight Login Failure with High Unknown users

REMOVED DETECTION

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

Reason: Detection deprecated as it no longer effectively identifies the intended malicious activity

Removed in version: 5.2.0

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

Updated Date: 2026-05-13 ID: 632663b0-4562-4aad-abe9-9f621a049738 Author: Okta, Inc, Michael Haag, Splunk Type: TTP Product: Splunk Enterprise Security

Description

DEPRECATION NOTE - This search has been deprecated and replaced with Okta ThreatInsight Threat Detected. The following analytic utilizes Oktas ThreatInsight to identify Login failures with high unknown users count and any included secondary outcome reasons. This event will trigger when a brute force attempt occurs with unknown usernames attempted.

1`okta` eventType="security.threat.detected" AND outcome.reason="Login failures with high unknown users count*" 
2| stats count min(_time) as firstTime max(_time) as lastTime values(displayMessage) by user eventType client.userAgent.rawUserAgent client.userAgent.browser outcome.reason 
3| `security_content_ctime(firstTime)` 
4| `security_content_ctime(lastTime)` 
5| `okta_threatinsight_login_failure_with_high_unknown_users_filter`

Data Source

No data sources specified for this detection.

Macros Used

Name Value
okta eventtype=okta_log OR sourcetype = "OktaIM2:log"
okta_threatinsight_login_failure_with_high_unknown_users_filter ``
okta_threatinsight_login_failure_with_high_unknown_users_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.004 Credential Stuffing 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 to be ingested in your Splunk deployment.

Known False Positives

Fidelity of this is high as it is Okta ThreatInsight. Filter and modify as needed.

Associated Analytic Story

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