SIOS runs as three separate systems: our cloud, the customer's server, and the user's workstation. The security-critical code is written once, as a single shared Rust substrate, and linked into all three. Here is why that is a deliberate engineering decision, not a convenience.
Because a control you implement three times is a control you must trust three times. We write the audit ledger, signing, licence verification and hardware attestation once, as one shared Rust substrate, linked into all three tiers. The same code that mints a key in our cloud verifies it on the workstation. One trust surface, not three.
Originally published on mickai.co.uk. This is a cross-post; the canonical version, with the full body, footnotes and references, lives on the mickai.co.uk article page.
Top comments (0)