Azure AD Successful Single-Factor Authentication
The following analytic identifies a successful single-factor authentication event against Azure Active Directory. It leverages Azure SignInLogs data, specifically focusing on events where single-factor authentication…
Description
The following analytic identifies a successful single-factor authentication event against Azure Active Directory. It leverages Azure SignInLogs data, specifically focusing on events where single-factor authentication succeeded. This activity is significant as it may indicate a misconfiguration, policy violation, or potential account takeover attempt. If confirmed malicious, an attacker could gain unauthorized access to the account, potentially leading to data breaches, privilege escalation, or further exploitation within the environment.
Detection logic
Detection requirements
- Platform
- IaaSIdentity ProviderOffice SuitePRESaaS
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- azure_active_directory
Known benign triggers
- Although not recommended, certain users may be required without multi-factor authentication. Filter as needed
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/T1078/004/ | 15from 2 sources |
| docs.microsoft.com/en-us/azure/active-directory/authentication/concept-mfa-howitworks* | Only this detection cites it |
| www.forbes.com/sites/daveywinder/2020/07/08/new-dark-web-audit-reveals-15-billion-stolen-logins-from-100000-breaches-passwords-hackers-cybercrime/?sh=69927b2a180f | 2 |
From the source
- At source
- Open at source
- Upstream identifier
- a560e7f6-1711-4353-885b-40be53101fcd
- Tagged by the source as
- Azure Active Directory Account TakeoverAzure Active DirectorycloudSplunk CloudSplunk EnterpriseSplunk Enterprise Securityidentity
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Published
- Aug 26, 2026
- Version
- 1