Recomputed on every load

Who covers what in cyber security

By Nick Forshteyn · CISO AI
Figures as at 18 November 2026

We read and tag every cyber security story we can find. Across 3495 of them from 35 outlets, the interesting result is not what gets covered. It is how differently each subject is covered: across its 31 stories, CISA advisory is 93.5% one outlet, while Microsoft, at 78 stories, is split across 19 outlets with none holding more than 14.1%.

How this is measured. Every story CISO AI holds, published between 23 May 2025 and 18 November 2026: 3495 in total from 35 outlets, counting the 53 publishers whose stories arrive through the financial wire as one. 7 outlets silent for more than a week and far longer than their usual gap are marked as last seen and cannot carry a headline claim. Each is summarised and tagged by topic when it arrives, and a story usually carries several tags, so topic shares sum past 100%. Counts are of stories, not words. These figures are computed when you load the page, so they move as the archive grows. The limitations are set out at the end, and they matter.

Some subjects have an owner. Others have nobody.

For each topic we count how many distinct outlets covered it and what share the leading outlet holds. Topics with fewer than 8 stories are excluded, because below that one extra story swings the percentage wildly. The two topics named above clear a higher bar again — 25 stories and 3 outlets — because a headline claim should not turn on a sample small enough for one outlet's back catalogue to move.

TopicStoriesOutletsLeading outletIts share
AI security 529 30 The Hacker News 17.4%
Vulnerability 358 22 The Hacker News 39.9%
data breach 355 17 Financial press wire 25.9%
Patch Management 335 25 The Hacker News 41.2%
vulnerability management 257 24 The Hacker News 23%
Phishing 254 25 The Hacker News 29.1%
cryptocurrency 249 10 Financial press wire 79.5%
malware 193 20 The Hacker News 46.6%
Stories per topic, for the 8 largest topics. A story usually carries several tags, so topics overlap and the counts deliberately do not sum to 3495.

CISA advisory is effectively CISA. Of its 31 stories, that one outlet wrote 29, and only 3 outlets covered the subject at all. Skip that publication and you miss 93.5% of it.

Microsoft is the opposite. At 78 stories it is spread across 19 outlets, with the largest, Dark Reading, holding just 14.1%. No single publication is a reliable way to follow it.

Concentration is not the same as volume

The 7 largest outlets still publishing, The Hacker News, Financial press wire, Dark Reading, The Register, The Record, Infosecurity Magazine, CyberScoop, produced 2405 of the 3495 stories, or 68.8% of everything. That sounds like a concentrated market, and by raw output it is. The topic table shows why that is misleading: the outlets that dominate the total are not the ones that own every subject.

The Hacker News: 791 stories (22.6%) Financial press wire: 358 stories (10.2%) Dark Reading: 337 stories (9.6%) The Register: 265 stories (7.6%) The Record: 264 stories (7.6%) Infosecurity Magazine: 248 stories (7.1%) CyberScoop: 142 stories (4.1%) 28 other outlets: 1090 stories (31.2%) 68.8% top 7 outlets
Share of all 3495 stories, by outlet. Outlets that have stopped publishing are counted under "other". Recomputed on every load, so the split moves as the archive grows.

The practical version: a reader following one masthead is not getting a smaller version of the whole picture. They are getting a picture with specific, predictable holes in it, and which holes depends entirely on which masthead.

What this means if you are trying to keep up

If you follow a single source, choose it for what you need to see rather than for general reputation. The Hacker News carries 17.4% of AI security; The Hacker News carries 39.9% of Vulnerability; Financial press wire carries 25.9% of data breach.

If you would rather not maintain a reading list, that is what the weekly briefing is for: every one of these 3495 stories is summarised in plain language, and each topic above has its own page, including AI security, Vulnerability, data breach, Patch Management.

Limitations, which are real

  • These are the outlets we ingest, not the whole press. Topic shares describe this corpus. A different feed list would produce different percentages.
  • Tagging is model-generated. Topics are assigned automatically when each story is summarised. It is consistent, which is what matters for comparing topics against each other, but it is not a human taxonomy and it will disagree with one at the margins.
  • Counts are of stories, not significance. A one-paragraph advisory and a three-thousand-word investigation count the same here.
  • Outlets join the corpus over time. A source we started reading recently carries only the stories published since it joined, so its share understates its actual output, and comparisons against long-standing sources favour the incumbents. Shares converge as the archive grows.
  • The window is still filling. Feeds deliver stories dated days earlier, so recent counts rise for a while after the fact. That is also why this page is computed rather than published: a figure written into a page was wrong within hours.
  • Outlets stop. A feed that goes dark keeps its stories in the archive. An outlet silent for more than 7 days and more than 3 times its own usual gap between stories is labelled with the date it was last seen wherever this page names it, and is not allowed to carry a headline claim, but its past stories still count in the totals.
  • The financial wire is one outlet here. It delivers each story under the original publisher's name; counting those as separate outlets inflated the outlet count and made cryptocurrency look more fragmented than the press actually is. Leak-site trackers are excluded altogether: a listing is not a story.
  • Cite it with the date you read it, shown above, since the numbers move as the archive grows.

Comments

No comments yet.

To comment, confirm your email once. We send a sign-in link; no password to remember.

Your name appears with your comment; your email never does. By continuing you accept our terms and privacy policy.