Computing Library › Security & Safety-Critical Computing
Security & Safety-Critical Computing

Supply-Chain Attacks

Rather than attacking a target directly, adversaries compromise a trusted supplier whose product the target already installs and trusts.

Attacking Through Trust

A supply-chain attack reaches its victims indirectly, by compromising something they already trust and install: a software vendor, an open-source library, a hardware component, or an update mechanism. Because the malicious code arrives through a legitimate, trusted channel, it bypasses defenses that would stop an external intruder. One compromised supplier can deliver malware to thousands of downstream victims at once.

Forms of Attack

Kronos motion — supply chain

Why They Are Hard to Defend

The trust that makes a supplier useful is exactly what the attack abuses. Signed updates verify as authentic because the vendor really signed them, after being compromised. This is why defense focuses on provenance and verification: knowing precisely what you run (via an SBOM), verifying integrity, pinning versions, hardening build pipelines, and monitoring for the unexpected behavior a malicious component eventually exhibits.

Reducing Exposure

Least privilege limits what a compromised component can do; segmentation limits how far it can spread; monitoring catches its activity. No single control prevents supply-chain attacks, so the answer is depth plus the ability to respond fast when one is discovered.

Fusion Context

A fusion program's control, simulation, and analysis software all depend on third-party components, making supply-chain integrity a first-class concern. For the Hyperion breeder and burner tooling, the defenses are SBOMs, signed and verified artifacts, pinned dependencies, and hardened build pipelines, so that a compromised upstream package cannot silently reach systems that influence plant design or operation.