Threat intelligence is the oldest idea in security and the hardest one to buy well. Every organisation already receives more of it than it can read: vendor feeds, government advisories, ISAC bulletins, open-source indicator lists, and the output of every tool it already owns. A threat intelligence platform is not sold to produce more of that. It is sold to decide which of it matters here, and to get that decision to somewhere it changes what happens.
The category has spent two years being absorbed. What is left is a market with two quite different halves, which are usually reviewed as though they were one.
Why this market exists
Intelligence that nobody acts on is a subscription, not a control. The problem a platform solves is the gap between a feed arriving and something changing: a block applied, a detection written, a patch prioritised, an engineering ticket raised. Most of the work is unglamorous. Deduplicate indicators arriving from nine sources. Decide which of them relate to anything you own. Attach enough context that an analyst can act without opening five tabs. Keep a record of what you knew and when, because that is what a regulator or an insurer asks for afterwards.
The second reason is that relevance is local. An indicator tied to a banking trojan matters enormously to a bank and not at all to a manufacturer whose exposure is a fleet of shipped devices running components chosen four years ago. A platform earns its price by knowing which of those you are.
What changed
The independents were bought, and not by security companies.
Mastercard acquired Recorded Future, the largest independent in the category, for $2.65 billion. The logic was that fraud data and threat data increasingly describe the same activity, and a payments network already sits where both land. Google folded Mandiant and VirusTotal into a single Google Threat Intelligence offering, selling one verdict on an indicator rather than a separate lookup in each. Dataminr, which detects events from public and social data in real time, bought ThreatConnect for $290 million to add the operational layer that turns a detection into a workflow.
Three of the best-known names in the category now sit inside a payments network, a hyperscaler and a real-time event detection business. None of those buyers is a traditional security vendor, which tells you what they think intelligence is for: it is a data asset that improves something they already sell.
Demand has not softened. Mordor Intelligence puts the market at $10.4 billion in 2026, up from $9.2 billion in 2025, and forecasts $18.9 billion by 2031. The money is going into consolidation rather than new entrants, which is the same pattern visible in cloud security.
The half nobody reviews
Everything above concerns intelligence about infrastructure: the estate you run, the identities in it, the indicators that suggest somebody is inside. It is built on indicators of compromise, and it is bought by a security operations team.
A second category has grown alongside it, driven by regulation rather than by attack volume. If your organisation ships products rather than only running systems, the question is not which indicator is active on your network, it is which vulnerable component is inside a device you sold three years ago and cannot easily reach. The Cyber Resilience Act, UNECE R155, IEC 62443-4-2 and PCI PTS all now demand a documented answer, and the unit of analysis is a bill of materials rather than an indicator.
PCA CERVUS, from the Hungarian firm PCA Cyber Security, is a clear example of the shape. It takes supplier SBOMs, validates the components against vulnerability intelligence, identifies which shipped products are affected, prioritises what is actually exploitable and routes the result to engineering rather than to a SOC. PCA are explicit that it complements a traditional platform rather than replacing one, and their own comparison is the clearest statement of the split: embedded products against general IT assets, device components as the model against indicators of compromise, engineering as the consumer against security operations.
Buyers in payments, automotive and industrial manufacturing increasingly need both, and they are not substitutes. An enterprise platform will not tell you that a component in a payment terminal shipped in 2023 is now exploitable. A product security platform will not tell you that someone is authenticating as your finance director.
How to evaluate one
Ask what it is intelligence about. Your infrastructure or your products. This decides the shortlist before any feature comparison, and getting it wrong is how organisations end up with a platform nobody in engineering will open.
Ask where the intelligence comes from. Proprietary collection, licensed feeds, open sources, or the vendor’s own customer telemetry. Each has a different failure mode, and a platform that mostly aggregates other people’s feeds is selling workflow, which is a legitimate thing to sell but a different one.
Ask what happens after the alert. A platform that raises an issue and stops has moved work rather than reduced risk. Look for the route into a ticket, a detection rule, a block, or an engineering backlog, and ask whether that route exists without a services engagement.
Ask how it decides relevance to you. Every vendor claims prioritisation. The question is what it is prioritising against: your asset inventory, your software bill of materials, your sector, or nothing but a generic severity score.
Ask who owns it after the pilot. Intelligence platforms are often bought by people who will not operate them. A platform nobody opens once the pilot ends has bought nothing, however good its collection is.
Where this ends up
The enterprise half is becoming a feature of larger platforms, and the remaining independents are competing on collection depth against buyers who have been told to consolidate. That is a difficult argument, though a real one for organisations whose risk justifies specialist collection.
The product half is growing for a reason that has nothing to do with attacker behaviour. Regulation created it, the deadlines are fixed, and the buyers are manufacturers who have never bought security intelligence before. It is the less crowded half, and the one where the evidence requirement is written into law.