Entra ID Device with ROADtools Default OS Build (Entity Analytics)
Identifies the first occurrence of a Microsoft Entra ID device, surfaced through the Entra ID Entity Analytics device inventory, whose host name follows the default "DESKTOP-" pattern and whose operating system build…
Description
Identifies the first occurrence of a Microsoft Entra ID device, surfaced through the Entra ID Entity Analytics device inventory, whose host name follows the default "DESKTOP-" pattern and whose operating system build is `10.0.19041.928`. This combination is the default device profile that ROADtools (roadtx) uses when registering a device, and the OS build typically differs from the patched OS versions of legitimate hosts in the environment. Adversaries register rogue devices in Entra ID to acquire a Primary Refresh Token (PRT), establish persistence, and obtain trusted, programmatic access to the tenant. Because the OS build is a tool default, this is a high-fidelity but evadable indicator; baseline approved device builds and naming conventions before relying on it.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersESXiIaaSIdentity ProviderLinuxmacOSNetwork DevicesOffice SuiteSaaSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
- Log source category
- event_index
Known benign triggers
- Authorized red team or penetration testing engagements that use ROADtools to register devices will appear in the device inventory and match this rule. If this is expected, add exceptions for the specific host names or device IDs.
- Unmanaged or imaged Windows 10 20H1 hosts may legitimately report the `10.0.19041.928` build with a default "DESKTOP-" host name. Validate against your device inventory and patch baseline before escalating.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| dirkjanm.io/introducing-roadtools-token-exchange-roadtx/ | 3 |
| github.com/dirkjanm/ROADtools | 16from 2 sources |
| unit42.paloaltonetworks.com/roadtools-cloud-attacks/ | 2 |
From the source
- At source
- Open at source
- Upstream identifier
- 10b63b69-9f08-4767-b318-12208f97ad41
- Tagged by the source as
- Data Source: Microsoft Entra IDData Source: Microsoft Entra ID Entity AnalyticsDomain: CloudDomain: IdentityNoise: UnknownPerformance: FastPlatform: Entra IDResources: Investigation GuideRule Type: New TermsTactic: PersistenceUse Case: Asset VisibilityUse Case: Threat Detection
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3