SECOPS

Triage Newly Authorized OAuth Apps by Scope Risk

Watches the Google Workspace audit log for new third-party OAuth grants, scores each app's requested scopes for risk.

CategorySecOps
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew OAuth authorize event in Workspace audit logGoogle DriveGoogle Drive
  • ActionExtract app name, grantee, and requested scopesGoogle DriveGoogle Drive
  • LogicScore scopes against risk table; tag low/medium/high
  • LogicBranch: route only high-risk grants to alerting
  • OutputPost triage card with approve/revoke buttons to SlackSlack

What it does

This workflow catches the moment a user connects a new third-party app to your Google Workspace and immediately judges how dangerous the grant is. It reads the OAuth scopes the app requested, classifies them (read-only calendar is low; full Drive or Gmail send is high), and posts a triage card to Slack so security sees risky grants within minutes instead of at the next quarterly audit.

When to use it

Use it when employees can self-authorize SaaS tools against Workspace and you want a real-time tripwire for over-permissioned apps. Ideal for teams without a formal app-vetting gate who still need to know when someone grants an unknown vendor write access to all company files.

How it works

  1. 1The audit-log webhook fires on a new `authorize` token event in Google Workspace.
  2. 2The flow pulls the app name, grantee, and full scope list from the event payload.
  3. 3A logic step scores the scopes against a risk table and tags the grant low, medium, or high.
  4. 4Low and medium grants are logged to a sheet; high-risk grants branch to alerting.
  5. 5A Slack message delivers the app, user, scopes, and risk score with approve/revoke buttons to the security channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.