Try in Splunk Security Cloud

Description

This Splunk detection focuses on instances where more than five unique Windows accounts are disabled within a 10-minute window, as indicated by Event Code 4725 in the Windows Security Event Log. The query analyzes the wineventlog_security dataset, grouping data into 10-minute segments, and tracks the count and distinct count of TargetUserName, the accounts being disabled. This pattern of disabling multiple accounts rapidly is unusual and could signal internal policy breaches or an external attacker's attempt to disrupt normal operations. Teams are advised to tailor the threshold and timeframe of this detection to their environment's specifics

  • Type: TTP

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

  • Last Updated: 2024-02-21
  • Author: Mauricio Velazco, Splunk
  • ID: 5d93894e-befa-4429-abde-7fc541020b7b

Annotations

ATT&CK

ATT&CK

ID Technique Tactic
T1098 Account Manipulation Persistence, Privilege Escalation
T1078 Valid Accounts Defense Evasion, Persistence, Privilege Escalation, Initial Access
Kill Chain Phase
  • Installation
  • Exploitation
  • Delivery
NIST
  • DE.CM
CIS20
  • CIS 10
CVE 


1
2
3
4
5



 `wineventlog_security` EventCode=4725 status=success 
| bucket span=10m _time 
| stats count dc(user) as unique_users values(user) as user by EventCode signature _time src_user SubjectDomainName TargetDomainName Logon_ID 
| where unique_users > 5 
| `windows_multiple_accounts_disabled_filter`

Macros

The SPL above uses the following Macros:

:information_source: windows_multiple_accounts_disabled_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
  • EventCode
  • success
  • TargetUserName
  • SubjectUserName
  • src_user
  • SubjectDomainName
  • TargetDomainName
  • Logon_ID
  • user

How To Implement

To successfully implement this search, you need to be ingesting Domain Controller events with the Windows TA. The Advanced Security Audit policy setting Audit User Account Management within Account Management needs to be enabled.

Known False Positives

Service accounts may be responsible for the creation, deletion or modification of accounts for legitimate purposes. Filter as needed.

Associated Analytic Story

RBA

Risk Score Impact Confidence Message
18.0 30 60 User $src_user$ disabled multiple accounts in a short period of time.

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