SECOPS
Auto-Purge Confirmed Phishing Across All Mailboxes
When an analyst confirms a phishing verdict, this searches every mailbox in the org for messages matching the malicious sender, subject, and URL.
How it runs
The automated pipeline, trigger to output.
- TriggerConfirmed-phishing webhook receivedHTTP webhook
- LogicVerify signature and confirmed verdict
- ActionSearch all org mailboxes for matchesGmail
- ActionPurge matching messages org-wideGmail
- OutputPost containment report to channelSlack
What it does
Contains a confirmed phishing campaign before more users click. Given a confirmed indicator set, an agent fans out across the organization's Gmail mailboxes, finds every copy of the malicious message by sender, subject fingerprint, and embedded URL, purges them, and returns a containment summary.
When to use it
Use this immediately after triage confirms a message is malicious and you suspect it was blasted to many recipients. It replaces the slow, error-prone process of an admin running manual searches mailbox by mailbox.
How it works
- 1A webhook from your triage tool fires with the confirmed indicators (sender, subject hash, URL).
- 2A guard step verifies the payload is signed by your triage system and the verdict is genuinely "confirmed".
- 3The agent enumerates org mailboxes and runs a matching search across each one.
- 4Every matching message is moved to trash and permanently purged.
- 5A containment report listing affected users and deleted counts posts to Slack for the incident record.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GmailRead, draft, send, label.
- 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.