Possible Rogue Device Registration in Entra ID (via azure)

PremiumReviewedSigma · Low · v1
Product
azure
Service
auditlogs
Author
HuntRule
Published
2026-10-18
Updated
2026-10-18

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects Entra ID device registration and join events that adversaries abuse to plant attacker-controlled devices for Primary Refresh Token acquisition. Unit 42 observed this technique with ROADtools during nation-state cloud intrusions to establish durable identity-based access.

Related detections7 linkedT1098.005 — drag to rearrange
Suspicious Token Request Using Microsoft Authentication Broker Client to Obtain Primary Refresh Token (via azure)
Suspicious Azure Tenant Root Elevation via elevateAccess
Suspicious AWS Virtual MFA Device Creation
Suspicious Device Registration Following OAuth Token Theft
Suspicious Workday Payment Election Change via Compromised Account (via workday)
Possible Rogue Device Registration in Entra ID After Device Code Phishing
Suspicious Exchange Online Mail Flow Rule or Connector Creation via Compromised Account
Possible Rogue Device Registration in Entra ID (via azure)
Pivot detection · T1098.005 · 7 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.