RESOURCES
The signed image, attestation, the provenance record, and what a sealed stack means.
Articles in Integrity
- Integrity
Rolling back to the previous signed release
A Substrate update can be undone. The previous signed release stays on the node, and a site that needs to step back applies it, attests, and resumes, with the rollback recorded like any other software load.
· 4 min read
- Integrity
The provenance record for a node
Every Czar node carries a provenance record covering its integration, its sealing, and every software load since. It is the node's history, kept on the appliance, written for the person who has to answer for it.
· 4 min read
- Integrity
What Watchman watches
Watchman is the Substrate service that keeps verifying after attestation: the signed software image and the enclosure's tamper indicators, continuously, with every deviation written to an append-only record.
· 4 min read
- Integrity
Attestation before a node takes work
Before a Czar node joins a Grid or accepts a single request, it attests what it is running. Only a node that has proved it runs a signed release is placed on the list of nodes that may take work.
· 4 min read
- Integrity
What the signed image guarantees
Substrate runs from a sealed, signed, read-only software image. That one property is what lets a node prove what it is running, lets Watchman detect a change, and lets a site roll back with confidence.
· 4 min read