Article reader Listen + reading controls
Article reader
Preparing the reader…
Reading settings
Semiconductor security is a coordination problem¶
The National Institute of Standards and Technology's (NIST) June 30 framework for analyzing collusion threats in the semiconductor supply chain provides a way to compare threats involving adversaries at different stages of the chain and to reason about security-cost tradeoffs.
Its deeper value is a reminder that supply-chain assurance cannot be reduced to evaluating one supplier at a time.
Semiconductors pass through design, intellectual-property, fabrication, packaging, test, distribution, integration, and maintenance ecosystems. Evidence is distributed. So is opportunity for manipulation.
Independent reviews can miss interaction risk¶
A component may pass its local controls while two stages together create a serious vulnerability. One party may alter a design; another may suppress a test signal. Neither action alone reveals the complete threat.
This resembles a broader problem in complex systems: risk emerges from interactions that no component owner sees. Leveson's systems-theoretic approach to safety argues that accidents can result from inadequate control of system interactions, not only failed parts.
Supply-chain security needs the same system view.
Evidence must cross boundaries¶
Organizations need artifacts that allow specialists and suppliers to share enough evidence without exposing all proprietary detail. Hardware bills of materials, provenance records, test results, change notices, anomaly reports, and chain-of-custody data can serve as boundary objects.
The challenge is semantic as well as technical. Does “verified” mean design review, physical inspection, functional test, or cryptographic attestation? Which version and facility does the evidence cover? Who can challenge it?
Without shared definitions, a complete-looking assurance package can consist of incompatible claims.
Prioritize by mission consequence¶
It is impossible to apply maximum scrutiny to every component. NIST's focus on severity metrics and tradeoffs is therefore practical. Programs should concentrate assurance where compromise could alter safety, confidentiality, command, or mission continuity.
A useful analysis should connect:
- critical functions and failure consequences;
- supplier stages with access or leverage;
- plausible single and colluding threat actors;
- preventive and detective controls;
- independent evidence;
- and recovery or substitution options.
The last item is often neglected. Assurance should include resilience: the ability to identify affected systems, replace a component, switch supply, or operate in a degraded mode.
Connect hardware to the AI strategy¶
Artificial intelligence (AI) capability depends on accelerators, networking, memory, firmware, compilers, and cloud infrastructure. A model-risk program that ignores the hardware and software supply chain protects only the visible layer.
Semiconductor assurance is not a separate technical specialty at the edge of AI strategy. It is part of the trust foundation for every advanced system that depends on it.
NIST's framework helps teams reason about combined threats. The organizational task is to create governance that can see across contracts and stages, preserve evidence, and make a mission-level decision before local assurances are assembled into false confidence.
Sources and research trail¶
- National Institute of Standards and Technology, “Analyzing Collusion Threats in the Semiconductor Supply Chain” (June 30, 2025).
- Leveson, Engineering a Safer World (2011).
- National Institute of Standards and Technology, Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations (2022).
- Carlile, “A Pragmatic View of Knowledge and Boundaries” (2002).