Try in Splunk Security Cloud


The following analytic identifies the addition of a new federated domain within an Azure Active Directory tenant. This event could represent the execution of the Azure Active Directory identity federation backdoor technique discovered by security researcher Nestori Syynimaa. Similar to Active Directory, Azure AD uses the concept of domains to manage directories of identities. A new Azure AD tenant will initially contain a single domain that is commonly called the cloud-only domain. Organizations can also add their registered custom domains to Azure AD for email addresses to match the organizations domain name. If the organization intends to use a third-party identity provider such as ADFS for authentication, the added custom domains can be configured as federated. An adversary who has obtained privileged access to an Azure AD tenant may leverage this technique to establish persistence and be able to authenticate to Azure AD impersonating any user and bypassing the requirement to have a valid password and/or perform MFA.

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

  • Last Updated: 2023-12-20
  • Author: Mauricio Velazco, Gowthamaraj Rajendran, Splunk
  • ID: a87cd633-076d-4ab2-9047-977751a3c1a0




ID Technique Tactic
T1484 Domain or Tenant Policy Modification Defense Evasion, Privilege Escalation
T1484.002 Trust Modification Defense Evasion, Privilege Escalation
Kill Chain Phase
  • Exploitation
  • DE.CM
  • CIS 10
 `azure_monitor_aad`  operationName="Set domain authentication" "properties.result"=success 
| rename properties.* as * 
| rename targetResources{}.displayName as domain 
| stats count min(_time) as firstTime max(_time) as lastTime by user, domain, result, operationName, src_ip 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `azure_ad_new_federated_domain_added_filter`


The SPL above uses the following Macros:

:information_source: azure_ad_new_federated_domain_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
  • operationName
  • properties.result
  • src_ip
  • properties.targetResources{}.displayName
  • user

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 AuditLogs log category.

Known False Positives

In most organizations, domain federation settings will be updated infrequently. Filter as needed.

Associated Analytic Story


Risk Score Impact Confidence Message
81.0 90 90 A new federated domain, $domain$ , was added by $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: 2