:no_entry: THIS IS A DEPRECATED DETECTION

This detection has been marked deprecated by the Splunk Threat Research team. This means that it will no longer be maintained or supported.

Try in Splunk Security Cloud

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.

  • Type: TTP

  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2024-08-16
  • Author: Okta, Inc, Michael Haag, Splunk
  • ID: 632663b0-4562-4aad-abe9-9f621a049738

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1078 Valid Accounts Defense Evasion, Persistence, Privilege Escalation, Initial Access
T1078.001 Default Accounts Defense Evasion, Persistence, Privilege Escalation, Initial Access
T1110.004 Credential Stuffing Credential Access
Kill Chain Phase
  • Exploitation
  • Installation
  • Delivery
NIST
  • DE.CM
CIS20
  • CIS 10
CVE 


1
2
3
4
5



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

Macros

The SPL above uses the following Macros:

:information_source: okta_threatinsight_login_failure_with_high_unknown_users_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • _time
  • eventType
  • client.userAgent.rawUserAgent
  • client.userAgent.browser
  • outcome.reason
  • displayMessage

How To Implement

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

RBA

Risk Score Impact Confidence Message
50.0 50 100 Okta ThreatInsight has detected or prevented a high number of login failures.

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

Reference

Test Dataset

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 | version: 2