SECOPS
Quarterly OAuth grant recertification sweep
Each quarter inventories every standing OAuth grant in the tenant, flags stale or unused high-scope apps.
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly recertification schedule
- ActionQuery full active-grant inventoryHTTP webhook
- LogicFlag stale, inactive, or orphaned grants
- ActionBuild recertification checklist databaseNotion
- OutputNotify owners that review window is openSlack
What it does
Closes the loop on grants that were approved once and never revisited. On a quarterly cadence it pulls the full standing inventory of third-party OAuth grants, flags those that hold high scopes but show no recent activity or whose owner has offboarded, and builds a recertification checklist requiring an explicit keep-or-revoke decision on each.
When to use it
Use this for periodic access-review compliance (SOC 2, ISO 27001) where every standing integration must be recertified on a schedule. It catches the slow accumulation of forgotten apps that real-time triage misses entirely.
How it works
- 1A scheduled trigger fires at the start of each quarter.
- 2An action queries the IdP for the complete list of active OAuth grants.
- 3A logic step flags grants that are high-scope and stale, inactive, or owned by departed users.
- 4An action builds a recertification database with one reviewable row per flagged grant and a decision field.
- 5The final output notifies grant owners and the security lead that the recertification window is open with the link.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect NotionPages, databases, comments.
- 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.