Azure AD Suspicious Device Registration

 Original Source: [splunk source]
Name:Azure AD Suspicious Device Registration
id:4cfe7afd-a22b-4af5-9520-39f7f6564e7f
version:1
date:None
author:Jake Enea, Onur Mustafa Erdogan, Splunk
status:production
type:Anomaly
Description:The following analytic detects suspicious Azure Active Directory device registrations by monitoring "Register device" audit events for device names matching specific DESKTOP patterns or the user agent "Dsreg/10.0 (Windows 10.0.19041.928)". This user agent may indicate device registration activity through ROADtools, an offensive security framework targeting EntraID deployments. Device registration can support persistence or provide a device identity that can be used to access internal resources. If confirmed malicious, an attacker could use the registered device to maintain access or facilitate further compromise of the environment.
Data_source:
  • -Azure Active Directory
search:`azure_monitor_aad` operationName="Register device" (
properties.targetResources{}.displayName IN (
"*-PC",
"DESKTOP-*",
"EC2AMAZ-*",
"LAPTOP-*",
"MININT-*",
"MSEDGEWIN10",
"WIN-*"
)
OR
properties.userAgent="Dsreg/*"
)
| rename properties.targetResources{}.displayName as dvc, properties.userAgent as user_agent
| fillnull
| stats count min(_time) as firstTime
max(_time) as lastTime
values(result) as result
values(user_agent) as user_agent

by tenantId user src dvc signature vendor_account vendor_product

| `security_content_ctime(firstTime)`
| `security_content_ctime(lastTime)`
| `azure_ad_suspicious_device_registration_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. This analytic was written to be used with the azure:monitor:aad sourcetype leveraging the AuditLog log category.
known_false_positives:Users may register devices with names that match the suspicious patterns. Filter as needed.
References:
  -https://www.wiz.io/blog/detecting-entra-device-registration-abuse
  -https://github.com/dirkjanm/ROADtools
drilldown_searches:
 name:'View the detection results for - "$src$" and "$user$"'
 search:'%original_detection_search% | search src = "$src$" user = "$user$"'
 earliest_offset:'$info_min_time$'
 latest_offset:'$info_max_time$'
 name:'View risk events for the last 7 days for - "$src$" and "$user$"'
 search:'| from datamodel Risk.All_Risk | search normalized_risk_object IN ("$src$", "$user$") | stats count min(_time) as firstTime max(_time) as lastTime values(search_name) as "Search Name" values(risk_message) as "Risk Message" values(analyticstories) as "Analytic Stories" values(annotations._all) as "Annotations" values(annotations.mitre_attack.mitre_tactic) as "ATT&CK Tactics" by normalized_risk_object | `security_content_ctime(firstTime)` | `security_content_ctime(lastTime)`'
 earliest_offset:'7d'
 latest_offset:'0'
analytic_story:['Azure Active Directory Account Takeover', 'Azure Active Directory Persistence']

asset_type:Azure Active Directory

mitre_attack_id:['T1098.005', 'T1586.003']

product:['Splunk Enterprise', 'Splunk Enterprise Security', 'Splunk Cloud']

category:cloud

security_domain:identity

tags:

tests:
 name:'True Positive Test'
 attack_data:
  data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1098.005/azure_ad_suspicious_device_registration/azure_ad_suspicious_device_registration.log
  source: Azure AD
  sourcetype: azure:monitor:aad
 test_type:'unit'
manual_test:None