Azure AD Concurrent Sessions From Different Ips
The following analytic detects an Azure AD account with concurrent sessions originating from multiple unique IP addresses within a 5-minute window. It leverages Azure Active Directory NonInteractiveUserSignInLogs to…
Description
The following analytic detects an Azure AD account with concurrent sessions originating from multiple unique IP addresses within a 5-minute window. It leverages Azure Active Directory NonInteractiveUserSignInLogs to identify this behavior by analyzing successful authentication events and counting distinct source IPs. This activity is significant as it may indicate session hijacking, where an attacker uses stolen session cookies to access corporate resources from a different location. If confirmed malicious, this could lead to unauthorized access to sensitive information and potential data breaches.
Detection logic
Detection requirements
- Platform
- Windows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- azure_active_directory
Known benign triggers
- A user with concurrent sessions from different Ips may also represent the legitimate use of more than one device. Filter as needed and/or customize the threshold to fit your environment. Also consider the geographic location of the IP addresses and filter out IP space that belong to your organization.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| attack.mitre.org/techniques/T1185/ | 4 |
| breakdev.org/evilginx-2-next-generation-of-phishing-2fa-tokens/ | 4 |
| github.com/kgretzky/evilginx2 | 4 |
From the source
- At source
- Open at source
- Upstream identifier
- a9126f73-9a9b-493d-96ec-0dd06695490d
- Tagged by the source as
- Azure Active Directory Account TakeoverCompromised User AccountScattered Lapsus$ HuntersAzure TenantcloudSplunk CloudSplunk EnterpriseSplunk Enterprise Securitythreat
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1