SECOPS

Over-Scoped OAuth App Revocation Review Queue

Scans OAuth grants for apps holding high-risk scopes that exceed a policy threshold and opens a Linear revocation-review ticket for each, with owner, scopes, and a decision…

CategorySecOps
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled audit run
  • ActionEnumerate OAuth grants and scopesOutlook
  • LogicFilter to apps exceeding scope policy
  • LogicDedupe against existing open tickets
  • OutputOpen a Linear revocation-review ticket per appLinearLinear

What it does

Identifies OAuth applications whose granted scopes exceed your organization's allowed risk threshold and turns each into an actionable Linear ticket so a human owner can approve, restrict, or revoke the grant.

When to use it

Use this once you have a defined scope policy and need to route over-scoped apps into a tracked review workflow rather than leaving findings in a report nobody actions. Ideal for teams that already triage security work in Linear.

How it works

  1. 1A schedule triggers the audit on your chosen cadence.
  2. 2It enumerates OAuth app grants and their scopes from the Microsoft tenant.
  3. 3A policy filter keeps only apps holding scopes above the threshold (e.g. mail.readwrite, full directory access, broad offline_access).
  4. 4For each remaining app it deduplicates against existing open tickets so it never files the same app twice.
  5. 5A Linear issue is created per new finding with the app name, risky scopes, consenting users, and a default review deadline assigned to the security owner.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  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.