Detection rules › Kusto Query Language

Potential Password Spray Attack (Uses Authentication Normalization)

Author
Ofer Shezaf
Source
upstream

'This query searches for failed attempts to log in from more than 15 various users within a 5 minute timeframe from the same source. This is a potential indication of a password spray attack To use this analytics rule, make sure you have deployed the ASIM normalization parsers'

MITRE ATT&CK coverage

TacticTechniques
Credential AccessT1110 Brute Force

Event coverage

ProviderEvent IDTitle
Security-Auditing4624An account was successfully logged on.
Security-Auditing4625An account failed to log on.
Security-Auditing4634An account was logged off.

Stages and Predicates

Stage 1: source

imAuthentication

Stage 2: where

and
  EventResult eq "Failure"
  EventType eq "Logon"

Stage 3: where

EventResultDetails in ["Incorrect password", "No such user or password"]

Stage 4: summarize

Stage 5: where

UserCount gt "FailureThreshold"

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
EventResulteq
  • Failure
EventResultDetailsin
  • Incorrect password
  • No such user or password
EventTypeeq
  • Logon
UserCountgt
  • FailureThreshold