Detection: Azure AD Device Code Authentication

Updated Date: 2026-05-13 ID: d68d8732-6f7e-4ee5-a6eb-737f2b990b91 Author: Mauricio Velazco, Gowthamaraj Rajendran, Splunk Type: TTP Product: Splunk Enterprise Security

Description

The following analytic identifies Azure Device Code Phishing attacks, which can lead to Azure Account Take-Over (ATO). It leverages Azure AD SignInLogs to detect suspicious authentication requests using the device code authentication protocol. This activity is significant as it indicates potential bypassing of Multi-Factor Authentication (MFA) and Conditional Access Policies (CAPs) through phishing emails. If confirmed malicious, attackers could gain unauthorized access to Azure AD, Exchange mailboxes, and Outlook Web Application (OWA), leading to potential data breaches and unauthorized data access.

Search

 1`azure_monitor_aad` category=SignInLogs "properties.authenticationProtocol"=deviceCode
 2  
 3| rename properties.* as *
 4  
 5| rename 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 user_agent
12       category
13  
14| `security_content_ctime(firstTime)`
15  
16| `security_content_ctime(lastTime)`
17  
18| `azure_ad_device_code_authentication_filter`

Data Source

Name	Platform	Sourcetype	Source
Azure Active Directory	Azure	`'azure:monitor:aad'`	`'Azure AD'`

Macros Used

Name	Value
azure_monitor_aad	`sourcetype=azure:monitor:aad`
azure_ad_device_code_authentication_filter	`search *`

azure_ad_device_code_authentication_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
T1528	Steal Application Access Token	Credential Access
T1566.002	Spearphishing Link	Initial Access

Exploitation

Delivery

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

Known False Positives

In most organizations, device code authentication will be used to access common Microsoft service but it may be legitimate for others. Filter as needed.

Associated Analytic Story

Azure Active Directory Account Takeover

Finding

Title	Entity Field	Entity Type	Risk Score
Device code requested for $user$ from $src$	user	user	50

Threat Objects

Field	Type
src	ip_address

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