SECOPS
Egress IOC Ledger Enrichment Agent
An agent that takes a new indicator from an egress investigation, enriches it across reputation and search sources, and appends a scored.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives new indicatorHTTP webhook
- ActionPull reputation + passive DNSOpenAI
- ActionGather open-source contextExa
- LogicScore confidence + dedupe vs ledger
- ActionWrite/merge IOC ledger row in NotionNotion
What it does
Given an indicator (IP, domain, or hash) surfaced during an egress investigation, an agent gathers reputation and open-source context, decides whether it is novel or already tracked, and appends a fully enriched, scored row to the central IOC ledger. Duplicates are merged rather than re-added.
When to use it
Use it when analysts paste raw indicators into a case and want the tedious enrichment-and-bookkeeping done for them, keeping one authoritative IOC ledger across all egress investigations.
How it works
- 1A webhook trigger receives a new indicator from an active investigation.
- 2An enrichment action pulls reputation, passive DNS, and category data for the indicator.
- 3A web-search action gathers open-source mentions and recent campaign context.
- 4The agent reasons over the evidence to assign a confidence and threat score and decide novel-vs-known.
- 5A logic step dedupes against the existing ledger, merging into the prior row when matched.
- 6A Notion action writes or updates the IOC ledger entry with sources cited.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ExaNeural search across the web.
- 4Connect NotionPages, databases, comments.
- 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
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.