109filers, current period
102the period before
77controls it touches
49frameworks
SOC 2 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
109
wrote this into a filing with the SEC
What it obligates
77
controls across 49 frameworks whose text speaks to it
Employers hiring for it
4,506
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.
2008
peak 135 in February 2026
2026
Who disclosed it
From SEC full-text search over 8-K filings. Every row links to the filing itself.
| Company | Form | Filed | |
| Cyngn Inc. CYN | 8-K | 2026-11-12 | filing |
| Artificial Intelligence Technology Solutions Inc. AITX | 8-K | 2026-09-15 | filing |
| Grayscale Hyperliquid Staking ETF HYPG | 8-K | 2026-10-05 | filing |
| Grayscale Bittensor Trust (TAO) TAO | 8-K | 2026-10-05 | filing |
| TECOGEN INC. TGEN | 8-K | 2026-10-14 | filing |
| VIDA Global Inc. VIDA | 8-K | 2026-09-30 | filing |
| Boost Run Inc. BRUN | 8-K | 2026-11-12 | filing |
| BNB PLUS CORP. BNBX | 8-K | 2026-10-02 | 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 |
| Senior Sourcing Security Assurance Analyst Block, Inc. · Bay Area, CA, United States of America | 2026-11-20 |
| Senior Enterprise Security Engineer Roblox Corp · San Mateo, CA, United States | 2026-11-20 |
| Enterprise Automation Engineer Datadog, Inc. · New York, New York, USA | 2026-11-19 |
| Senior Software Engineer in Test Okta, Inc. · Toronto, ON, Canada | 2026-11-19 |
| Senior Software Development Engineer in Test - Okta Identity Governance Okta, Inc. · Toronto, ON, Canada | 2026-11-19 |
| Senior Software Engineer in Test Okta, Inc. · Toronto, ON, Canada | 2026-11-19 |
| Director, Data Center Security Operations CoreWeave, Inc. · Livingston, NJ / New York, NY / Sunnyvale, CA / Bellevue, WA | 2026-11-18 |
| Security Engineer Prelude Therapeutics Inc · Paris, France | 2026-11-18 |
| Senior Staff IAM Engineer SoFi Technologies, Inc. · WA - Seattle; CA - San Francisco; UT - Cottonwood Heights; NY - New York City; TX - Frisco | 2026-11-18 |
| Information Systems Auditor SolarWinds Corp · Manila, Philippines | 2026-11-18 |
| Senior Manager, Customer Engineering Cloudflare, Inc. · Hybrid | 2026-11-17 |
| Manager, Corporate Security - Platform Security Gitlab Inc. · Remote, United States | 2026-11-17 |
| Senior Software Development Engineer in Test - Okta Identity Governance Okta, Inc. · Toronto, ON, Canada | 2026-11-17 |
| Senior Security Auditor Roblox Corp · Gurugram, Haryana, India | 2026-11-17 |
Which industries file it
Companies grouped by the industry classification on their own filing. A count, not a
survey.
| Industry | | Companies |
|---|
| Software and IT services | | 141 |
| Banking | | 36 |
| Securities and investment | | 33 |
| Services and entertainment | | 30 |
| Holding and investment offices | | 27 |
| Instruments and medical devices | | 26 |
| Chemicals and pharmaceuticals | | 20 |
| Insurance | | 20 |
| Health services | | 16 |
| Industrial machinery | | 16 |
What it obligates
Our corpus holds 77 controls across
49 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.
- Role inventory + RACI
- Crosswalk document
- Control matrix mapping each in-scope criterion to controls
- Gap assessment against the 2022 revised points of focus
- System description prepared under the SOC 2 description criteria
- Statement of the trust services categories in scope
- Assessment register showing each provider's last assessment date, outcome and open findings
- Assessment method matrix showing which tiers need a SOC 2 report, PCI AoC, questionnaire or onsite review
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.
- Multi-framework alignment ad-hoc
- Roles undefined
- Sectoral coordination weak
- Missing due diligence
- Crosswalk not maintained
- Multi-framework alignment gaps
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.
778And ISO 27701:2019 is not a separate programme. 778 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
540And ISO 27002:2022 is not a separate programme. 540 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
364And ISO/IEC 42001:2023 is not a separate programme. 364 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
896 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
778 already done
778 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.
SOC 2 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
- 109 public companies wrote this into an 8-K in the last seven days, 7% 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,506 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, SOC 2. 332 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 778 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
- 7 companies disclosed this for the first time in the last ninety days, out of 468 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.
5 frameworks, 332 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:2019778
ISO 27002:2022540
ISO/IEC 42001:2023364
ISO 22301:2019316
PCI DSS 4.0198
COBIT 2019152
NIS2 Directive134
Counted as controls reached through cross-framework mappings. It measures
overlap of work, not compliance with the named framework.
Run as two programmes
896 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
778 already done
778 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.
778And ISO 27701:2019 is not a separate programme. 778 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
540And ISO 27002:2022 is not a separate programme. 540 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
364And ISO/IEC 42001:2023 is not a separate programme. 364 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 SOC 2 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. SOC 2 corporate disclosure activity: 109 filers against 102 in the prior period, in 10-K and 10-Q filings, this quarter against the same quarter last year. Accessed 22 November 2026. https://signals.theartofservice.com/t/soc-2/
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