The real mistake was to connect such food critical equipment to the internet. I don't know who dared to do that, this has been part of the common knowledge for a while now.
You still can do it, but it better be a super low level private network: basically a super low VPN/crypto without using any off-the-self kludge, open source or not, probably directly implemented in some hardware driver in assembly for machine code/hardware control (if traffic was "big", it would have been FPGAs, probably). And you ** _MUST_ ** have a permanent and significantly sized and competent "security" team 24/24 7/7 ** you can trust ** for monitoring and looking for "pertinent" flaws.
Mechanically, the effort required is some exponential of the machine code (compilers are a [trust] problem, not a solution) size, complexity and code unstability (change over time).
No, trusted compilers of comfy computer languages do not exist by definition, eat the bullet.
Related to crypto: I wish we had some open source binary specifications implemented in various ISAs for some micro-architectures. You want machine code here, not even C or whatever (or at best only for those binary specifications).
And don't be a fool, ASIC trust will be a thing: some features will have to be disabled, or you better be ready to change some micro-architecture, yes, would be better to have several micro-architectures based on the same ISA (i.e. RISC-V for zero IP lock) ready at proper scale.
You still can do it, but it better be a super low level private network: basically a super low VPN/crypto without using any off-the-self kludge, open source or not, probably directly implemented in some hardware driver in assembly for machine code/hardware control (if traffic was "big", it would have been FPGAs, probably). And you ** _MUST_ ** have a permanent and significantly sized and competent "security" team 24/24 7/7 ** you can trust ** for monitoring and looking for "pertinent" flaws.
Mechanically, the effort required is some exponential of the machine code (compilers are a [trust] problem, not a solution) size, complexity and code unstability (change over time).
No, trusted compilers of comfy computer languages do not exist by definition, eat the bullet.
Related to crypto: I wish we had some open source binary specifications implemented in various ISAs for some micro-architectures. You want machine code here, not even C or whatever (or at best only for those binary specifications).
And don't be a fool, ASIC trust will be a thing: some features will have to be disabled, or you better be ready to change some micro-architecture, yes, would be better to have several micro-architectures based on the same ISA (i.e. RISC-V for zero IP lock) ready at proper scale.