06/09/2026
We're in Brussels for TechNet International, and this morning Sheldon Lo-A-Njoe took the stage to address a pressing question for modern mission owners: how do you trust the software you're running when you can't reach a network to verify it?
For years, that verification depended on connectivity, and you'd confirm an artifact is what it claims to be in real time against a central source of truth. But this approach doesn't work in DDIL and air-gapped environments, and that's exactly where the stakes are highest.
At TechNet, Sheldon walked through how we close that gap: build the verification into the software itself. This means tamper-evident proof of origin, build, and approval travels with the artifact, so forces can confirm that what they're deploying is authentic, unmodified, and authorized, with or without a network to check against.
In short: trust travels with the software, not through the network.
That's also what makes it work across a coalition. When the proof lives in the artifact, every partner can verify the same software independently, which is what audit-ready compliance and interoperability actually require in contested conditions.
Sheldon goes deeper on all of this in an article he wrote with Nicolas Ferrao at Airbus Defence and Space, including the five most common ways supply chains get compromised and the cryptographic proof that shuts each one down.
Worth a read if you couldn't catch him on stage 👉 https://okt.to/iw3SCm