Disclosure · 99 filers

Operational Resilience

99 companies wrote this into a filing in the last 14 days, up from 66. Below: which of them, and what the corpus says they now owe.

Data measured , page built 22 September 2026 at 16:18 UTC.

99filers, current period
66the period before
50controls it touches
17frameworks
first appears Feb 2009 2008 2026 145 filings in the busiest month
Operational Resilience 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 99 wrote this into a filing with the SEC
What it obligates 50 controls across 17 frameworks whose text speaks to it
Employers hiring for it 4,368 open US roles name it, and the ones below are hiring now

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.

 
072145
2008 peak 145 in February 2026 2026

Who disclosed it

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

CompanyFormFiled
PROVIDENT FINANCIAL SERVICES INC PFS8-K2026-08-04filing
ESSENTIAL PROPERTIES REALTY TRUST, INC. EPRT8-K2026-09-16filing
Nuburu, Inc.8-K2026-07-21filing
Mobility Global Inc.8-K2026-07-02filing
Alcoa Corp AA8-K2026-09-09filing
AZZ INC AZZ8-K2026-07-08filing
Aurora Innovation, Inc.8-K2026-07-29filing
UNIVERSAL CORP /VA/ UVV8-K2026-08-05filing
Medline Inc. MDLN8-K2026-08-05filing
Mount Logan Capital Inc.8-K2026-08-11filing
Replimune Group, Inc. REPL10-Q2026-08-14filing
Civeo Corp CVEO8-K2026-07-30filing
MARA Holdings, Inc. MARA8-K2026-08-06filing
TREDEGAR CORP TG8-K2026-08-07filing

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
Manager, Change and Configuration Management
AST SpaceMobile, Inc. · Lanham, Maryland, United States
2026-09-21
Director, Resilience
COMMVAULT SYSTEMS INC · United States
2026-09-17
Senior Engineer, Directory Services
GoDaddy Inc. · United States
2026-09-17
Senior Solutions Engineer, Okta
Okta, Inc. · Chicago, Illinois
2026-09-17
Professional Services Consultant
Zscaler, Inc. · Bangalore, IND; Bangalore, IND
2026-09-16
Lead IAM Engineer
Braze, Inc. · Austin
2026-09-15
Lead IAM Engineer
Braze, Inc. · Toronto
2026-09-15
Lead IAM Engineer
Braze, Inc. · Chicago
2026-09-15
Solutions Architect (Germany or Austria)
COMMVAULT SYSTEMS INC · Frankfurt, Germany
2026-09-15
Infrastructure Engineer
Griffin-American Healthcare REIT IV, Inc. · London or remote within the UK
2026-09-15
Senior Compliance Risk Manager - Securities Compliance
MERCURY SYSTEMS INC · San Francisco, CA, New York, NY, Portland, OR, or Remote within United States
2026-09-15
Senior Solutions Engineer, Okta (Strategic Accounts - Minnesota)
Okta, Inc. · Minnesota
2026-09-15
Brokerage Risk Analyst Intern (Summer 2027)
Robinhood Markets, Inc. · Chicago, IL
2026-09-14
Principal Engineer, Duo Agent Platform
Gitlab Inc. · Remote, Canada; Remote, Poland; Remote, United Kingdom; Remote, United States
2026-09-11

Which industries file it

Companies grouped by the industry classification on their own filing. A count, not a survey.

IndustryCompanies
Banking77
Software and IT services69
Securities and investment38
Insurance26
Services and entertainment24
Chemicals and pharmaceuticals23
Mining and extraction16
Industrial machinery13
Holding and investment offices12
Business services9

What it obligates

Our corpus holds 50 controls across 17 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
HKMA SPM
Hong Kong
6
FFIEC IT Examination Handbook
United States
5
PCI PIN Security
International
5
PCI P2PE
International
5
PCI SSF
International
5
HKMA TM-G-1 verified
Hong Kong
4
DORA verified
European Union
3
HKMA Cyber Resilience Assessment Framework (C-RAF) verified
Hong Kong
3
Japan FSA Cybersecurity Guidelines for Financial Institutions verified
Japan
3
Lloyd's Minimum Standards verified
United Kingdom (Lloyd's)
3
IRM Enterprise Risk Management Framework (Institute of Risk Management) verified
International (IRM)
2
Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 verified
International
1
PSD2 SCA verified
European Union
1
APRA CPS 230 Operational Risk Management verified
Australia
1

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 22301 Evidence & Implementation Kit

49 controls sit behind ISO 22301:2019, 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 22301:2019 NIST SP 800-53 Rev 5273 shared controlsNIST Cybersecurity Framework 2.0191 shared controlsPCI DSS 4.0175 shared controlsISO 27002:2022148 shared controlsISO 27001:2022143 shared controlsSOC 2139 shared controlsCIS Controls v890 shared controlsNIST SP 800-53 Revision 5.1 HIGH83 shared controlsCloud Security Alliance Cloud Co…78 shared controlsNIST SP 800-161 Rev 166 shared controls
ISO 22301:2019 holds 49 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.
49If you already run ISO 22301:2019, that is the 49 controls behind this disclosure, already evidenced.
229And ISO 27002:2022 is not a separate programme. 229 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
224And ISO 27001:2022 is not a separate programme. 224 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
50And NIS2 Directive is not a separate programme. 50 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

278 controls

ISO 22301:2019 and ISO 27002:2022 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

229 already done

229 of ISO 27002:2022's controls are controls you evidenced for ISO 22301:2019. Same artefacts, same owner, no second effort. The mapping is the only reason anybody knows.

first appears Feb 2009 2008 2026 145 filings in the busiest month
Operational Resilience 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
99 public companies wrote this into an 8-K in the last seven days, 50% 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
4,368 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 22301:2019, DORA, EU Cyber Resilience Act. 83 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 22301:2019 has done 229 of the controls that carry ISO 27002:2022 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
16 companies disclosed this for the first time in the last ninety days, out of 380 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.

4 frameworks, 83 controls between them.

ISO 22301:2019 NIST SP 800-53 Rev 5273 shared controlsNIST Cybersecurity Framework 2.0191 shared controlsPCI DSS 4.0175 shared controlsISO 27002:2022148 shared controlsISO 27001:2022143 shared controlsSOC 2139 shared controlsCIS Controls v890 shared controlsNIST SP 800-53 Revision 5.1 HIGH83 shared controlsCloud Security Alliance Cloud Co…78 shared controlsNIST SP 800-161 Rev 166 shared controls
ISO 22301:2019 holds 49 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 27002:2022229
ISO 27001:2022224
NIS2 Directive50
ISO/IEC 42001:202345
ISO 9001:201539
ISO 27701:201935
ISO 22000:201832
ISO 37001:201628

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

Run as two programmes

278 controls

ISO 22301:2019 and ISO 27002:2022 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

229 already done

229 of ISO 27002:2022's controls are controls you evidenced for ISO 22301:2019. Same artefacts, same owner, no second effort. The mapping is the only reason anybody knows.

49If you already run ISO 22301:2019, that is the 49 controls behind this disclosure, already evidenced.
229And ISO 27002:2022 is not a separate programme. 229 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
224And ISO 27001:2022 is not a separate programme. 224 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
50And NIS2 Directive is not a separate programme. 50 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:
Operational Resilience filers →

Tell me when Operational Resilience 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 14 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. Operational Resilience corporate disclosure activity: 99 filers against 66 in the prior period, in 10-K and 10-Q filings, this quarter against the same quarter last year. Accessed 23 September 2026. https://signals.theartofservice.com/t/operational-resilience/

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