SECOPS
Snowflake Egress Cluster Hunt to Discord Report
Hunts archived Cloudflare egress logs in Snowflake on a daily schedule to cluster low-and-slow exfiltration patterns, then posts a ranked summary report to a Discord SOC channel.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts hunt
- ActionQuery Snowflake, cluster egress transfersSnowflake
- LogicScore clusters (volume, beaconing, rarity)
- LogicFilter + rank above hunt threshold
- ActionDraft analyst summaries per clusterOpenAI
- OutputPost ranked digest to DiscordDiscord
What it does
Runs a daily threat hunt across long-window Cloudflare egress logs in Snowflake to catch slow-drip exfiltration that single-event alerting misses. It clusters related transfers by source, destination, and timing, ranks the suspicious clusters, and delivers a digest to Discord.
When to use it
Use it for retrospective hunting when attackers spread exfiltration thin to stay under per-event thresholds. Good for teams warehousing months of logs in Snowflake who want a daily, human-readable hunt digest.
How it works
- 1A daily schedule trigger starts the hunt.
- 2A Snowflake action queries the trailing egress window and groups transfers into candidate clusters.
- 3A logic step scores each cluster on cumulative volume, beaconing regularity, and destination rarity.
- 4A filter logic step keeps only clusters above the hunt threshold and ranks them.
- 5An OpenAI action drafts a concise analyst-readable summary for each top cluster.
- 6A Discord output posts the ranked digest with links back to the underlying queries.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect DiscordCommunity channels + voice + bots.
- 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.
