SECOPS
Log Phishing Indicators to a Living Blocklist
Whenever a phishing verdict is confirmed, this records the sender, URLs, and domains to a Postgres IOC ledger, deduplicates against prior incidents, and flags repeat campaigns.
How it runs
The automated pipeline, trigger to output.
- TriggerConfirmed-verdict webhook receivedHTTP webhook
- ActionNormalize indicators
- LogicLook up indicators in IOC ledgerPostgres
- ActionInsert new or increment sighting countPostgres
- OutputAlert on repeat-campaign matchSlack
What it does
Builds an institutional memory of phishing indicators. Each confirmed verdict appends its senders, URLs, and domains to a Postgres indicator ledger, checks whether those indicators have appeared before, and surfaces when a campaign is a repeat or escalation of a known one.
When to use it
Use this when reports keep coming from the same actors and you want a queryable blocklist plus campaign correlation instead of scattered tickets. It is the system-of-record backbone other phishing workflows can read from.
How it works
- 1A confirmed-verdict webhook delivers the indicator set.
- 2Each indicator is normalized (lowercased domains, stripped URL params).
- 3A Postgres lookup checks whether any indicator already exists in the ledger.
- 4New indicators are inserted; matches increment a sighting count and link to the prior incident.
- 5If indicators match a known campaign, an alert posts to Slack so responders know it's a repeat actor.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.