SECOPS
Escalate Breaches of Tier-1 SSO Vendors to On-Call
When a disclosed breach hits a vendor marked critical in your SSO inventory, it opens a PagerDuty incident and posts the context to Slack so on-call responds immediately.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled critical-vendor scan
- ActionFetch newly disclosed breachesExa
- ActionLoad inventory with criticality tiersAirtable
- LogicKeep only tier-1 vendor matches
- ActionOpen PagerDuty incidentPagerDuty
- OutputPost incident context to SlackSlack
What it does
It separates a breach you should sleep on from a breach you must page someone for. The workflow only escalates when the breached vendor is tagged tier-1 or critical in your app inventory, so on-call isn't woken for low-impact disclosures. Everything else is logged silently.
When to use it
Use it when you have an established severity tiering on your SSO apps and want true 24/7 coverage for breaches of the vendors that hold your crown-jewel data or sit in your auth path. Pairs well with the broader breach-watch matcher running alongside it.
How it works
- 1A scheduled run kicks off the scan.
- 2Exa retrieves newly disclosed breaches across the configured sources.
- 3Airtable supplies the SSO inventory with each vendor's criticality tier.
- 4A branch keeps only breaches whose matched vendor is tier-1 or critical.
- 5For each critical match it opens a PagerDuty incident with the vendor, blast radius, and source link.
- 6It posts a parallel Slack note to the incident channel so responders have the same context without leaving chat.
Set it up
What you configure once, before turning it on.
- 1Connect ExaNeural search across the web.
- 2Connect AirtableBases, tables, views, automations.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.