Detection: Azure AD Multiple AppIDs and UserAgents Authentication Spike

Description

The following analytic detects unusual authentication activity in Azure AD, specifically when a single user account has over 8 authentication attempts using 3+ unique application IDs and 5+ unique user agents within a short period. It leverages Azure AD audit logs, focusing on authentication events and using statistical thresholds. This behavior is significant as it may indicate an adversary probing for MFA requirements. If confirmed malicious, it suggests a compromised account, potentially leading to further exploitation, lateral movement, and data exfiltration. Early detection is crucial to prevent substantial harm.

Search

1`azure_monitor_aad` category=SignInLogs operationName="Sign-in activity" (properties.authenticationRequirement="multiFactorAuthentication" AND properties.status.additionalDetails="MFA required in Azure AD") OR (properties.authenticationRequirement=singleFactorAuthentication AND "properties.authenticationDetails{}.succeeded"=true) 
2| bucket span=5m _time 
3| rename properties.* as * 
4| stats count min(_time) as firstTime max(_time) as lastTime dc(appId) as unique_app_ids dc(userAgent) as unique_user_agents values(appDisplayName) values(deviceDetail.operatingSystem) by user, src_ip 
5| where count > 5 and unique_app_ids > 2 and unique_user_agents > 5 
6| `security_content_ctime(firstTime)` 
7| `security_content_ctime(lastTime)` 
8| `azure_ad_multiple_appids_and_useragents_authentication_spike_filter`

Data Source

Name	Platform	Sourcetype	Source
Azure Active Directory Sign-in activity	Azure	'azure:monitor:aad'	'Azure AD'

Macros Used

Annotations

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Implementation

You must install the latest version of Splunk Add-on for Microsoft Cloud Services from Splunkbase (https://splunkbase.splunk.com/app/3110/#/details). You must be ingesting Azure Active Directory events into your Splunk environment through an EventHub. This analytic was written to be used with the azure:monitor:aad sourcetype leveraging the SignInLogs log category.

Known False Positives

Rapid authentication from the same user using more than 5 different user agents and 3 application IDs is highly unlikely under normal circumstances. However, there are potential scenarios that could lead to false positives.

Associated Analytic Story

• Azure Active Directory Account Takeover

Risk Based Analytics (RBA)

References

• https://attack.mitre.org/techniques/T1078/

• https://www.blackhillsinfosec.com/exploiting-mfa-inconsistencies-on-microsoft-services/

• https://github.com/dafthack/MFASweep

• https://www.youtube.com/watch?v=SK1zgqaAZ2E

Detection Testing

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub | Version: 5