Name:Azure AD Privileged Role Assigned id:a28f0bc3-3400-4a6e-a2da-89b9e95f0d2a version:5 date:2024-09-30 author:Mauricio Velazco, Gowthamaraj Rajendran, Splunk status:production type:TTP Description:The following analytic detects the assignment of privileged Azure Active Directory roles to a user. It leverages Azure AD audit logs, specifically monitoring the "Add member to role" operation. This activity is significant as adversaries may assign privileged roles to compromised accounts to maintain persistence within the Azure AD environment. If confirmed malicious, this could allow attackers to escalate privileges, access sensitive information, and maintain long-term control over the Azure AD infrastructure. Data_source:
-Azure Active Directory Add member to role
search:`azure_monitor_aad` "operationName"="Add member to role" | rename properties.* as * | rename initiatedBy.user.userPrincipalName as initiatedBy | rename targetResources{}.modifiedProperties{}.newValue as roles | eval role=mvindex(roles,1) | stats count min(_time) as firstTime max(_time) as lastTime values(user) as user by initiatedBy, result, operationName, role | lookup privileged_azure_ad_roles azureadrole AS role OUTPUT isprvilegedadrole description | search isprvilegedadrole = True | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)` | `azure_ad_privileged_role_assigned_filter`
how_to_implement: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 will legitimately assign the privileged roles users as part of administrative tasks. Filter as needed. References: -https://docs.microsoft.com/en-us/azure/active-directory/roles/concept-understand-roles -https://docs.microsoft.com/en-us/azure/active-directory/roles/permissions-reference -https://adsecurity.org/?p=4277 -https://www.mandiant.com/resources/detecting-microsoft-365-azure-active-directory-backdoors -https://docs.microsoft.com/en-us/azure/active-directory/roles/security-planning -https://attack.mitre.org/techniques/T1098/003/ drilldown_searches: name:'View the detection results for - "$user$"' search:'%original_detection_search% | search user = "$user$"' earliest_offset:'$info_min_time$' latest_offset:'$info_max_time$' name:'View risk events for the last 7 days for - "$user$"' search:'| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$user$") starthoursago=168 | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`' earliest_offset:'$info_min_time$' latest_offset:'$info_max_time$' tags: analytic_story: - 'Azure Active Directory Persistence' - 'NOBELIUM Group' asset_type:Azure Active Directory confidence:90 impact:70 message:A privileged Azure AD role was assigned for User $user$ initiated by $initiatedBy$ mitre_attack_id: - 'T1098' - 'T1098.003' observable: name:'user' type:'User' - role: - 'Victim' name:'initiatedBy' type:'User' - role: - 'Attacker' product: - 'Splunk Enterprise' - 'Splunk Enterprise Security' - 'Splunk Cloud' required_fields: - '_time' - 'user' - 'properties.targetResources{}.type' - 'properties.initiatedBy.user.userPrincipalName' - 'properties.result' risk_score:63 security_domain:audit
