Detection rules › Splunk

Windows Multiple Disabled Users Failed To Authenticate Wth Kerberos

Author
Mauricio Velazco, Splunk
Source
upstream

The following analytic detects a single source endpoint failing to authenticate with 30 unique disabled domain users using the Kerberos protocol within 5 minutes. It leverages Windows Security Event 4768, focusing on failure code 0x12, indicating revoked credentials. This activity is significant as it may indicate a Password Spraying attack targeting disabled accounts, a tactic used by adversaries to gain initial access or elevate privileges. If confirmed malicious, this could lead to unauthorized access or privilege escalation within the Active Directory environment, posing a severe security risk.

MITRE ATT&CK coverage

TacticTechniques
Credential AccessT1110.003 Brute Force: Password Spraying

Event coverage

ProviderEvent IDTitle
Security-Auditing4768A Kerberos authentication ticket (TGT) was requested.

Stages and Predicates

Stage 1: search

search EventCode=4768 Status=0x12 TargetUserName!="*$"

Stage 2: bucket

bucket span=5m _time

Stage 3: stats

stats dc(TargetUserName) AS unique_accounts,AS user,AS dest BY _time, IpAddress

Stage 4: where

where unique_accounts>30

Stage 5: search

search `macro`

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
EventCodeeq
  • 4768 corpus 10 (splunk 10)
Statuseq
  • 0x12 corpus 2 (splunk 2)
TargetUserNamene
  • *$ corpus 10 (splunk 10)
unique_accountsgt
  • 30 corpus 8 (splunk 8)