Disclosure · 9 filers

Data Breach

9 companies wrote this into a filing in the last 7 days, small numbers either way. Below: which of them, and what the corpus says they now owe.

Data measured , page built 21 November 2026 at 16:39 UTC.

9filers, current period
9the period before
264controls it touches
143frameworks
first appears May 2008 2008 2026 71 filings in the busiest month
Data Breach 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 9 wrote this into a filing with the SEC
What it obligates 264 controls across 143 frameworks whose text speaks to it
Employers hiring for it 796 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.

 
03671
2008 peak 71 in November 2025 2026

Who disclosed it

From SEC full-text search over 8-K filings. Every row links to the filing itself.

CompanyFormFiled
HYDROFARM HOLDINGS GROUP, INC. HYFM8-K2026-11-16filing
GridAI Technologies Corp. GRDX8-K2026-11-17filing
All In FutureTech Alliance, Inc. AIFA8-K2026-11-19filing
RAPID MICRO BIOSYSTEMS, INC. RPID8-K2026-11-16filing
American Drive Acquisition Co8-K2026-11-18filing
WEN Acquisition Corp8-K2026-11-16filing
INTUIT INC. INTU8-K2026-11-19filing
Berto Acquisition Corp.8-K2026-11-18filing
Lulu's Fashion Lounge Holdings, Inc. LVLU8-K2026-11-17filing

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.

RolePosted
Chief Information & Security Officer
Nextdoor Holdings, Inc. · Dallas, TX
2026-11-05
Senior Technical Support Engineer - Shifted Work Week
Ping Identity Holding Corp. · USA - Remote
2026-10-30
Senior Technical Support Engineer
Ping Identity Holding Corp. · USA - Remote - California
2026-10-29
Compliance Advisory Manager
Griffin-American Healthcare REIT IV, Inc. · London or remote within the UK
2026-10-27
Senior Technical Support Engineer II
Ping Identity Holding Corp. · Sydney, New South Wales, Australia
2026-10-16
Data Privacy and AI Associate
Barnes & Noble Education, Inc. · Morristown
2026-10-12
Data Privacy and AI Associate
Barnes & Noble Education, Inc. · Raleigh
2026-10-12
Data Privacy and AI Associate
Barnes & Noble Education, Inc. · Chicago
2026-10-12
Data Privacy and AI Associate
Barnes & Noble Education, Inc. · Dallas
2026-10-12
Data Privacy and AI Associate
Barnes & Noble Education, Inc. · Atlanta
2026-10-12
Data Privacy and AI Associate
Barnes & Noble Education, Inc. · Nashville
2026-10-12
Data Privacy and AI Associate
Barnes & Noble Education, Inc. · Washington, D.C.
2026-10-12
Data Privacy and AI Associate
Barnes & Noble Education, Inc. · Indianapolis
2026-10-05
Sr Princ Product Manager - Digital Footprint Control
Gen Digital Inc. · USA - Mountain View, CA
2026-09-03

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
710
Director or officer departure
Item 5.02
384
Change of accountant
Item 4.01
35
Delisting or listing rule failure
Item 3.01
32
Bankruptcy or receivership
Item 1.03
18
Material impairment
Item 2.06
4
Financial statements no longer reliable
Item 4.02
2
Material cybersecurity incident
Item 1.05
1
Mentioned in routine reporting Companies
Financial statements and exhibits
Item 9.01
1852
Entry into a material agreement
Item 1.01
1702
Regulation FD disclosure
Item 7.01
1005
Completion of an acquisition
Item 2.01
313
Results of operations, the earnings release
Item 2.02
178
Shareholder vote
Item 5.07
40

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.

IndustryCompanies
Holding and investment offices273
Chemicals and pharmaceuticals267
Software and IT services216
Banking120
Instruments and medical devices102
Services and entertainment88
Electronics and electrical equipment84
Industrial machinery71
Retail64
Insurance56

What it obligates

Our corpus holds 264 controls across 143 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.

FrameworkControls
Malaysia PDPA 2010 verified
Malaysia
6
NIST SP 800-61 Rev. 3 verified
United States (NIST, FISMA authority); voluntary for non-federal organizations
6
Notifiable Data Breaches Scheme (Australia) verified
Australia
6
Japan FSA Cybersecurity Guidelines for Financial Institutions verified
Japan
6
Lloyd's Minimum Standards verified
United Kingdom (Lloyd's market)
6
Rwanda DPL verified
Rwanda
5
Nigeria Data Protection Act 2023 (NDPA) verified
Nigeria
5
PDPA Singapore verified
Singapore
4
India DPDP Act verified
India
4
Nigeria Data Protection Regulation (NDPR) verified
Nigeria
4
OAIC Privacy Management Framework verified
Australia
4
UK Privacy and Electronic Communications Regulations 2003 (PECR) verified
United Kingdom
4
Privacy and Other Legislation Amendment Act 2024 (Australia) verified
Australia (Commonwealth)
4
Australian Energy Sector Cyber Security Framework (AESCSF) verified
Australia
4

What an auditor will ask you to produce

The artefacts named on those controls, most frequently cited first.

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.

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 NIST SP 800-53 Rev 5682 shared controlsFedRAMP Moderate651 shared controlsPCI DSS 4.0649 shared controlsCIS Controls v8435 shared controlsSOC 2369 shared controlsNIST Cybersecurity Framework 2.0350 shared controlsISO 27701:2019346 shared controlsCloud Security Alliance Cloud Co…266 shared controlsCMMC 2.0263 shared controlsC5 (Germany)195 shared controls
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.
494And ISO 27701:2019 is not a separate programme. 494 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
339And ISO 27002:2022 is not a separate programme. 339 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
248And ISO 22301:2019 is not a separate programme. 248 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

612 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

494 already done

494 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.

first appears May 2008 2008 2026 71 filings in the busiest month
Data Breach 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
9 public companies wrote this into an 8-K in the last seven days, 0% fewer 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
796 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 SP 800-61 Rev. 3. 485 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 494 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
93 companies disclosed this for the first time in the last ninety days, out of 1879 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.

8 frameworks, 485 controls between them.

ISO 27001:2022 NIST SP 800-53 Rev 5682 shared controlsFedRAMP Moderate651 shared controlsPCI DSS 4.0649 shared controlsCIS Controls v8435 shared controlsSOC 2369 shared controlsNIST Cybersecurity Framework 2.0350 shared controlsISO 27701:2019346 shared controlsCloud Security Alliance Cloud Co…266 shared controlsCMMC 2.0263 shared controlsC5 (Germany)195 shared controls
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:2019494
ISO 27002:2022339
ISO 22301:2019248
ISO/IEC 42001:2023170
COBIT 2019152
PCI DSS 4.0151
NIS2 Directive86

Counted as controls reached through cross-framework mappings. It measures overlap of work, not compliance with the named framework.

Run as two programmes

612 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

494 already done

494 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.
494And ISO 27701:2019 is not a separate programme. 494 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
339And ISO 27002:2022 is not a separate programme. 339 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
248And ISO 22301:2019 is not a separate programme. 248 of its controls are the same controls. If it is on next year's plan, that part of it is already done.

If that number surprised you, the same measurement across every topic we track:
What changed this week →

This is what it looks like when the same failure is named by standards bodies who never spoke to each other:
How compliance programmes fail →

And the companies that have already written this into a filing:
Data Breach filers →

Tell me when Data Breach 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. Data Breach corporate disclosure activity: 9 filers against 9 in the prior period, in 8-K filings over seven days against the seven before. Accessed 22 November 2026. https://signals.theartofservice.com/t/data-breach/

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