SECOPS
OAuth Grant Auto-Revoke on Blocklist Match
When a new OAuth grant appears, it checks the app and its scopes against a policy blocklist and, on a match.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: new OAuth app grantHTTP webhook
- ActionLoad policy blocklist and allowlistPostgres
- LogicBranch: blocklist match?
- ActionRevoke grant via Cloudflare Access / IdPCloudflare
- OutputOpen PagerDuty incident with contextPagerDuty
What it does
Enforces a hard OAuth policy without waiting for a human. When a new third-party grant is detected, it checks the app identity and requested scopes against a blocklist stored in Postgres (denied vendors, banned scope combinations like full Drive plus external sharing). If it matches, the flow revokes the grant immediately through Cloudflare Access / IdP API and pages on-call so a human knows a block fired.
When to use it
Use this when certain scope combinations or vendors are categorically not allowed and you want enforcement to happen in seconds, with an alert rather than an approval gate. Best for high-sensitivity environments.
How it works
- 1A webhook fires on a new OAuth grant event.
- 2The flow loads the policy blocklist and allowed-vendor list from Postgres.
- 3A logic branch evaluates the grant against the blocklist rules.
- 4On a match, an action call revokes the grant via the Cloudflare Access / IdP integration.
- 5A PagerDuty incident is opened with the app, user, scopes, and revoke result.
- 6Non-matching grants are logged to Postgres and pass through silently.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.