SECOPS
Escalate OAuth grants by privileged users on-call
When an admin or other privileged user consents to a high-scope OAuth app, it pages the on-call security responder immediately and opens an incident.
How it runs
The automated pipeline, trigger to output.
- TriggerHigh-scope grant receivedHTTP webhook
- LogicCheck user against privileged roster
- ActionPage on-call security responderPagerDuty
- ActionPost incident summary to channelSlack
- OutputLog escalation for incident metricsDatadog
What it does
Applies the harshest scrutiny to the most dangerous combination: a privileged account (admin, finance, executive) granting broad OAuth scopes. A grant that would be routine from a standard user becomes a paging-worthy incident here, because compromise of a privileged consent can expose the whole tenant. It pages on-call and spins up an incident in one motion.
When to use it
Use this when privileged-account OAuth consent is a tracked incident-response trigger and a delayed review is unacceptable. It is the escalation tier above routine grant triage, reserved for accounts whose access could cascade.
How it works
- 1A webhook receives a high-scope consent grant.
- 2A logic step checks the consenting user against the privileged-account roster and exits if the user is standard.
- 3A PagerDuty incident is triggered for the on-call security responder with the app and scope context.
- 4An action posts the incident link and a one-line summary to the security channel.
- 5The final output logs the escalation event to the time-series store for later incident metrics.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect DatadogMetrics, traces, log search.
- 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.