Azure Ad Concurrent Sessions From Different Ips

Description

Used Evilnginx2 to phish an Azure AD user and steal session cookies. Then, imported the stolen session cookies into a different browser to access Azure AD resources from a different location and source ip. Tenant specific details have been replaced in the dataset including tenant id, user names, ips, etc.

MITRE ATT&CK Techniques

ID Technique Tactic
T1185 Browser Session Hijacking Collection

Environment Details

Field Value
Environment attack_range
Directory azure_ad_concurrent_sessions_from_different_ips
Test Date 2023-01-24

Datasets

The following datasets were collected during this attack simulation:

Azuread

  • Path: /datasets/attack_techniques/T1185/azure_ad_concurrent_sessions_from_different_ips/azuread.log
  • Sourcetype: azure:monitor:aad
  • Source: azure

The following detections in our security content repository use this attack data for testing:

Detection Name Type Source MITRE ATT&CK Analytic Story
Azure AD Concurrent Sessions From Different Ips TTP Cloud T1185 Compromised User Account, Azure Active Directory Account Takeover, Scattered Lapsus$ Hunters

Usage Instructions

Replay with Splunk Attack Data

Replay attack data with replay.py from Splunk Attack Data.

1python replay.py --dataset /datasets/attack_techniques/T1185/azure_ad_concurrent_sessions_from_different_ips/azuread.log --index attack_data

Manual Import

  1. Download the dataset files from the paths listed above
  2. Configure your Splunk instance with the appropriate sourcetypes
  3. Import the logs using the Splunk Add Data wizard

Find more detections and analytics for this attack technique in our security content repository.


Source: GitHub | Version: 1.0