Try in Splunk Security Cloud


The following analytic identifies instances where a new owner is assigned to an application registration within an Azure AD and Office 365 tenant. It leverages O365 audit logs, specifically events related to changes in owner assignments within the AzureActiveDirectory workload for application registrations. Assigning a new owner to an application registration can grant significant control over the application's configuration, permissions, and behavior. An unauthorized or inadvertent change in ownership can lead to misuse of the application, potentially affecting data access, user permissions, or the application's interactions within the tenant. Monitoring for such changes ensures that only legitimate and authorized personnel have control over application registrations. If an attacker successfully assigns themselves or a compromised account as an owner to an application registration, they can modify the application's settings, permissions, and behavior. This can lead to unauthorized data access, escalation of privileges, or the introduction of malicious behavior within the application's operations

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

  • Last Updated: 2023-09-07
  • Author: Mauricio Velazco, Splunk
  • ID: c068d53f-6aaa-4558-8011-3734df878266




ID Technique Tactic
T1098 Account Manipulation Persistence, Privilege Escalation
Kill Chain Phase
  • Installation
  • Exploitation
  • DE.CM
  • CIS 10
`o365_management_activity` Workload=AzureActiveDirectory Operation="Add owner to application." 
| eval app_id=mvindex('ModifiedProperties{}.NewValue', 0) 
| eval app_displayName=mvindex('ModifiedProperties{}.NewValue', 1) 
| stats max(_time) as lastTime values(ModifiedProperties{}.NewValue) by Operation, user, app_displayName, object 
| `security_content_ctime(lastTime)` 
| `o365_application_registration_owner_added_filter`


The SPL above uses the following Macros:

:information_source: o365_application_registration_owner_added_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
  • Workload
  • Operation
  • ModifiedProperties{}.NewValue
  • user

How To Implement

You must install the Splunk Microsoft Office 365 Add-on and ingest Office 365 management activity events.

Known False Positives

Application owners may be added for legitimate reasons, filter as needed.

Associated Analytic Story


Risk Score Impact Confidence Message
30.0 60 50 Application registration $app_displayName$ was assigned a new owner $object$

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