Analysis
The model file on disk has a hash and a signature. Both pass. The model in memory may still not be the one you signed.
That is the finding I'd keep from an NVIDIA blog post dated October 29. NVIDIA and Eclypsium say they demonstrated that compromised infrastructure could alter a model's behaviour in memory while the stored file, hash and signature checks still passed. The post summarises the research in a sentence and links to it, so the detail isn't there. Read it as a vendor's claim, not an independent result.
The surrounding pitch combines BlueField DPUs with Eclypsium's assurance software. BlueField supplies hardware-rooted controls: authenticated boot, isolation, protected key management, rollback protection and device attestation. Eclypsium compares hardware and firmware against known-good baselines and watches for drift below the operating system.
One physical detail matters more than the product list. The post notes that DPUs, GPUs and management controllers can reach system memory directly. That makes IOMMU and PCIe access controls part of a model's integrity story, not just a networking footnote.
A signature proves what was loaded from disk. It says little about what is executing after firmware, a management controller or a peripheral with memory access has been tampered with. NVIDIA itself acknowledges that no single control establishes trust, and that boot-time measurements don't reflect current behaviour.
The post gives no performance figures, availability, pricing or independent evaluation.
So the test is one you can run on your own setup. Ask what evidence shows the host was in a known-good state while the model was serving. Then ask who checks that evidence after each firmware update, and whether anyone has actually done it on your target hardware.
Source: Building Trusted AI Infrastructure for Safe and Secure AI · 2026-10-29
Why it matters
Verifying a model file is not the same as verifying the machine running it, so ask your hosting provider or IT lead what covers the second part.
