What a threat intelligence feed is
A feed is data your tools can read without a person copying it in. It updates on a schedule, often every few minutes or hours. Each item has a type, a value, a time and usually a source.
The difference from a report is speed and structure. A report is written for people. A feed is written for machines, so your SIEM can match it against your own logs.
The four main types
- Indicator feeds. IP addresses, domains, URLs and file hashes linked to malware or attacks. You block or alert on them.
- Vulnerability feeds. New CVEs and which ones attackers are exploiting now. You use them to decide what to patch first.
- Dark web and leak-site feeds. Posts on ransomware leak sites, criminal forums and Telegram channels that name organisations, plus access sales and leaked data. You use them to learn when a client is named.
- Threat actor feeds. Which groups are active, what they target and how they work. You use them for briefings and to set priorities.
The formats you will meet
- JSON over a REST API. The most common. Your script or SIEM polls an endpoint and keeps a cursor so it fetches only new items.
- STIX over TAXII. A standard format and transport for sharing threat data between organisations and platforms.
- Webhooks. The provider pushes each new item to your endpoint as it happens, signed so you can check it is genuine.
- CSV and plain lists. Simple block lists of IPs or domains, often used by free feeds.
Free and paid feeds
Free feeds, such as community-run indicator lists and government advisories, are a good start for blocking known bad infrastructure. They rarely tell you that your client in particular has been named.
Paid feeds add sources that are hard to collect, such as closed forums, leak sites and stealer logs, plus support and uptime commitments. Judge a paid feed by how many of its items are about your clients and how fast they arrive.
How MSSPs turn feeds into service
- Filter the feed to each client's domains, brands, suppliers and industry.
- Send matches to the channel your team watches: SIEM, ticketing, Slack or Teams.
- Check each match against the client's own logs before you raise an incident.
- Report what you found, and what you checked, in a monthly client report.
Our SIEM integration guide shows this step by step for Splunk, Sentinel, QRadar and Elastic.
The AdverseMonitor feed
AdverseMonitor provides a dark web and ransomware feed: posts from leak sites, criminal forums, Telegram channels and the open web that name the domains and companies you monitor.
- Read it through the AdverseMonitor API as JSON. MSSP Pro allows 1,000 requests a day and MSSP Scale 10,000.
- Or receive each new match as a signed webhook, which fires for exactly the matches your alerts get.
- It does not offer STIX or TAXII today, and it does not include indicator or vulnerability feeds.
Read how teams use it in five dark web monitoring API workflows.
