This topic is kind of fascinating though. Considering the mindset from the Reflections on Trusting Trust paper, I do wonder how you bootstrap an assured supply chain like this. I know verification of chips and designs has been an active research area. But is there any formal solution to the larger problem of all the transitive dependencies of design and control of production?
How do you get there if you weren't already doing it from the start? It isn't just the chain of custody of the new chip that comes out. What about all the chips used in the production process and in the chain-of-custody tracking process? What about the chain of custody of all the design and process control artifacts that influenced the implementation of these processes? And the chips used to develop and manage those artifacts...
It feels like it most likely is a "turtles all the way down" kind of myth. Eventually, do you just give up and hope your layers of compliance frameworks have produced some kind of defense in depth cocoon?
I'm not sure it is even all that asymmetric. Do all the layers of compliance ritual disrupt the attacker more aggressively than it disrupts the desired production? There is a strong whiff of regulatory capture to these compliance frameworks, making it hard to divine how much it really blocks attackers versus upstart competitors...
Bootstrapping that from scratch today would be slow. The more feasible path is to use an existing assured supply chain to bootstrap initial capability and then swap out those bits with your own.
It's just not enough to make me care, I'd probably just rely on the packaging, and vendor procurement, but I guess this is an additional tool.
Edit: looks like they have (one?) partnership in place to help an OEM do that: https://news.lenovo.com/pressroom/press-releases/intel-colla...
4/3/26 Shipped to MSS facility Beijing
4/5/26 Received at MSS facility Beijing
4/5/26 Special firmware upgrade performed at MSS facility
4/7/26 Shipped from MSS facility Beijing to customer in United States via Fedex