2020 in the archive: the year attention was reallocated, not expanded
The only year here that rises. What rose, and what quietly stopped being written about to make room for it.
Last reviewed September 3, 2026
- The rise is one subject. Remove it and the year falls below the one before it.
- Displacement, not addition. Everything else drops 61 entries in the month the new subject appears.
- It never came back. Non-pandemic writing ends the year at 139, still below January.
- The claim has a control. The same test finds 5 entries in 2019 and 163 in 2021.
The shape of the year, in two parts
Each column is a month, split into the pandemic and everything else. The totals barely move across the year. What moves is the composition, and the lower band is the one to follow.
Red: the pandemic and working from home. Dark: every other subject, running from 170 in January to 109 in Mar and 139 in December.
Did the pandemic add to the year, or replace part of it?
The arithmetic answers it in one line. 2020 holds 1,891 entries and the year before holds 1,687, a rise of 204. Entries concerning the pandemic or working from home number 289. Take them out and what remains is 1,602 — 85 below the previous year.
So the rise is not a rise. Strip one subject and the decline that has been running since the autumn of 2017 continues without a break, at very close to the rate it was already travelling at.
That is worth separating from a claim it resembles. This page is not saying the pandemic caused the field to write less about other things; a subtraction cannot establish a cause, and the previous piece in this series overreached in exactly that way and had to be corrected. What the arithmetic establishes is narrower and still useful: the exceptional year is not exceptional once one subject is removed, so any explanation of 2020 as a year of expanded activity has to survive that removal first.
The monthly figures are what turn a subtraction into something more interesting, and they are the next section.
Where does it turn?
Mar. Two things happen in the same month and they are the same size.
- Jan1700170
- Feb1493146
- Mar13324109
- Apr17560115
- May16854114
- Jun15323130
- Jul16224138
- Aug15617139
- Sep16012148
- Oct16023137
- Nov13518117
- Dec17031139
Month · total · pandemic · everything else
Pandemic entries go from 3 in Feb to 24 in Mar. Everything else goes from 146 to 109 across the same four weeks. One quantity gains 21 and the other loses 37.
The total for Mar is 133, which is the lowest month of the year. A reader looking only at annual or even monthly totals would record Mar as unremarkable and slightly quiet. Underneath, the largest single change in composition anywhere in this archive was taking place.
April is the mirror image: the total reaches 175, the highest of the year, while the non-pandemic band sits at 115 — still far below January. The month that looks busiest is a month in which most subjects were being covered less than usual.
What did the displacement cost?
Roughly 61 entries a month at the deepest point, and it did not recover. Non-pandemic writing begins the year at 170, bottoms out at 109 in Mar, and finishes December at 139.
What that means concretely is that every subject not connected to the emergency competed for a smaller share of a fixed quantity of attention. Vulnerability disclosure, authentication, insider risk, regulatory enforcement, hardware, the slow arguments about identity and access — all of it continued happening and less of it was recorded.
The mechanism is not mysterious. A publication has a fixed number of slots in a week and a finite number of people to fill them, and a subject that every reader is living through wins that competition without an editorial decision being required. Nobody chooses to cover authentication less. It simply loses.
There is a second-order effect worth naming. Displacement does not fall evenly: subjects with a natural news hook survive it, and slow structural ones do not. An enforcement action or a disclosed breach still arrives with a date attached and gets written up. An argument about privilege management, certificate lifetimes or the state of an organisation's asset inventory has no date, and it is the first thing to lose its slot when the week is full.
So a shock does not simply reduce coverage. It shifts the balance towards events and away from conditions, which over a long enough period makes the record read as though the field consisted mostly of incidents.
For anybody using a record like this one to reason about a period, that has a direct consequence. A subject appearing less often during a shock is evidence about the newsroom, not about the subject, and a comparison that spans 2020 will show declines in almost everything for reasons that have nothing to do with the things declining.
The remote-working surge lasted six weeks
Entries specifically about working from home number 87 across the year and peak in Apr at 25. By the second half of the year they have largely gone, while the arrangement they describe carried on for years afterwards.
That gap between the writing and the condition is the most transferable observation here. What generated the surge was the transition — the fortnight in which organisations had to decide about laptops, home routers, virtual private networks, split tunnels, family members sharing a machine, printed documents in kitchens, and whether a call could be recorded from a bedroom. Once those decisions were made, badly or well, there was nothing further to publish.
The exposure did not end when the writing did. A workforce operating from unmanaged networks on hurriedly issued equipment was a standing condition for several years, and it produced almost no coverage after the first quarter of it.
Anybody who inferred from the archive that remote working stopped being a security problem in the summer of 2020 would have been reading the publishing cycle rather than the risk.
Why did the displaced writing not come back?
It partly did, and the partial recovery is the interesting part. The non-pandemic band climbs back from 109 to around 139 by December, which is most of the way but not all of it: January's 170 is never reached again in this year.
One reading is that the pandemic simply kept a residual share — it never falls below double figures after March, and December is one of its larger months at 31. A subject that stays at a tenth of the output permanently reduces what is available for everything else.
The other reading is that this is the ordinary decline reasserting itself. The years either side of 2020 were falling, so a band that ends lower than it started is doing what the record was doing anyway, and the pandemic explains the shape of the dip rather than the level it recovers to.
This archive cannot separate those two, and it is worth saying so rather than choosing the more satisfying one. The measurement that would settle it — what would have been written in the absence of the shock — does not exist and cannot be constructed from anything here.
Ransomware went the other way
One subject grew against the displacement rather than with it. Ransomware appears 143 times in 2020 and rises through the year, from 9 in January to 25 in December.
As a share of entries carrying a written summary, so that the years are comparable:
- 4.3%2018
- 5.1%2019
- 8.8%2020
- 19.4%2021
The trough is 2018, the year after ransomware's famous one, when the subject had exhausted its novelty. From there it climbs steadily and does not stop. By the end of this archive it is the largest single subject of any year in it.
The addition is worth stating precisely, because it changed what a backup is worth. A victim with clean, tested, offline copies can decline to pay for decryption and restore instead — which is why backups were, for years, the whole of the advice. Once the stolen material is also published unless a second payment is made, restoring solves the outage and does nothing about the disclosure. The defence that had worked kept working against exactly half of the problem, and the half it no longer covered was the one that carried the regulatory consequence, the supervisory notification and the letters to customers.
What changed in this period was the model rather than the technique: attacks aimed at organisations that could not tolerate downtime, ransoms negotiated rather than demanded, and the addition of publication as a second threat when encryption alone stopped being sufficient. That is the shape this site describes in its guide to what ransomware costs and how it gets in, and 2020 is where the curve turns upward for good.
December arrives with two entries
The intrusion disclosed in the middle of December, in which a compromised software update from a network monitoring vendor reached tens of thousands of organisations including several governments, appears in this archive 2 times. Both are in Dec.
Nothing about that is a failure of judgement. The disclosure landed with a fortnight of the year remaining, the extent took months to establish, and an entry filed in December could not have said much beyond that something serious had happened.
It is the third December in this archive with the same property. A grid attack at the end of 2015 entered as a question a week after the event. A processor-level flaw broke in the opening days of 2018 and belongs to a year that had not yet started when it was found. Events do not distribute themselves conveniently across reporting periods, and the ones that arrive in the final fortnight are systematically under-recorded in the year that contains them.
The asymmetry is between when something happens and when it becomes describable. An intrusion of that kind is discovered, then scoped, then attributed, then argued about in hearings, and each stage produces writing months apart from the last. The archive records the final stage of one event beside the first stage of another and files them under whichever year they landed in.
The practical form of that is worth keeping. Any annual summary of anything is weakest about its own last month, and the December of a bad year is precisely where a reader should expect the record to be thinnest.
The tags stopped distinguishing
The eight most-used labels of 2020:
- 423Cyber Security
- 347Cyber Threats
- 263Cybersecurity
- 249Cyber Risks
- 237Cyber Attacks
- 185Malware
- 181Hackers
- 180Phishing
5 of the eight are variants of the same word, accounting for about 74% of the tags in that group. Two of them differ only by a space.
Five years earlier the leading labels were software, identity, mobile, network and hardware — categories that sort material into different piles. A label applied to a quarter of everything sorts nothing; it records that the entry is about the subject of the site, which was already known.
Classification decays this way when nobody is maintaining it and the volume keeps arriving. New labels get added faster than old ones get merged, near-duplicates accumulate, and the generic term wins because it is never wrong. The result still looks like an index and no longer functions as one.
It is also why the counts on these pages are drawn from titles and summaries rather than from tags. Text matching is generous and imprecise, and it has one decisive advantage over a decayed taxonomy: it is measuring what somebody wrote rather than which button they pressed afterwards.
The sector that could least afford it
One subject moved against the displacement. Entries touching hospitals, patients, medical devices or the vaccine effort number 68 across 2020 — a small share of the year, and one of the few that ends higher than it began:
- Jan3
- Feb5
- Mar6
- Apr4
- May4
- Jun6
- Jul3
- Aug5
- Sep6
- Oct5
- Nov9
- Dec12
From 3 in January to 12 in December. The proportions are modest and the direction is unambiguous, running opposite to almost everything else in the year.
The reason is that healthcare sat on both sides of the reallocation at once. It was where the emergency was happening and it was also a legitimate security subject, so it did not have to compete with the pandemic for space — it arrived attached to it. Nothing else in the archive had that property.
The December entries give the flavour without needing interpretation: ransomware described as falling hardest on hospitals, tens of millions of medical images sitting on servers with no protection in front of them, and warnings about the distribution effort that was about to begin. A ward that cannot admit patients because its scheduling system is encrypted is the point at which arguments about security in healthcare stop being conducted in the abstract.
The caution belongs with it. 68 entries is a doubling of a small number rather than a large movement, and a subject that quadruples from three to twelve has not become dominant. What makes it worth recording is the direction, in a year where the direction of nearly everything else was down.
What makes this claim checkable?
A subtraction on its own proves very little. Remove any sufficiently large subject from any year and the total falls; the question is whether the expression doing the removing is measuring the thing it claims to.
So the same test runs on the years either side. It matches 5 entries in 2019, out of 1,687, and 163 in 2021, out of 1,628.
That is the pattern it should produce if it works. Almost nothing before the event, a large presence during it, and a substantial residue afterwards — because the subject did not end in December. An expression that quietly matched general vocabulary would have returned a large number for 2019 too, and it returns 5.
This is published rather than done privately for a specific reason. The previous piece in this series named a cause for a decline on the strength of three data points, and measuring four more years removed the conclusion. A claim without its control is a hunch with figures attached, and the difference is not visible from the outside unless the control is printed.
How well recorded is this year?
Less well than the one before it, and the gap is large enough to qualify everything above. The share of entries carrying a written summary, by year:
- 201866%1,156 of 1,758
- 201977%1,300 of 1,687
- 202050%947 of 1,891
- 202152%850 of 1,628
77% in 2019 and 50% here. The year that gained entries lost description, so a good deal of 2020 exists in this archive as a headline and a date with nothing underneath.
That has a specific consequence for the counting on this page. Subject matching runs over titles and summaries, so a year with less summary text offers less surface to match against, and every subject figure for 2020 is a floor drawn from thinner material than the equivalent figure for 2019.
It cuts in a direction worth naming rather than glossing. If anything it makes the central finding conservative: the pandemic subject was found in 289 entries despite half the year having no summary to search, so the true share is more likely above 15.3% than below it. An undercounted displacement is still a displacement.
What it genuinely weakens is any fine-grained comparison of small subjects between 2020 and 2019. A category that appears to have halved may have done nothing of the sort and simply lost the text it was being found in — which is why the argument on this page rests on a large movement in a large subject rather than on a set of small ones moving together.
Who was writing it, and why that matters here
2020 draws on 233 distinct publications, with 640 entries naming one. The six most frequent:
- 112helpnetsecurity.com
- 62forbes.com
- 38securitymagazine.com
- 35securitybrief.eu
- 29cisomag.eccouncil.org
- 29itproportal.com
That count is ordinary for this archive. The years on either side sit at 228 and 232, and the surrounding period is stable enough that the source base can be treated as roughly constant across it.
Which is not a throwaway observation, because it is what makes the rest of this page credible. A finding about composition — that one subject displaced others — would be worth very little if the set of contributors had also changed, since a different mix of publications writes about different things for reasons that have nothing to do with events. The displacement would then be an artefact of who was supplying the record.
It is not. Broadly the same publications, in broadly the same proportions, wrote about markedly different things from March onwards. That is a change in what was being covered rather than in who was covering it, and it is the difference between an observation and a coincidence.
It is also the check that the previous piece in this series lacked. There, a source count was read as a cause without being tested against neighbouring years, and it did not survive the test. Here the same quantity is used the other way round — as a constant that licenses a comparison rather than as an explanation of it.
What 2020 settled
That the perimeter argument was over. An organisation whose entire workforce is operating from domestic networks on short notice cannot describe its security in terms of inside and outside, and the vocabulary that replaced it — verifying every request regardless of origin — became standard in this period rather than aspirational.
That availability is a security property and not an operations one. Hospitals and public bodies under ransomware during a health emergency made the case in a way that a decade of argument had not, and it is the reasoning behind this site's guide to availability and resilience.
And that a trusted software update is a route in. The December intrusion established what had been a theoretical concern about suppliers as a demonstrated method, which is the argument this site now makes about code arriving from somebody else's server — though, as this page has shown, it established it almost entirely in the following year's record rather than this one's.
And it settled something about the people doing the defending, which the archive records only obliquely. Security teams went home too. Incident response conducted from kitchens over conference calls, a colleague's screen no longer glanceable, the informal channel by which somebody mentions that a server is behaving oddly — all of it had to be rebuilt as procedure or lost. The writing covered the workforce being remote and had very little to say about the responders being remote.
What 2020 did not settle, for a reader of archives rather than of the field, is whether a year that looks busier was busier. This one looks like the exception in a decade of decline and stops looking like it after a single subtraction.
Common questions
How many entries does this archive hold for 2020?
1,891, against 1,687 the year before. That makes 2020 the only year here that rises rather than falls, and the rise is the subject of this page.
Did the pandemic increase how much was written about security?
No. It replaced part of it. 289 entries — 15.3% of the year — concern the pandemic or working from home. Remove them and 2020 holds 1,602, which is 85 fewer than the previous year rather than more.
How can that be checked?
By running the same test on the years either side. The same expression matches 5 entries in 2019 and 163 in 2021. Almost nothing beforehand and a substantial presence afterwards is the shape it should have if it is measuring what it claims to.
When does the year turn?
Mar. Entries about the pandemic go from 3 to 24, and everything else falls from 146 to 109 in the same month. The new subject and the drop in the old ones arrive together.
Did the displaced subjects come back?
Not within the year. Non-pandemic entries peak in Jan at 170 and never return to that level, ending the year at 139. The reallocation held for the remaining nine months.
How long did the remote-working surge last?
About six weeks. Entries about working from home peak in Apr at 25 and fall away quickly afterwards, even though the working arrangement itself lasted years. The writing tracked the transition rather than the condition.
What else grew in 2020?
Ransomware, and it grew against the trend rather than with it. It appears 143 times and rises through the year, ending at 25 in December. As a share of entries carrying a summary it runs 4.3% in 2018, 5.1% in 2019, 8.8% in 2020, 19.4% in 2021.
Is the December supply-chain intrusion in this archive?
Barely. It appears 2 times, in Dec. The event that reshaped how governments and large organisations think about software suppliers arrived too late in the year to be understood inside it, which is a recurring property of Decembers in this record.
Why do the tags all look the same?
Because by 2020 the classification had stopped distinguishing. 5 of the eight most-used labels are near-synonyms built on the same word, accounting for about 74% of the tags in that group. A taxonomy whose leading terms are variants of one another has lost the ability to sort.
Does a rise in entries mean a rise in attacks?
No, and this year is a demonstration of why not. The total rose while the underlying record continued to shrink, because one subject arrived that everybody had a reason to write about. Volume follows what is sayable at least as closely as it follows what is happening.
Was 2020 unusual in this archive?
In one respect only. It is the sole year that interrupts a decline running from September 2017 onwards, and the interruption disappears once a single subject is removed. In every other respect it continues what the years around it were already doing.
Can these figures be checked?
Yes. Every number is computed from the archive when the page is built, the test that supports the central claim is stated explicitly, and the control that validates the test is published alongside it rather than described.
2020 in the archive
The 1,891 entries behind this page run from January 2, 2020 to December 31, 2020, drawn from 233 publications.
Browse the archive by month, read the same treatment of 2018, 2017 or 2015, or search across every year.