SECOPS
Confirmed Exfil Containment and Remediation Tracker
When an analyst confirms an egress event as exfiltration, this blocks the destination at Cloudflare, files a tracked remediation ticket in Linear.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: investigation confirmed exfilHTTP webhook
- LogicValidate verdict, extract destination + IOCs
- ActionApply Cloudflare block rule on destinationCloudflare
- ActionOpen Linear remediation ticketLinear
- OutputNotify incident channel on MS TeamsMicrosoft Teams
What it does
Acts on a confirmed verdict: once an analyst marks an egress investigation as true-positive exfiltration, it pushes a block rule for the malicious destination at Cloudflare, opens a Linear remediation ticket pre-populated with the case and IOCs, and alerts the incident channel.
When to use it
Use it as the response stage after triage, when you want confirmed exfil to trigger consistent containment and a tracked remediation owner instead of ad-hoc manual steps. Pairs with the investigation-dossier and IOC-ledger workflows.
How it works
- 1A webhook trigger fires when an investigation is marked confirmed exfiltration.
- 2A logic step validates the verdict payload and extracts the destination and IOC set.
- 3A Cloudflare action applies a block/firewall rule against the malicious destination.
- 4A Linear action opens a remediation ticket with the case summary, IOCs, and assigned owner.
- 5An MS Teams output notifies the incident channel with containment status and the ticket link.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect Microsoft TeamsChannels, chats, files.
- 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.