Azure AD Service Principal Enumeration
This detection leverages azure graph activity logs to identify when graph APIs have been used to identify 10 or more service principals. This type of behaviour is associated with tools such as Azure enumberation…
Description
This detection leverages azure graph activity logs to identify when graph APIs have been used to identify 10 or more service principals. This type of behaviour is associated with tools such as Azure enumberation tools such as AzureHound or ROADtools.
Detection logic
Detection requirements
- Platform
- IaaSIdentity ProviderOffice SuiteSaaS
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- azure_active_directory_microsoftgraphactivitylogs
Known benign triggers
- No false positives have been identified at this time.
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 |
|---|---|
| github.com/SpecterOps/AzureHound | 3from 2 sources |
| github.com/dirkjanm/ROADtools | 16from 2 sources |
| splunk.github.io/splunk-add-on-for-microsoft-cloud-services/Install/ | 3 |
| splunkbase.splunk.com/app/3110 | 3 |
From the source
- At source
- Open at source
- Upstream identifier
- 3f0647ce-add5-4436-8039-cbd1abe74563
- Tagged by the source as
- Azure Active Directory Privilege EscalationCompromised User AccountAzure TenantcloudSplunk CloudSplunk EnterpriseSplunk Enterprise Securityidentity
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1