SECOPS
Open a PagerDuty Incident for High-Risk OAuth Grants
On a schedule, scans recent OAuth token grants in Google Workspace for high-blast-radius scopes (full Drive, Gmail send.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled scan of active OAuth tokens
- ActionEnumerate workspace OAuth tokens and scopesGoogle Drive
- LogicKeep only high-blast-radius scope grants
- LogicDrop apps on the approved-vendor allowlist
- ActionOpen PagerDuty incident per flagged grantPagerDuty
- OutputPost incident link to security Slack channelSlack
What it does
This workflow treats a dangerous OAuth grant as a security incident, not just a notification. On a recurring scan it lists tokens issued across the workspace, filters for the scopes that let an app read all mail, modify every file, or act as an admin, checks each app against your approved-vendor allowlist, and pages the on-call security engineer through PagerDuty for anything that slips through.
When to use it
Use it when over-permissioned OAuth apps need an SLA-backed response, not a Slack message that scrolls away. Good for regulated environments where an unsanctioned app with mailbox-wide access must be acknowledged and remediated within a defined window.
How it works
- 1A schedule triggers the scan every few hours.
- 2The flow enumerates active OAuth tokens and their scopes from the Workspace directory.
- 3A logic step keeps only grants holding high-blast-radius scopes.
- 4A second logic step drops any app present on the approved-vendor allowlist.
- 5For each remaining grant, the flow opens a PagerDuty incident with the app, user, and scopes.
- 6A Slack note links the incident so the channel has context.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.