Detection: Detect Password Spray Attempts

Description

This analytic employs the 3-sigma approach to detect an unusual volume of failed authentication attempts from a single source. A password spray attack is a type of brute force attack where an attacker tries a few common passwords across many different accounts to avoid detection and account lockouts. By utilizing the Authentication Data Model, this detection is effective for all CIM-mapped authentication events, providing comprehensive coverage and enhancing security against these attacks.

 1
 2| tstats `security_content_summariesonly` values(Authentication.user) AS unique_user_names dc(Authentication.user) AS unique_accounts values(Authentication.app) as app count(Authentication.user) as total_failures from datamodel=Authentication.Authentication where Authentication.action="failure" NOT Authentication.src IN ("-","unknown") by Authentication.src, Authentication.action, Authentication.signature_id, sourcetype, _time span=5m  
 3| `drop_dm_object_name("Authentication")`
 4    ```fill out time buckets for 0-count events during entire search length```
 5
 6| appendpipe [
 7| timechart limit=0 span=5m count 
 8| table _time] 
 9| fillnull value=0 unique_accounts
10  ``` Create aggregation field & apply to all null events```
11
12| eval counter=src+"__"+sourcetype+"__"+signature_id  
13| eventstats values(counter) as fnscounter  
14| eval counter=coalesce(counter,fnscounter) 
15  ``` stats version of mvexpand ```
16
17| stats values(app) as app values(unique_user_names) as unique_user_names values(total_failures) as total_failures values(src) as src values(signature_id) as signature_id values(sourcetype) as sourcetype count by counter unique_accounts _time
18    ``` remove duplicate time buckets for each unique source```
19
20| sort - _time unique_accounts 
21| dedup _time counter
22    ```Find the outliers```
23
24| eventstats avg(unique_accounts) as comp_avg , stdev(unique_accounts) as comp_std by counter 
25| eval upperBound=(comp_avg+comp_std*3) 
26| eval isOutlier=if(unique_accounts > 30 and unique_accounts >= upperBound, 1, 0) 
27| replace "::ffff:*" with * in src  
28| where isOutlier=1  
29| foreach * 
30    [ eval <<FIELD>> = if(<<FIELD>>="null",null(),<<FIELD>>)] 
31
32| table _time, src, action, app, unique_accounts, unique_user_names, total_failures, sourcetype, signature_id, counter 
33| `detect_password_spray_attempts_filter`

Data Source

Name Platform Sourcetype Source
Windows Event Log Security 4625 Windows icon Windows 'xmlwineventlog' 'XmlWinEventLog:Security'

Macros Used

Name Value
security_content_summariesonly summariesonly=summariesonly_config allow_old_summaries=oldsummaries_config fillnull_value=fillnull_config``
detect_password_spray_attempts_filter search *
detect_password_spray_attempts_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
T1110.003 Password Spraying Credential Access
T1110 Brute Force Credential Access
KillChainPhase.EXPLOITAITON
NistCategory.DE_CM
Cis18Value.CIS_10
APT28
APT29
APT33
Agrius
Chimera
Ember Bear
HEXANE
Lazarus Group
Leafminer
Silent Librarian
APT28
APT38
APT39
APT41
Agrius
DarkVishnya
Dragonfly
Ember Bear
FIN5
Fox Kitten
HEXANE
OilRig
Turla

Default Configuration

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

Setting Value
Disabled true
Cron Schedule 0 * * * *
Earliest Time -70m@m
Latest Time -10m@m
Schedule Window auto
Creates Notable Yes
Rule Title %name%
Rule Description %description%
Notable Event Fields user, dest
Creates Risk Event True
This configuration file applies to all detections of type TTP. These detections will use Risk Based Alerting and generate Notable Events.

Implementation

Ensure in-scope authentication data is CIM mapped and the src field is populated with the source device. Also ensure fill_nullvalue is set within the macro security_content_summariesonly. This search opporates best on a 5 minute schedule, looking back over the past 70 minutes. Configure 70 minute throttling on the two fields _time and counter.

Known False Positives

Unknown

Associated Analytic Story

Risk Based Analytics (RBA)

Risk Message Risk Score Impact Confidence
Potential Password Spraying attack from $src$ targeting $unique_accounts$ unique accounts. 49 70 70
The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.

References

Detection Testing

Test Type Status Dataset Source Sourcetype
Validation Passing N/A N/A N/A
Unit Passing Dataset XmlWinEventLog:Security XmlWinEventLog
Integration ✅ Passing Dataset XmlWinEventLog:Security XmlWinEventLog

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