SECOPS
Open a revoke-review ticket for risky OAuth grants
Turns each flagged high-scope OAuth grant into a Linear review ticket with the app details and a revoke decision checklist.
How it runs
The automated pipeline, trigger to output.
- TriggerHigh-scope grant receivedHTTP webhook
- LogicDedupe against recent app+user grants
- ActionCreate revoke-review issueLinear
- ActionAssign to on-rotation reviewerLinear
- OutputPost ticket link to security channelSlack
What it does
Converts a flagged OAuth grant into a tracked review item. Each risky grant becomes a Linear issue containing the app identity, requested scopes, the user who consented, and a structured checklist for the reviewer to decide whether to keep or revoke. Nothing is auto-revoked; a human makes the call with full context.
When to use it
Use this when OAuth grant review needs an accountable owner and an audit trail rather than a fire-and-forget alert. It fits orgs with a security backlog in Linear who want every high-scope grant to land as an actionable, assignable, time-bound task.
How it works
- 1A webhook receives a grant that an upstream filter has already marked high-scope.
- 2A logic step deduplicates against recent app+user pairs so a re-consent does not spawn a duplicate ticket.
- 3A Linear issue is created with a templated body: app, publisher, scopes, consent time, and a keep/revoke checklist.
- 4The issue is labeled by risk tier and assigned to the on-rotation reviewer.
- 5The final output posts the ticket link to the security channel so the team sees it surface in real time.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.