why this works is based on our understanding of advanced cyber security concepts.

Its easy to understand that Domain Systems makes un-hackable hardware, based on the laws of physics. we can present an impenetrable front, that also can release and publish information as if through a force field. that really cool, BUT...

Its important that the systems in the protected "Low Threat" environment don't have anything on them like an unfortunate wireless chip forgotten, tempest problems, or physical security concerns and insider threat issues.

Its also important that the public facing machine that helps facilitate the delivery pipeline to the World Wide Web, is hardened and checked for OPSEC leaks. because this "final delivery" part of the pipeline is in the "High Threat" exposure area, even if I harden it with the latest internet defense techniques, I have to assume that the hackers are really good and will compromise that machine. The public facing machine in the "High Threat Area" needs to be re-imaged before deployment to production and the OS disk written over with zeros and ones, and other things like that you could think of. That way, when the elite H4ck3r5 totally pwn that last accessible part of the pipeline, they are left with an empty blank faceless generic OS, and no attribution, down to the block level.

easy!

when you work with us, we will asses your OT and IT Infrastructure in its totality, and make sure that we are adding a vault door to the front, with without the back porch unlocked.

That would be silly!

{Well thats useless, what if i need to talk out back to the internet? - easy}