SECOPS
Phishing URL and IOC Enrichment
Takes a reported phishing email submitted via webhook, extracts every URL and sender indicator, enriches them against threat-intel lookups.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives reported email payloadHTTP webhook
- ActionExtract and de-dupe URLs, domains, senders
- ActionEnrich indicators with reputation lookupsExa
- LogicRoll up indicators into case verdict
- ActionWrite enriched case to PostgresPostgres
- OutputPost verdict summary to SlackSlack
What it does
Automatically enriches the indicators in a reported phishing email. It pulls every URL, domain, and sender address out of the report, runs each through reputation and reachability checks, and produces a consolidated verdict with the supporting evidence attached.
When to use it
Use this when your intake already exists but analysts still copy-paste URLs into separate tools to judge them. It standardizes enrichment so every report lands with a malicious / suspicious / clean verdict and evidence trail.
How it works
- 1An intake system POSTs the reported email payload to the webhook trigger.
- 2URLs, domains, and sender addresses are extracted and de-duplicated.
- 3Each indicator is enriched: reputation and web context lookups gather hosting, age, and known-bad signals.
- 4A scoring step rolls the per-indicator findings into a single case verdict.
- 5The enriched case, with verdict and evidence, is written to a Postgres case table and a summary is posted to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ExaNeural search across the web.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
Scheduled AWS Access-Key Age Sweep and Forced Rotation
Runs daily to find IAM access keys older than your policy threshold, deactivates the stale key, issues a fresh pair, and notifies the key owner with their replacement instructions.
Correlate Datadog WAF anomaly alert with Cloudflare evidence
When Datadog fires a WAF block-rate anomaly monitor, it pulls the matching Cloudflare firewall events, builds an evidence pack of top rules and ASNs.
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.
Non-Rotatable Leaked Secret to PagerDuty Escalation
Catches secret-scan hits for credentials that cannot be auto-rotated, gathers blast-radius context, and pages the on-call engineer with a step-by-step manual rotation runbook.
GitHub Secret-Scan Hit to Auto-Revoke and Rotate
When GitHub secret scanning flags a leaked credential in a repo, it auto-classifies the secret type, revokes the live key at the provider, mints a replacement.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.