Industries / Technology / Software and SaaS / Cybersecurity
Responding to incidents
Containing an attack once it is found, getting systems running again, and telling the people and authorities who need to know.
7
Milestones achieved, from 1990 to 2025.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1990
Response teams form a network
After a worm in 1988 drew a response that was "isolated and uncoordinated", and another, the WANK worm, hit in October 1989, incident response teams found it hard to work together across languages, time zones and national rules. In 1990 they formed FIRST, the Forum of Incident Response and Security Teams, so that teams could reach one another during an attack. It had 5 members in its first year and 856 in 2026, by its own count.
Credit
the founding teams of FIRST
2004
A handbook for handling incidents
NIST, the US standards agency, published the Computer Security Incident Handling Guide (SP 800-61) in January 2004: how to set up a response team, staff it, detect and analyze incidents, and learn from each one afterwards. It was revised in 2008 and 2012. The third revision, in April 2025, recast it as a profile of NIST's Cybersecurity Framework 2.0, so that incident response is planned across all of an organization's risk management, not only after an attack.
Credit
Tim Grance (NIST), Karen Kent and Brian Kim (Booz Allen Hamilton), authors of the 2004 guide; NIST
2016
Free keys for ransomware victims
Ransomware locks a victim's files by encrypting them and demands payment for the key. In 2016 the Dutch police's National High Tech Crime Unit, Europol's European Cybercrime Centre, Kaspersky and McAfee set up No More Ransom, a website that gives away decryption tools for the families of ransomware whose locks researchers have found a way to undo. At five years, Europol said it offered 121 free tools covering 151 ransomware families, had 170 partners, and had helped more than six million people recover their files, keeping almost €1 billion from criminals by its estimate.
Credit
Politie (Netherlands), Europol, Kaspersky, McAfee
2017
A plan nobody had rehearsed
On 12 May 2017 the WannaCry ransomware hit more than 200,000 computers in at least 100 countries. In England it affected at least 80 of 236 hospital trusts and infected 595 GP practices, and NHS England estimated more than 19,000 appointments were cancelled. That evening a security researcher activated a "kill-switch" that stopped it locking devices. The UK National Audit Office found that every infected NHS body had unpatched or unsupported Windows, and that the Department of Health had a response plan but had not tested it locally, so it was "not immediately clear who should lead".
LessonA response plan that has never been rehearsed leaves people unsure who is in charge when an attack comes.
Credit
UK National Audit Office, report of October 2017
2023
Four business days to tell
On 26 July 2023 the US Securities and Exchange Commission required listed companies to disclose a cybersecurity incident on Form 8-K, under a new Item 1.05, within four business days of deciding it is material to investors. Disclosure may be delayed only if the US Attorney General finds it a substantial risk to national security or public safety. The rule applied from 18 December 2023. By November 2026 ransomware.live, an independent tracker, counted 990 cyber-incident 8-K filings, of which only 33 used Item 1.05; the rest used Item 8.01, for other events.
Credit
US Securities and Exchange Commission
2025
Review board dismissed mid-inquiry
The US Cyber Safety Review Board, created in 2022, investigated major incidents and published findings, among them a 2024 report on hacks of Microsoft's cloud email. In January 2025 the acting Secretary of Homeland Security, Benjamin Huffman, ended the memberships of all the department's advisory committees, including the board, while it was investigating Salt Typhoon's intrusions into nine US telecom companies. In May 2025 four US senators asked for it to be revived, saying the public was left without a full account.
LessonA review body that can be dismissed partway through leaves a major incident without a public account of what went wrong.
Credit
US Department of Homeland Security
2025
Most victims stop paying
Chainalysis, a blockchain-analysis firm, counted about $820 million in ransomware payments in 2025, against a revised $892 million in 2024, while the number of victims claimed on extortion sites rose by about 50%. It found that only 28% of victims paid in 2025, a record low, down from 62.8% in 2024 and 78.9% in 2022. Chainalysis credits better incident response, more scrutiny from regulators and law-enforcement disruption of the gangs.
Credit
Chainalysis, which measured it
Watch for
A ban on paying ransoms
The UK government said it would ban public bodies, including NHS trusts, councils and schools, and operators of critical national infrastructure from paying ransoms. Other businesses would have to tell the government before paying. Nearly three quarters of consultation respondents backed the ban. In February 2026 the law firm Goodwin reported that no bill carrying it had yet been introduced.
Achieved whenthe ban is in force in law and the government reports how covered bodies hit by ransomware recovered without paying.
Claimed by
UK Home Office, July 2025
Seventy-two hours to report
A 2022 US law, the Cyber Incident Reporting for Critical Infrastructure Act, requires CISA to write rules under which critical-infrastructure companies report serious cyber incidents within 72 hours and ransom payments within 24 hours. CISA says it "continues to work on the final rule" after funding lapses held up the work, and it held four town halls on it in June 2026.
Achieved whenthe final rule takes effect and CISA publishes how many reports it has received.
Claimed by
CISA, June 2026
Open
01
Downtime from company filings
A public table of every cyber incident a US-listed company has reported on Form 8-K since December 2023, with four dates for each: when the company found the attack, when it disclosed it, when it said operations were restored, and the cost it later reported. The later dates come from amended 8-Ks and quarterly and annual reports.
The briefCredit · unclaimed02
Which active gangs have keys
For the 50 ransomware groups that named the most victims on their leak sites in 2025 and 2026, a table showing whether a free decryption tool exists for their ransomware, where to get it, and when it was released compared with the group's last post.
The briefCredit · unclaimed
Open 01 · the brief
Downtime from company filings
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A public table of every cyber incident a US-listed company has reported on Form 8-K since December 2023, with four dates for each: when the company found the attack, when it disclosed it, when it said operations were restored, and the cost it later reported. The later dates come from amended 8-Ks and quarterly and annual reports.
Why it is still open
Trackers list the filings but not the recovery. Ransomware.live records 990 filings with the company, filing date, item and a severity score. A commercial listing from sec-api.io gives the filing date and a summary, and mentions recovery only in passing, such as one company's "~8-hour disruption". Neither has a field for the restoration date or the length of the outage. The law firm Debevoise & Plimpton measured the time from detection to disclosure in the rule's first 100 days, 5.45 business days on average, and found that more than half of the companies reported a disruption to operations, but it gave no durations.
Built with what exists
SEC EDGAR full-text search and its free data APIs; Python; a language model to pull candidate dates from each filing, with a person checking every date against the sentence it came from.
First step
Record the found, disclosed and restored dates for the 33 Item 1.05 filings.
Done looks like
All 33 Item 1.05 filings and at least 200 of the Item 8.01 filings traced, each date linked to the filing sentence it came from. A second person checks 30 rows chosen at random and agrees with at least 28. Updated each quarter.
Open 02 · the brief
Which active gangs have keys
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
For the 50 ransomware groups that named the most victims on their leak sites in 2025 and 2026, a table showing whether a free decryption tool exists for their ransomware, where to get it, and when it was released compared with the group's last post.
Why it is still open
No More Ransom counts the families it covers, 151 in 2021 by Europol's count, but a search in November 2026 found no published figure for how many currently active groups can be decrypted for free. The examples point to keys arriving late: Gen Digital released a FunkSec decryptor through No More Ransom in July 2025 "because the ransomware is now considered dead", four months after the group's last leak-site post.
Built with what exists
Ransomware.live, a free tracker that only reads what gangs post publicly and offers an API; No More Ransom's list of decryption tools; decryptor pages from security firms; Python. No ransomware samples are needed.
First step
Pull 2025 victim counts per group from ransomware.live and match the top 20 against No More Ransom's tool list.
Done looks like
50 groups, each with a yes or no, a link to the tool if one exists, the tool's release date and the group's last leak post. A second person checks 10 rows and agrees with all 10. Updated every six months.