Detection: Azure AD Application Administrator Role Assigned

Description

The following analytic identifies the assignment of the Application Administrator role to an Azure AD user. It leverages Azure Active Directory events, specifically monitoring the "Add member to role" operation. This activity is significant because users in this role can manage all aspects of enterprise applications, including credentials, which can be used to impersonate application identities. If confirmed malicious, an attacker could escalate privileges, manage application settings, and potentially access sensitive resources by impersonating application identities, posing a significant security risk to the Azure AD tenant.

 1`azure_monitor_aad`  operationName="Add member to role"  "properties.targetResources{}.modifiedProperties{}.newValue"="*Application Administrator*"
 2  
 3| rename properties.* as *
 4  
 5| rename initiatedBy.user.userPrincipalName as initiatedBy, userAgent as user_agent
 6  
 7| fillnull
 8  
 9| stats count min(_time) as firstTime max(_time) as lastTime
10    BY dest user src
11       vendor_account vendor_product initiatedBy
12       user_agent signature
13  
14| `security_content_ctime(firstTime)`
15  
16| `security_content_ctime(lastTime)`
17  
18| `azure_ad_application_administrator_role_assigned_filter`

Data Source

Name Platform Sourcetype Source
Azure Active Directory Add member to role Azure icon Azure 'azure:monitor:aad' 'Azure AD'

Macros Used

Name Value
security_content_ctime convert timeformat="%Y-%m-%dT%H:%M:%S" ctime($field$)
azure_ad_application_administrator_role_assigned_filter search *
azure_ad_application_administrator_role_assigned_filter is an empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Annotations

- MITRE ATT&CK
+ Kill Chain Phases
+ NIST
+ CIS
- Threat Actors
ID Technique Tactic
T1098.003 Additional Cloud Roles Persistence
Exploitation
Installation
DE.CM
CIS 10

Default Configuration

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

Setting Value
Disabled true
Cron Schedule 0 * * * *
Earliest Time -70m@m
Latest Time -10m@m
Schedule Window auto
Creates Finding (Notable) Yes
Rule Title %name%
Rule Description %description%
Notable Event Fields user, dest
Creates Intermediate Finding (Risk Event) No
TTP detections generate a Finding (Notable) and may generate Intermediate Findings (Risk Events) for associated entities.

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. This analytic was written to be used with the azure:monitor:aad sourcetype leveraging the Auditlog log category

Known False Positives

Administrators may legitimately assign the Application Administrator role to a user. Filter as needed.

Associated Analytic Story

Finding

Title Entity Field Entity Type Risk Score
The privileged Azure AD role Application Administrator was assigned for User $user$ initiated by $initiatedBy$ user user 50

References

Detection Testing

Test Type Status Dataset Source Sourcetype
Validation Passing N/A N/A N/A
Unit Passing Dataset Azure AD azure:monitor:aad
Integration ✅ Passing Dataset Azure AD azure:monitor:aad

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: 15