SECOPS
Detect Sudden OAuth Grant Spikes for One App
Monitors OAuth authorization events and alerts when a single third-party app is granted access by an unusual number of users in a short window.
How it runs
The automated pipeline, trigger to output.
- TriggerOAuth authorize event from audit logGoogle Drive
- ActionAppend app, user, and timestamp to grant logPostgres
- LogicCount distinct grantees per app over rolling window
- LogicBranch when an app exceeds the spike threshold
- OutputAlert security in Slack with app, count, and scopesSlack
What it does
This workflow looks for the pattern that single-grant reviews miss: many users authorizing the same unfamiliar app in a short span. That spike is a classic consent-phishing fingerprint and also catches a risky tool spreading by word of mouth. It counts grants per app over a rolling window and alerts when any app crosses your threshold.
When to use it
Use it as a defense against OAuth consent-phishing campaigns, where an attacker tricks staff into granting a malicious app mailbox or Drive access. It is also useful for catching shadow-IT tools going viral internally before they hold half the company's data.
How it works
- 1The audit-log webhook fires on each OAuth authorize event.
- 2The flow records the app, user, and timestamp to a running grant log in Postgres.
- 3A logic step counts distinct grantees per app over the rolling window.
- 4When an app exceeds the spike threshold, the flow branches to alerting.
- 5A Slack alert names the app, the grant count, the scopes, and the affected users so security can move to revoke.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.