Try in Splunk Security Cloud


The following analytic identifies one source Ip failing to authenticate with 30 unique valid users within 5 minutes. This behavior could represent an adversary performing a Password Spraying attack against an Azure Active Directory tenant to obtain initial access or elevate privileges. Error Code 50126 represents an invalid password. This logic can be used for real time security monitoring as well as threat hunting exercises.
Azure AD tenants can be very different depending on the organization. Users should test this detection and customize the arbitrary threshold if needed.

  • Type: Anomaly
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2022-07-12
  • Author: Mauricio Velazco, Splunk
  • ID: 94481a6a-8f59-4c86-957f-55a71e3612a6




ID Technique Tactic
T1586 Compromise Accounts Resource Development
T1586.003 Cloud Accounts Resource Development
T1110 Brute Force Credential Access
T1110.003 Password Spraying Credential Access
T1110.004 Credential Stuffing Credential Access
Kill Chain Phase
  • Weaponization
  • Exploitation
  • DE.AE
  • CIS 10
 `azuread` body.category= SignInLogs{}.succeeded= false 
| rename* as * 
| bucket span=5m _time 
| stats  dc(userPrincipalName) AS unique_accounts values(userPrincipalName) as tried_accounts by _time, ipAddress 
| where unique_accounts > 30 
| `azure_ad_multiple_users_failing_to_authenticate_from_ip_filter`


The SPL above uses the following Macros:

:information_source: azure_ad_multiple_users_failing_to_authenticate_from_ip_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • _time
  • body.category

How To Implement

You must install the latest version of Splunk Add-on for Microsoft Cloud Services from Splunkbase ( You must be ingesting Azure Active Directory events into your Splunk environment. Specifically, this analytic leverages the SignInLogs log category.

Known False Positives

A source Ip failing to authenticate with multiple users is not a common for legitimate behavior.

Associated Analytic Story


Risk Score Impact Confidence Message
63.0 70 90 Source Ip $$ failed to authenticate with 30 users within 5 minutes.

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.


Test Dataset

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

source | version: 1