huntrule

Azure Sign-In: Successful single-factor atRisk logins from non-registered devices

Alerts on at-risk successful Azure sign-ins from devices with missing trust type when MFA isn’t required.

FreeReviewedSigma · High · v5
Product
azure
Service
signinlogs
Author
Harjot Singh, '@cyb3rjy0t' (SigmaHQ), DRL 1.1
Published
2023-01-10
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Initial Access → Defense Evasion

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies successful Azure sign-ins marked as atRisk where only single-factor authentication was used and the sign-in device trust type is empty or null. Attackers may use low-assurance device states to blend into normal activity while maintaining access without triggering stronger MFA requirements. Detection relies on Azure sign-in log telemetry fields including authentication requirement, risk state, sign-in status, and device detail trust type.

Reporting behind it

Related detections9 linkedT1078 — drag to rearrange
Suspicious SonicWall NetExtender VPN Command-Line Authentication with Always-Trust (via process_creation)
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious SSH Daemon Configuration Change Enabling Root Login
Suspicious NTLM Network Logon From Attacker Controlled Workstation Names (via security)
Suspicious dMSA Object Access with Migration AccessMask
Malicious ESX Admins Group Added to Privileged Directory Group
Malicious ESX Admins Group Creation via WinRM Host
Suspicious BrightMetricAgent Remote Tool Execution Associated With Volt Typhoon
Azure Sign-In: Successful single-factor atRisk logins from non-registered devices
Pivot detection · T1078 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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