Azure AD User Login Risk: Impossible Travel from Distant Locations

Flags Azure Entra risk events tagged as impossibleTravel indicating implausible geographic sign-in travel within a short time.

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

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

Identifies account activity flagged as an impossible travel risk event when sign-in activity is observed from geographically distant locations within an unrealistically short time window. This behavior matters because it can indicate credential theft or session compromise rather than legitimate user movement. The detection relies on Azure risk telemetry that produces risk events of type impossibleTravel.

Related detections9 linkedT1078 — drag to rearrange
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious SSH Daemon Configuration Change Enabling Root Login
Suspicious NTLM Network Logon From Attacker Controlled Workstation Names (via security)
Suspicious dMSA Object Access with Migration AccessMask
Malicious ESX Admins Group Added to Privileged Directory Group
Malicious ESX Admins Group Creation via WinRM Host
Suspicious BrightMetricAgent Remote Tool Execution Associated With Volt Typhoon
Suspicious SmarterMail Force Password Reset API Request Indicating Account Takeover
Azure AD User Login Risk: Impossible Travel from Distant Locations
Pivot detection · T1078 · 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.