18filers, current period
17the period before
133controls it touches
64frameworks
Ransomware in 10-K and 10-Q filings, by month.
The marked line is the first month any public company in our record used the phrase; everything left of it is nobody writing it down.
Companies disclosing it
18
wrote this into a filing with the SEC
What it obligates
133
controls across 64 frameworks whose text speaks to it
Employers hiring for it
843
open US roles name it, and the ones below are hiring now
The long view, in 8-K filings
An 8-K is filed within four business days of an event, so this counts filings made because something happened.
Every month since 2008. The last point is the current month and is still
filling, so it always looks lower than it will be.
2008
peak 98 in February 2023
2026
The long view, in annual and quarterly filings
A 10-K or 10-Q is a periodic report, so this counts how often the phrase appears in routine annual and quarterly reporting. It moves far more slowly and the numbers are larger.
Every month since 2008. The last point is the current month and is still
filling, so it always looks lower than it will be.
2008
peak 1,277 in February 2026
2026
In annual and quarterly filings the same phrase appears 938 times this quarter, against 892. A 10-K moves slowly: a company changing what it writes there has changed its mind about what is material, rather than reacting to one event.
Who disclosed it
From SEC full-text search over 8-K filings. Every row links to the filing itself.
| Company | Form | Filed | |
| ROYAL GOLD INC RGLD | 8-K | 2026-11-18 | filing |
| Ameris Bancorp ABCB | 8-K | 2026-11-16 | filing |
| ROSS STORES, INC. ROST | 8-K | 2026-11-19 | filing |
| SYPRIS SOLUTIONS INC SYPR | 8-K | 2026-11-17 | filing |
| FB Financial Corp FBK | 8-K | 2026-11-16 | filing |
| VisionWave Holdings, Inc. | 8-K | 2026-11-20 | filing |
| WORLD OMNI AUTO RECEIVABLES LLC | 8-K | 2026-11-18 | filing |
| World Omni Auto Receivables Trust 2026-D | 8-K | 2026-11-18 | filing |
| Integer Holdings Corp ITGR | 8-K | 2026-11-17 | filing |
| RAPID MICRO BIOSYSTEMS, INC. RPID | 8-K | 2026-11-16 | filing |
| AYTU BIOPHARMA, INC AYTU | 8-K | 2026-11-16 | filing |
| 3D SYSTEMS CORP DDD | 8-K | 2026-11-13 | filing |
The full search on EDGAR
Who is hiring for it
A sample of the open roles naming this phrase. An employer paying a salary
against something is the least ambiguous demand signal there is, and every row links to the
posting so the claim can be checked rather than believed. The total above is the whole US
market; these are the ones we hold the posting for.
| Role | Posted |
| Account Executive, Portworx, FSI (EMEA) Pure Storage, Inc. · Paris, France; Staines, United Kingdom | 2026-11-18 |
| GSI Specialty Seller, Identity Resilience (Global) Rubrik, Inc. · Remote - United States | 2026-11-18 |
| Account Executive, Sales Specialist Unstructured Data - UK Rubrik, Inc. · London | 2026-11-16 |
| Sr Technician, Site Services Abacus Life, Inc. · Boston, Massachusetts, United States | 2026-11-13 |
| Sales Specialist Unstructured Data Rubrik, Inc. · Australia/Singapore | 2026-11-12 |
| Sales Specialist - Unstructured Data Rubrik, Inc. · Paris, France | 2026-11-12 |
| Software Engineer - UI Test Rubrik, Inc. · Bangalore, India | 2026-11-12 |
| Advisory Solutions Architect, MSP (New Product Intro) Rubrik, Inc. · Remote - United States | 2026-11-12 |
| Event Marketing Manager - EMEA Rubrik, Inc. · Amsterdam, Netherlands | 2026-11-11 |
| Sr. Analyst, Enterprise Service Desk Abacus Life, Inc. · Newark, New Jersey, United States | 2026-11-10 |
| Principal Security Architect, Identity Resilience AvePoint, Inc. · Chicago, IL, United States | 2026-11-06 |
| Senior Security Research Engineer Elastic N.V. · United States | 2026-11-02 |
| Software Engineer - Trust & Platform Security Snowflake Inc. · US-WA-Bellevue | 2026-10-30 |
| Client Executive, SLED Cloudflare, Inc. · Hybrid | 2026-10-29 |
How it actually arrives
An 8-K's meaning is in its item number, not its text. These are the items the filings
containing this phrase were filed under. The first group is something that happened to the
company. The second is the phrase turning up in the ordinary course of reporting, most often in
an earnings release, which is a very different thing and is usually the larger number.
| Filed because something happened |
Companies |
| Other material event Item 8.01 | 570 |
| Director or officer departure Item 5.02 | 236 |
| Change of accountant Item 4.01 | 25 |
| Delisting or listing rule failure Item 3.01 | 23 |
| Bankruptcy or receivership Item 1.03 | 15 |
| Material cybersecurity incident Item 1.05 | 6 |
| Material impairment Item 2.06 | 4 |
| Financial statements no longer reliable Item 4.02 | 2 |
| Mentioned in routine reporting |
Companies |
| Financial statements and exhibits Item 9.01 | 1384 |
| Entry into a material agreement Item 1.01 | 1151 |
| Regulation FD disclosure Item 7.01 | 741 |
| Results of operations, the earnings release Item 2.02 | 225 |
| Completion of an acquisition Item 2.01 | 173 |
| Shareholder vote Item 5.07 | 42 |
This is why a headline count on its own overstates the case.
Where the routine number dominates, the phrase is being tracked as language rather than as
events.
Which industries file it
Companies grouped by the industry classification on their own filing. A count, not a
survey.
| Industry | | Companies |
|---|
| Holding and investment offices | | 168 |
| Software and IT services | | 151 |
| Chemicals and pharmaceuticals | | 144 |
| Banking | | 102 |
| Electronics and electrical equipment | | 76 |
| Instruments and medical devices | | 73 |
| Industrial machinery | | 65 |
| Mining and extraction | | 58 |
| Services and entertainment | | 57 |
| Pipelines and communications | | 52 |
What it obligates
Our corpus holds 133 controls across
64 frameworks whose text speaks to this. Not a judgement:
these controls say so, and each is one lookup from its source document. Ordered by how much each
framework has to say about it, so the one that will cost you the most work is first. Every name
opens that framework in the corpus.
What an auditor will ask you to produce
The artefacts named on those controls, most frequently cited first.
- Pipeline + emerging risk readiness
- Backup policy
- Offline backup arrangements
- Multi-framework alignment + crosswalk
- Control matrix mapping each in-scope criterion to controls
- Gap assessment against the 2022 revised points of focus
- Backup policy defining scope, frequency and retention
- Backup job monitoring and failure remediation records
How it usually fails
Recorded when each control was verified against its source. This is where programmes
that think they are covered turn out not to be.
- Pipeline not tracked
- International alignment weak
- Adoption monitoring weak
- Incomplete CMDB
- Multi-framework alignment ad-hoc
- Control set still based on pre-2022 points of focus
ISO 27001:2022 Evidence & Implementation Kit
118 controls sit behind ISO 27001:2022, and this is the documentation set for them: an adopt-ready artifact per control, and the evidence an auditor asks for against each.
See what is in it, $249
The same set every buyer of this kit receives. Nothing here is produced on request.
ISO 27001:2022 holds 123 controls. They appear again inside
122 other frameworks in our corpus; the 10 strongest are shown. Thickness and
size both carry the number of controls shared, so work done once counts in every framework on
this diagram.
118If you already run ISO 27001:2022, that is the 118 controls behind this disclosure, already evidenced.
691And ISO 27701:2019 is not a separate programme. 691 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
464And ISO 27002:2022 is not a separate programme. 464 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
359And ISO 22301:2019 is not a separate programme. 359 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
Run as two programmes
809 controls
ISO 27001:2022 and ISO 27701:2019 scoped separately, each with its own
evidence, its own owner and its own budget line. This is how almost everybody does it.
Run once, counted twice
691 already done
691 of ISO 27701:2019's controls are controls you evidenced for
ISO 27001:2022. Same artefacts, same owner, no second effort. The mapping is the
only reason anybody knows.
Ransomware in 10-K and 10-Q filings, by month.
The marked line is the first month any public company in our record used the phrase; everything left of it is nobody writing it down.
What this actually means
- Why now
- 18 public companies wrote this into an 8-K in the last seven days, 6% more than the seven before. That is not sentiment or a survey. It is a count of companies choosing to put a phrase into a document they are legally accountable for.
- Who already cares
- 843 open US roles name this work today, which suggests increased attention to it beyond what any filing says. A job advertisement clears a budget holder and a filing clears legal, so the two answer to different people. We have not measured which moves first, only that both are moving.
- What comes into scope
- Once the phrase is on the record it maps to obligations within ISO 27001:2022, ISO 27001:2013, NIST Cybersecurity Framework 1.1. 651 controls behind those, and the difference between asserting them and evidencing them is the whole of the work.
- Who is quietly ahead
- Anyone already running ISO 27001:2022 has done 691 of the controls that carry ISO 27701:2019 too. Same evidence, second standard. Most organisations run those as two programmes with two budgets because nobody told them the mapping existed.
- Who is exposed
- 91 companies disclosed this for the first time in the last ninety days, out of 4067 in total. A first mention is a company deciding it can no longer not say it. Whoever has not yet is either genuinely unaffected or has not looked, and nothing here distinguishes the two.
What this obligates
The instruments in our corpus that govern this disclosure, and how many controls sit
behind each. This is not a filing count. It is what applies once a company has written the
phrase down.
7 frameworks, 651 controls between them.
ISO 27001:2022 holds 123 controls. They appear again inside
122 other frameworks in our corpus; the 10 strongest are shown. Thickness and
size both carry the number of controls shared, so work done once counts in every framework on
this diagram.
What closing it also moves
The same controls appear in other frameworks through mappings held in our corpus. Work
done here is already progress there. This is the part that is not in EDGAR and not in any public
dataset: it comes from mappings built and verified by hand, control by control.
ISO 27701:2019691
ISO 27002:2022464
ISO 22301:2019359
ISO/IEC 42001:2023343
NIS2 Directive201
PCI DSS 4.0165
COBIT 2019152
Counted as controls reached through cross-framework mappings. It measures
overlap of work, not compliance with the named framework.
Run as two programmes
809 controls
ISO 27001:2022 and ISO 27701:2019 scoped separately, each with its own
evidence, its own owner and its own budget line. This is how almost everybody does it.
Run once, counted twice
691 already done
691 of ISO 27701:2019's controls are controls you evidenced for
ISO 27001:2022. Same artefacts, same owner, no second effort. The mapping is the
only reason anybody knows.
118If you already run ISO 27001:2022, that is the 118 controls behind this disclosure, already evidenced.
691And ISO 27701:2019 is not a separate programme. 691 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
464And ISO 27002:2022 is not a separate programme. 464 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
359And ISO 22301:2019 is not a separate programme. 359 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
Tell me when Ransomware files something new
One email when a public company newly discloses this, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
Where this comes from
The left half is public record: SEC full-text search over 8-K filings, counted across a
7 day window against the equivalent window before it. You can check
every row.
The right half is ours: 723 frameworks and
20,473 controls, 531 of those frameworks verified against
their source documents, with the auditor evidence and common failure modes recorded control by
control. Controls appear here because their own text names this term.
Cite this
The Art of Service Signals. Ransomware corporate disclosure activity: 18 filers against 17 in the prior period, in 8-K filings over seven days against the seven before. Accessed 22 November 2026. https://signals.theartofservice.com/t/ransomware/
Free to use with attribution, no permission needed. The chart downloads as an SVG
with the source printed on it. If you cite it we would like to know, but you do not need to
ask.
Today's edition ·
How programmes fail ·
The obligation index