huntrule

Azure Entra ID risk event: successful password spray detection

Flags Azure Entra ID risk events indicating a successful password spray attempt.

FreeReviewedSigma · High · v5
Product
azure
Service
riskdetection
Author
Mark Morowczynski '@markmorow', Gloria Lee, '@gleeiamglo' (SigmaHQ), DRL 1.1
Published
2023-09-03
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Cred Access

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Azure Entra ID Risk Detection events where the riskEventType is passwordSpray, indicating a successful password spray attempt. Attackers use password spraying to compromise accounts by trying the same password across many users while avoiding lockouts. The detection relies on risk telemetry from the Azure risk detection service indicating the specific password spray risk type.

Reporting behind it

Related detections9 linkedT1110 — drag to rearrange
Malicious SQL Server - Brutforce Enumeration with Non Existing Users - Login (via application)
Malicious Brutforce Enumeration with Non Existing Users - Login (via security)
Malicious Brutforce Enumeration on Windows OpenSSH Server with Non Existing User (via security)
Malicious Brutforce on Windows OpenSSH Server with Valid Users (via security)
Malicious RDP Discovery Performed on Multiple Hosts (via rdp)
Possible SonicWall Credential Testing via userLogin Endpoint
Malicious Brutforce Enumeration with Unexisting Users - Kerberos (via security)
Suspicious JumpCloud Password Brute Force Followed by Success
AWS CloudTrail ConsoleLogin Failed authentication
Azure Entra ID risk event: successful password spray detection
Pivot detection · T1110 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.