LoFP LoFP / users joining or registering a personal or freshly imaged windows device that still has its default hostname will match. this rule is informational only and is intended for correlation and baselining, not standalone alerting.

Techniques

Sample rules

Entra ID Device Registration with Default Hostname Pattern

Description

Detects a successful Microsoft Entra ID audit event for Register device where the registered device carries a default Windows or kit-style hostname (DESKTOP-, Device-, or Work Pc*). Adversary-in-the-middle and device-code phishing kits, along with tooling such as ROADtools, register a device with the token broker to obtain a device-bound Primary Refresh Token (PRT) and rarely set a custom device name, so the registered object keeps the default DESKTOP-, Device-, or Work Pc name. Registering a device establishes persistence that survives password resets and user session revocation. This rule is intentionally simple and user-agent and OS-build independent, so it still fires when a kit changes its Dsreg user agent or spoofed OS build. Default hostnames are also common on legitimate personal or freshly imaged Windows devices, so this is a building block rule that does not generate alerts on its own. It captures the population of default-named registrations so it can be correlated with other signals (non-Dsreg user agents, spoofed OS builds, multiple registrations, or the AiTM chain) and baselined over time, with the intent to promote it to a standalone rule if the volume proves manageable.

Detection logic

data_stream.dataset:"azure.auditlogs" and event.action:"Register device" and
event.outcome:(success or Success) and
azure.auditlogs.properties.initiated_by.user.id:* and
azure.auditlogs.properties.target_resources.0.display_name:(DESKTOP-* or Device-* or Work*Pc*)