Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Feed quality measures whether a threat intelligence source is accurate, timely, relevant, and well maintained. Volume is the one metric that tells you nothing useful.

What Is Threat Feed Quality?
Buy three threat feeds and you will find the same domain in all three, dated differently, with no indication of which source saw it first or whether any of them still believes it is hostile. Feed quality is the discipline of answering those questions before the data reaches a blocking rule. It matters because a poor feed is not merely useless—it generates false positives that erode analyst trust and, at the gateway, breaks legitimate traffic.
Vendors quote indicator counts because the number is large and easy to compare. It correlates with nothing you care about. A feed of ten million hashes of commodity malware samples, each seen once, generates enormous storage and processing cost and almost no detections, because file hashes change with every build. The same vendor’s 400 well-researched domains tied to an actor active against your industry will produce more value in a month. Ask for detections rather than entries: how many alerts did this source generate in the trial, how many were true positives, and how many would you have caught another way?
Run the evaluation before the contract, over at least 30 days, with every candidate feed ingested side by side into a staging index rather than into production blocking. Record for each source the number of indicators delivered, the overlap percentage with every other source, the number of hits against your real telemetry, the true positive rate of those hits, and the median age of an indicator at the time of its first hit. Those five numbers settle most purchasing arguments, and they frequently show that the cheapest source contributed the most unique detections.
Afterwards, keep scoring. Assign each source a confidence weight, decay indicators on a schedule appropriate to their type—shorter for addresses, longer for actor-registered domains—and route only high-confidence, high-relevance entries to automatic blocking. Everything else belongs in enrichment and hunting, where a false positive costs an analyst five minutes instead of costing the business an outage.
Feeds delivered as STIX over TAXII make quality measurable, because the format carries producer identity, confidence, creation time, and an expiry field. A CSV of addresses carries none of that, so you cannot deduplicate honestly or retire entries automatically. When a vendor offers both, take the structured version even if it is more work to ingest. The same applies to reputation feeds, where a score and category beat a flat blocklist every time.
Every feed reflects where its producer can see. A vendor with a large endpoint estate in North America reports what that estate meets; a European sector ISAC reports what its members meet. Neither is wrong, both are partial, and the gap is why sector sharing often outperforms a larger commercial source for relevance. In the UK, CiSP membership costs nothing and carries sector groups, which makes it the sensible baseline to measure paid feeds against rather than an afterthought.
At Privia Security, we evaluate and tune intelligence sources for clients as part of our SOC maturation services, measuring detections produced rather than indicators delivered.
Fewer than most teams assume. Two or three well-chosen sources with low overlap and strong relevance to your industry outperform a dozen that repackage the same open data. Add a sector sharing community, which is often free, and measure the unique detections each source contributes. Drop any that produce nothing unique over a quarter.
It depends entirely on what the feed drives. For automatic blocking at a gateway, anything above about one per cent will eventually cause a business-visible outage, so only high-confidence entries belong there. For enrichment and hunting, a much higher rate is tolerable because the cost of a wrong entry is analyst time rather than broken traffic.
Yes, and you should insist on it. Ask for a 30-day trial delivered to a staging index, run it beside your existing sources, and measure overlap, unique hits against your own telemetry, and true positive rate. Vendors who will not supply a trial with raw data, only a portal demonstration, are asking you to buy on their metrics rather than yours.
Because infrastructure is reused. Cloud providers reassign addresses within days, compromised websites are cleaned, and a domain seized by law enforcement may later be used for sinkholing. Without expiry your blocking list grows without limit and the oldest entries become the most dangerous, since they are the most likely to now belong to a legitimate service.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.