SECOPS
Triage newly consented high-scope OAuth apps
Catches OAuth consent-grant events as they happen, flags grants that request high-risk scopes, and posts a triage card to your security channel with the app, scopes…
How it runs
The automated pipeline, trigger to output.
- TriggerConsent-grant event receivedHTTP webhook
- LogicMatch against high-risk scope list
- ActionPost triage card to security channelSlack
- OutputAppend flagged grant to audit sheetAirtable
What it does
Watches your identity provider's audit stream for new third-party OAuth consent grants. When an app is authorized against a sensitive scope (full mailbox, drive-wide read, directory read, send-as), it raises a triage notice instead of letting it pass silently. Low-scope grants are dropped so the channel stays signal-rich.
When to use it
Run this when your org allows users to self-consent to OAuth apps and you need real-time visibility into which apps are gaining broad access. It is the front door of an OAuth audit program: catch the grant the moment it lands, before the app has done anything with the access.
How it works
- 1A webhook fires on each new consent-grant event from your IdP audit log.
- 2A logic step compares the requested scopes against a configured high-risk scope list and exits quietly when none match.
- 3A Slack message is posted to the security channel with the app name, publisher, consenting user, scope list, and grant timestamp.
- 4The final output appends the same record to an audit sheet so every flagged grant has a durable row for later review.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect AirtableBases, tables, views, automations.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.