Suspicious OAuth Application Consent or Permission Grant (via auditlogs)

PremiumReviewedSigma · Medium · v1
Product
azure
Service
auditlogs
Author
HuntRule
Published
2026-11-06
Updated
2026-11-06

ATT&CK techniques

Cred Access
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects an Entra ID user or admin granting OAuth consent or delegated API permissions to an application, the mechanism behind consent-phishing attacks that give an adversary-controlled app persistent access to mail and data without a password. Malicious OAuth app registration and consent is a prominent phishing technique in the Red Canary Threat Detection Report. Detecting consent and permission-grant operations surfaces illicit application access before data is exfiltrated.

Related detections9 linkedT1528 — drag to rearrange
Malicious Context.ai OAuth Application Authorization by Client ID (via google_workspace)
Suspicious Entra ID ROPC Authentication Bypassing MFA
Suspicious Consent to Application Grant in Entra ID
Malicious Azure AD Application Consent Granted with Mail Permissions
Suspicious Device Code Authentication via Microsoft Authentication Broker
Suspicious Microsoft 365 OAuth Authorization to Visual Studio Code Client
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious Google Workspace OAuth Authorization for Chrome Web Store Scope via Token Audit
Suspicious OAuth Application Consent Grant via Azure Audit Logs
Suspicious OAuth Application Consent or Permission Grant (via auditlogs)
Pivot detection · T1528 · 9 related

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