Try in Splunk Security Cloud


The following analytic detects the assignment of an Azure AD Privileged Identity Management (PIM) role. It leverages Azure Active Directory events to identify when a user is added as an eligible member to a PIM role. This activity is significant because PIM roles grant elevated privileges, and their assignment should be closely monitored to prevent unauthorized access. If confirmed malicious, an attacker could exploit this to gain privileged access, potentially leading to unauthorized actions, data breaches, or further compromise of the environment.

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

  • Last Updated: 2024-05-14
  • Author: Mauricio Velazco, Splunk
  • ID: fcd6dfeb-191c-46a0-a29c-c306382145ab




ID Technique Tactic
T1098 Account Manipulation Persistence, Privilege Escalation
T1098.003 Additional Cloud Roles Persistence, Privilege Escalation
Kill Chain Phase
  • Installation
  • Exploitation
  • DE.CM
  • CIS 10
 `azure_monitor_aad` operationName="Add eligible member to role in PIM completed*" 
| rename properties.* as * 
| stats count min(_time) as firstTime max(_time) as lastTime values(user) as user values(targetResources{}.displayName) as displayName  by result, operationName, initiatedBy.user.displayName 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `azure_ad_pim_role_assigned_filter`


The SPL above uses the following Macros:

:information_source: azure_ad_pim_role_assigned_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
  • properties
  • operationName
  • user
  • initiatedBy.user.userPrincipalName
  • result

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

Known False Positives

As part of legitimate administrative behavior, users may be assigned PIM roles. Filter as needed

Associated Analytic Story


Risk Score Impact Confidence Message
35.0 70 50 An Azure AD PIM role assignment was assiged to $user$

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