SECOPS

Real-Time Alert on New High-Risk OAuth App Consent

Listens for new third-party OAuth consent events via webhook, scores the requested scopes instantly, and pings security in Slack within seconds when a user grants a high-risk app.

CategorySecOps
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWebhook receives new consent eventHTTP webhook
  • LogicExtract app, user, and requested scopes
  • LogicRisk-gate on scope sensitivity
  • ActionEnrich with publisher verification statusOutlook
  • OutputPost urgent alert to security SlackSlack

What it does

Watches for the moment a user consents to a new third-party OAuth application and, when the requested permissions are high-risk, raises an immediate alert so security can investigate before the grant is abused.

When to use it

Use this when periodic scans aren't fast enough — for example to catch consent-phishing attacks where an attacker tricks a user into authorizing a malicious app. Pairs well with a weekly scan that covers the rest.

How it works

  1. 1An incoming webhook receives the audit-log consent event from your tenant's event stream.
  2. 2The flow extracts the app identity, the consenting user, and the requested scopes.
  3. 3A risk gate evaluates the scopes; benign sign-in-only grants are dropped, while mail, files, or directory access trigger the alert path.
  4. 4For flagged grants it enriches with the app's publisher verification status.
  5. 5An urgent message is posted to the security Slack channel with the user, app, scopes, and a one-click context for follow-up.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect OutlookMail, calendar, contacts.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.