Azure risk detection: Malicious IP sign-in risk event based on sign-in failure rate

Flags Azure risk events for sign-ins associated with malicious IPs using maliciousIPAddress failure-rate indications.

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

ATT&CK techniques

C2
  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. Exfiltration

  13. Impact

What it detects

This rule flags Azure risk events where the risk event type is set to maliciousIPAddress. It indicates sign-in activity originating from an IP address classified as malicious, which attackers may use to probe accounts or attempt credential access. The detection relies on Azure risk detection telemetry that records the riskEventType value for these events.

Related detections9 linkedT1090 — drag to rearrange
Malicious QDoor Remote Proxy Execution via WMIC Node Process Call Create of svhost from Temp (via process_creation)
Suspicious SOCKS Proxy Persistence via SystemBC PowerShell Run Key
Malicious Java Backdoor Execution from Public Documents via javaw (via process_creation)
Suspicious Proxyware Installation via accept-tos Flag on Linux
Suspicious DNS Query to Dynamic DNS and Tunneling Providers Abused by RATs
Malicious GenAI Browser Extension C2 and PAC Redirection (via proxy)
Malicious FRP Reverse Proxy Tunnel Identified by Hardcoded Token (via process_creation)
Suspicious SSH Reverse Tunnel Over DNS Port
Suspicious Chisel SOCKS Tunnel Command Line
Azure risk detection: Malicious IP sign-in risk event based on sign-in failure rate
Pivot detection · T1090 · 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.