Source: The Red Canary Blog: Information Security Insights
Author: Matt Graeber
URL: https://redcanary.com/blog/threat-detection/entra-id-oauth-attacks/
ONE SENTENCE SUMMARY:
Red Canary models an Entra ID OAuth consent attack using ChatGPT, outlining investigative questions, required AuditLogs, and remediation strategies.
MAIN POINTS:
- Threat research pivots from observed OAuth attacks to anticipate evolving adversary techniques.
- Hypothetical Entra ID scenario uses ChatGPT to gain Microsoft Graph email access.
- A non-admin user consented to Mail.Read, offline_access, profile, and openid permissions.
- The event includes precise timestamp, tenant, user, app IDs, and source IP.
- ChatGPT service principal matched the legitimate OpenAI application, not an impersonator.
- Mail.Read is highlighted as a frequently abused permission prompting investigation.
- Investigation aims to confirm user intent and possible coercion into granting consent.
- Authorization questions assess whether email-reading access is appropriate for the app.
- Tenant governance concerns include whether the application is sanctioned internally.
- Correlated Log Analytics AuditLogs required: “Consent to application” and “Add service principal.”
TAKEAWAYS:
- Treat high-impact OAuth permissions like Mail.Read as investigation triggers even for known apps.
- Validate application authenticity and publisher identity to detect lookalike OAuth abuse.
- Determine user intent and potential social engineering behind non-admin consent actions.
- Use CorrelationId to link consent events with service principal creation for complete timelines.
- Enforce tenant sanctioning and approval workflows to reduce risky third-party OAuth access.