mirror of
https://github.com/splunk/security_content
synced 2026-06-08 17:32:49 +00:00
Bhavin Patel
75 lines
3.4 KiB
YAML
75 lines
3.4 KiB
YAML
name: Azure AD Device Code Authentication
|
|
id: d68d8732-6f7e-4ee5-a6eb-737f2b990b91
|
|
version: 2
|
|
date: '2023-12-20'
|
|
author: Mauricio Velazco, Gowthamaraj Rajendran, Splunk
|
|
status: production
|
|
type: TTP
|
|
data_source: []
|
|
description: The following analytic identifies the execution of the Azure Device Code Phishing attack,
|
|
which can lead to Azure Account Take-Over (ATO). The detection leverages Azure AD logs specifically
|
|
focusing on authentication requests to identify the attack. This technique involves creating malicious
|
|
infrastructure, bypassing Multi-Factor Authentication (MFA), and bypassing Conditional Access Policies (CAPs).
|
|
The attack aims to compromise users by sending them phishing emails from attacker-controlled domains and trick
|
|
the victims into performing OAuth 2.0 device authentication. A successful execution of this attack can result
|
|
in adversaries gaining unauthorized access to Azure AD, Exchange mailboxes, and the target's Outlook Web Application (OWA).
|
|
This attack technique was detailed by security researchers including Bobby Cooke, Stephan Borosh, and others.
|
|
It's crucial for organizations to be aware of this threat, as it can lead to unauthorized access and potential data breaches.
|
|
search: '`azure_monitor_aad` category=SignInLogs "properties.authenticationProtocol"=deviceCode
|
|
| rename properties.* as *
|
|
| stats count min(_time) as firstTime max(_time) as lastTime by user src_ip, appDisplayName, userAgent
|
|
| `security_content_ctime(firstTime)`
|
|
| `security_content_ctime(lastTime)`
|
|
| `azure_ad_device_code_authentication_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 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.
|
|
references:
|
|
- https://attack.mitre.org/techniques/T1528
|
|
- https://github.com/rvrsh3ll/TokenTactics
|
|
- https://embracethered.com/blog/posts/2022/device-code-phishing/
|
|
- https://0xboku.com/2021/07/12/ArtOfDeviceCodePhish.html
|
|
- https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-device-code
|
|
tags:
|
|
analytic_story:
|
|
- Azure Active Directory Account Takeover
|
|
asset_type: Azure AD
|
|
confidence: 50
|
|
impact: 70
|
|
message: Device code requested for $user$ from $src_ip$
|
|
mitre_attack_id:
|
|
- T1528
|
|
- T1566
|
|
- T1566.002
|
|
observable:
|
|
- name: user
|
|
type: User
|
|
role:
|
|
- Victim
|
|
- name: src_ip
|
|
type: IP Address
|
|
role:
|
|
- Attacker
|
|
product:
|
|
- Splunk Enterprise
|
|
- Splunk Enterprise Security
|
|
- Splunk Cloud
|
|
risk_score: 35
|
|
required_fields:
|
|
- _time
|
|
- category
|
|
- user
|
|
- properties.authenticationProtocol
|
|
- properties.ipAddress
|
|
- properties.status.additionalDetails
|
|
- properties.appDisplayName
|
|
- properties.userAgent
|
|
security_domain: identity
|
|
tests:
|
|
- name: True Positive Test
|
|
attack_data:
|
|
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1528/device_code_authentication/azure-audit.log
|
|
source: Azure AD
|
|
sourcetype: azure:monitor:aad
|