Identity case
Impossible-travel sign-in flagged by the rule
The impossible-travel rule fired: one user signed in from the US, then the UK, 35 minutes apart. A stolen account, or a known path?
- BeginnerLevel
- 15 minAbout
- New detailsEvery attempt
- KQL or SPLQuery language
Free. Read the briefing as a guest; investigating needs a free account.
The alert
Impossible travel: US then UK within 35 minutes
Rule fired "impossible travel" for jjohnson - US then UK within the hour. Looks scary but I ran out of time, can you confirm?
From one version of the case: the company, the people and the details change with every attempt.
About this kind of alert
Impossible-travel alerts: one account signing in from two places too far apart to travel between. They catch stolen credentials, and they also fire on VPNs, mobile networks and real trips.
What you do
- Read the escalation from an L1 colleague and the events they attached.
- Hunt the logs in KQL (Microsoft Sentinel) or SPL (Splunk) and pin the evidence.
- Find the root cause and scope the incident: which accounts and hosts are affected.
- Map what you found to MITRE ATT&CK, set the severity and choose the response.
- Get a debrief: what happened, the evidence you missed, and what the attacker does next if you were wrong.
Logs you will query
| Microsoft Sentinel | Splunk |
|---|---|
SigninLogs | index=azure sourcetype=azure:monitor:aad |
AuditLogs | index=azure sourcetype=azure:monitor:aad |
EmailEvents | index=o365 sourcetype=o365:reporting:messagetrace |


