Disclosure · 15 filers

Supply Chain Due Diligence

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

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

15filers, current period
9the period before
13controls it touches
6frameworks
first appears May 2011 2008 2026 19 filings in the busiest month
Supply Chain Due Diligence 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 15 wrote this into a filing with the SEC
What it obligates 13 controls across 6 frameworks whose text speaks to it
Employers hiring for it 11 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.

 
01019
2008 peak 19 in February 2026 2026

Who disclosed it

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

CompanyFormFiled
UNIVERSAL CORP /VA/ UVV8-K2026-11-04filing
Mueller Water Products, Inc. MWA10-K2026-11-18filing
SOMNIGROUP INTERNATIONAL INC. SGI8-K2026-11-09filing
GREIF, INC10-K2026-11-18filing
lululemon athletica inc. LULU10-Q2026-09-03filing
Microvast Holdings, Inc. MVST10-Q2026-11-09filing
TYSON FOODS, INC. TSN10-K2026-11-16filing
Hewlett Packard Enterprise Co10-Q2026-09-03filing
PLEXUS CORP PLXS10-K2026-11-19filing
NETGEAR, INC. NTGR10-Q2026-11-04filing
QVC Group, Inc. QVCG10-Q2026-11-16filing
Fortinet, Inc. FTNT10-Q2026-10-30filing
iRhythm Holdings, Inc. IRTC10-Q2026-11-05filing
Post Holdings, Inc. POST10-K2026-11-19filing

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
Senior Supply Chain Compliance Lead
CoreWeave, Inc. · Sunnyvale, CA / Bellevue, WA
2026-11-13

Which industries file it

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

IndustryCompanies
Electronics and electrical equipment15
Industrial machinery9
Instruments and medical devices6
Transport equipment5
Food, beverage and tobacco4
Wholesale trade4
Chemicals and pharmaceuticals4
Wood, paper and printing3
Textiles and apparel3
Retail3

What it obligates

Our corpus holds 13 controls across 6 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
Responsible Minerals Initiative (RMI) verified
Global (industry programme; recognised under Regulation (EU) 2017/821 by Commission Implementing Decision C(2025) 6853 and by the London Metal Exchange)
5
ILO Declaration on Fundamental Principles and Rights at Work (Core Conventions) verified
International (ILO, 187 member states)
3
ICC Incoterms 2020 verified
International (ICC)
2
FFIEC IT Examination Handbook verified
United States (FRB, FDIC, NCUA, OCC and state banking supervisors)
1
ILO Nursing Personnel Convention C149 (1977) verified
International (ILO); binding on 41 ratifying Members
1
Germany Works Constitution Act (BetrVG) verified
Germany
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.

NIST SP 800-161 Cybersecurity Supply Chain Risk Management Evidence & Implementation Kit

191 controls sit behind NIST SP 800-161 Rev 1, 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.

NIST SP 800-161 Rev 1 Cloud Security Alliance Cloud Co…299 shared controlsC5 (Germany)217 shared controlsNIST SP 800-53 Rev 5215 shared controlsNIST Cybersecurity Framework 2.0165 shared controlsFedRAMP Moderate161 shared controlsAWS Well-Architected Security Pi…156 shared controlsISO 27001:2022132 shared controlsISO 27002:2022132 shared controlsCIS Controls v8127 shared controlsAzure Security Benchmark121 shared controls
NIST SP 800-161 Rev 1 holds 191 controls. They appear again inside 34 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.
191If you already run NIST SP 800-161 Rev 1, that is the 191 controls behind this disclosure, already evidenced.
135And ISO 27001:2022 is not a separate programme. 135 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
132And ISO 27002:2022 is not a separate programme. 132 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
119And ISO 27701:2019 is not a separate programme. 119 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

326 controls

NIST SP 800-161 Rev 1 and ISO 27001: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

135 already done

135 of ISO 27001:2022's controls are controls you evidenced for NIST SP 800-161 Rev 1. Same artefacts, same owner, no second effort. The mapping is the only reason anybody knows.

first appears May 2011 2008 2026 19 filings in the busiest month
Supply Chain Due Diligence 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
15 public companies wrote this into an 8-K in the last seven days, 67% 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
11 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 NIST SP 800-161 Rev 1, ISO 28001:2007 Supply Chain Security Management, NIST SP 800-161. 235 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 NIST SP 800-161 Rev 1 has done 135 of the controls that carry ISO 27001: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
3 companies disclosed this for the first time in the last ninety days, out of 66 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, 235 controls between them.

NIST SP 800-161 Rev 1 Cloud Security Alliance Cloud Co…299 shared controlsC5 (Germany)217 shared controlsNIST SP 800-53 Rev 5215 shared controlsNIST Cybersecurity Framework 2.0165 shared controlsFedRAMP Moderate161 shared controlsAWS Well-Architected Security Pi…156 shared controlsISO 27001:2022132 shared controlsISO 27002:2022132 shared controlsCIS Controls v8127 shared controlsAzure Security Benchmark121 shared controls
NIST SP 800-161 Rev 1 holds 191 controls. They appear again inside 34 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 27001:2022135
ISO 27002:2022132
ISO 27701:2019119
ISO 22301:201977
PCI DSS 4.018
ESRS (revised 2026)9

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

Run as two programmes

326 controls

NIST SP 800-161 Rev 1 and ISO 27001: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

135 already done

135 of ISO 27001:2022's controls are controls you evidenced for NIST SP 800-161 Rev 1. Same artefacts, same owner, no second effort. The mapping is the only reason anybody knows.

191If you already run NIST SP 800-161 Rev 1, that is the 191 controls behind this disclosure, already evidenced.
135And ISO 27001:2022 is not a separate programme. 135 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
132And ISO 27002:2022 is not a separate programme. 132 of its controls are the same controls. If it is on next year's plan, that part of it is already done.
119And ISO 27701:2019 is not a separate programme. 119 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:
Supply Chain Due Diligence filers →

Tell me when Supply Chain Due Diligence 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. Supply Chain Due Diligence corporate disclosure activity: 15 filers against 9 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/supply-chain-due-diligence/

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