OAuth app investigation
How an AI SOC investigates a risky OAuth grant: list the app's scopes and users, check the publisher, trace what the token did, and revoke with approval.
The short answer
An OAuth app investigation decides whether a third-party app that users authorized is a risk, what data it reached, and whether to revoke it. Cotool's example OAuth Grant Responder runs this from a Google Workspace alert and asks #security before revoking the app everywhere.[1]
The problem
How an AI SOC handles it
Example
GET https://admin.googleapis.com/admin/reports/v1/activity/users/all/applications/token?maxResults=25The Reports API call for OAuth token activity across all users. Add an eventName filter, such as revoke, to narrow it.[7]
What people approve
How Cotool handles it
- Cotool's Detect page shows a Google Workspace OAuth grant detection that a tuning agent narrowed with the security team's register of approved apps.[5]
Integrations used
Sources
- Respond to every signal (Cotool Respond) · accessed November 16, 2026
- Microsoft Graph integration (Cotool docs) · accessed November 16, 2026
- Threat hunting (Cotool Hunt) · accessed November 16, 2026
- Alerts (Cotool docs) · accessed November 16, 2026
- Detection engineering (Cotool Detect) · accessed November 16, 2026
- Steal Application Access Token, T1528 (MITRE ATT&CK) · accessed November 16, 2026
- Manage OAuth token audit activity (Google Workspace Admin SDK) · accessed November 16, 2026


