Azure Ad High Number Of Failed Authentications For User

Description

Used Invoke-MSOLSpray to perform a brute force attack attack against a unique Azure AD account with 25 passwords. Tenant specific details have been replaced in the dataset including tenant id, user names, ips, etc.

MITRE ATT&CK Techniques

ID Technique Tactic
T1110.001 Password Guessing Credential Access

Environment Details

Field Value
Environment attack_range
Directory azure_ad_high_number_of_failed_authentications_for_user
Test Date 2023-01-23

Datasets

The following datasets were collected during this attack simulation:

Azuread

  • Path: /datasets/attack_techniques/T1110.001/azure_ad_high_number_of_failed_authentications_for_user/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 High Number Of Failed Authentications From Ip TTP Cloud T1110.001, T1110.003 Compromised User Account, Azure Active Directory Account Takeover, NOBELIUM Group
Azure AD High Number Of Failed Authentications For User TTP Cloud T1110.001 Compromised User Account, Azure Active Directory Account Takeover

Usage Instructions

Replay with Splunk Attack Data

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

1python replay.py --dataset /datasets/attack_techniques/T1110.001/azure_ad_high_number_of_failed_authentications_for_user/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