Azure AD Sign-in Logs: Detect ROPC Authentication Flow Use in Application Sign-ins

Flags Azure AD sign-ins where the message indicates an application is using the ROPC authentication flow.

FreeReviewedSigma · Medium · v5
Product
azure
Service
signinlogs
Author
Mark Morowczynski '@markmorow', Bailey Bercik '@baileybercik' (SigmaHQ), DRL 1.1
Published
2022-06-01
Updated
2026-07-31

ATT&CK techniques

Initial Access → Defense Evasion
  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 flags sign-in events in Azure AD sign-in logs where the sign-in message contains "ROPC", indicating use of the Resource Owner Password Credentials authentication flow. Attackers may prefer ROPC because it requires direct handling of user passwords by the application, increasing credential exposure risk. The detection relies on the presence of the "ROPC" indicator in the logged message field.

Related detections9 linkedT1078 — drag to rearrange
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
Suspicious SmarterMail Force Password Reset API Request Indicating Account Takeover
Suspicious Mailbox Forwarding Rule Creation Following AiTM Phishing
Azure AD Sign-in Logs: Detect ROPC Authentication Flow Use in Application Sign-ins
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.