SECOPS
Bulk IOC Enrichment to Threat Watchlist
On a schedule, pulls newly reported phishing IOCs, batch-enriches them with reputation and geolocation data, deduplicates against your existing watchlist.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled enrichment run
- LogicFilter out known and allowlisted IOCs
- ActionBatch-enrich IOCs via reputation APIHTTP webhook
- LogicKeep only above-threshold malicious IOCs
- ActionUpsert confirmed IOCs to blocklist tablePostgres
- OutputPost run summary to SlackSlack
What it does
Keeps an internal threat watchlist current. It gathers IOCs collected since the last run, enriches each in batch, drops duplicates and known-good indicators, and persists confirmed-malicious ones to a Postgres table your firewall and mail filters can sync from.
When to use it
Run this when individual reports are already triaged but you need a clean, deduplicated blocklist that downstream controls consume. It's the back-of-house job that converts ad-hoc reports into durable, queryable defense data.
How it works
- 1A scheduled trigger fires (e.g. every hour) and reads IOCs reported since the last watermark.
- 2A logic step filters out indicators already present in the watchlist and obvious internal/allowlisted entries.
- 3Remaining IOCs are batch-enriched against a reputation and geolocation API over HTTP.
- 4A logic step keeps only indicators scoring above the malicious threshold.
- 5The confirmed-malicious IOCs are upserted into the Postgres blocklist table with first-seen and source metadata.
- 6A run summary — counts added, skipped, and flagged for review — is posted to Slack.
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.