Detection rules › Splunk

Windows Multiple Users Failed To Authenticate Using Kerberos

Author
Mauricio Velazco, Splunk
Source
upstream

The following analytic identifies a single source endpoint failing to authenticate with 30 unique users using the Kerberos protocol. It leverages EventCode 4771 with Status 0x18, indicating wrong password attempts, and aggregates these events over a 5-minute window. This behavior is significant as it may indicate a Password Spraying attack, where an adversary attempts to gain initial access or elevate privileges in an Active Directory environment. If confirmed malicious, this activity could lead to unauthorized access, privilege escalation, and potential compromise of sensitive information.

MITRE ATT&CK coverage

TacticTechniques
Credential AccessT1110.003 Brute Force: Password Spraying

Event coverage

ProviderEvent IDTitle
Security-Auditing4771Kerberos pre-authentication failed.

Stages and Predicates

Stage 1: search

search EventCode=4771 Status=0x18 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
  • 4771 corpus 2 (splunk 2)
Statuseq
  • 0x18 corpus 2 (splunk 2)
TargetUserNamene
  • "*$" corpus 7 (splunk 7)
unique_accountsgt
  • 30 corpus 8 (splunk 8)