Continuous assurance

The Assurance Plane

A deployed quantum-safe system can be correct on install day and quietly wrong six months later. The assurance plane is the independent, continuous evidence layer that proves a fielded system still meets its security contract, and shows its work every time it is asked. Run the proof, break it on purpose, and run a live adversarial pass.

conformanceintegrity livenessgraded

The idea

Three planes, and the one most programs forget

A sovereign crypto system has three planes. The first two are familiar. The third is where trust is actually earned, and it is usually an afterthought.

Data plane

Move it, sealed

The protected channel that carries payloads under post-quantum cryptography.

Control plane

Decide who, and what

The authority layer that governs which parties and actions are permitted.

Assurance plane

Prove it, continuously

The independent evidence layer that keeps proving the other two are doing what they claim.

The demonstration below is that third plane, made touchable. It is the honest answer to the question every security reviewer eventually asks: how do you know it is still secure in production, today, not just on the day it shipped.

Run it

The assurance gate board

Seven automatic gates. Run the pass and each one evaluates and lights. Then inject a fault and watch the relevant gate fail loudly and fail closed. A gate that can never say no is broken, so every gate here is built to be able to refuse.

Idle. The board has not been run. Press Run assurance pass to evaluate all seven gates.

Live integrity check

Live computed

This panel computes a real SHA-256 digest of the text below in your browser using your browser crypto. Edit a single character, or use a fault toggle, and the digest changes completely and the integrity gate refuses. ML-KEM-1024 and ML-DSA-87 are the production primitives; this hash is an honest analog of the integrity property, labeled as such.

Sealed digest(not sealed yet)
Live digestcomputing...
Artifact not sealed. Run the assurance pass to capture a reference digest.

Fault injection · break it on purpose

01

Standards conformance

The declared suite is checked against the pinned policy, parsed live from the artifact, not inferred from a version string.

NOT RUNFactLive
Press Run assurance pass.
02

Correctness evidence

The cryptographic round trip is byte-identical end to end, and an independent second implementation agrees. Two engines, the same answer, or it does not ship.

NOT RUNInferenceSample
Press Run assurance pass.
03

Integrity and tamper detection

Verification returns a plain verdict, and a tampered artifact is refused rather than quietly accepted. This gate is computed live from the digest above.

NOT RUNFactLive
Press Run assurance pass.
04

Timing-behavior discipline

Constant-time testing is part of the standing gate battery, so a regression in secret-dependent timing is caught by machine rather than discovered by an adversary.

NOT RUNInferenceSample
Press Run assurance pass.
05

Liveness and substance

An independent monitor proves on a schedule that services are not merely up but doing real work. Not port-open-but-hollow, not secure-but-leaking.

NOT RUNInferenceSample
Press Run assurance pass.
06

Fail-closed regression gates

The profile is checked live against an explicit deny list and the active policy. A retired or unlisted profile is refused; the default state is denied, not allowed.

NOT RUNFactLive
Press Run assurance pass.
07

Graded provenance

Every result carries a grade: FACT, INFERENCE, or UNVERIFIED. A pass is a claim until it is recomputed from source. Nothing is trusted because a label says so.

NOT RUNInferenceSample
Press Run assurance pass.

See it against your stack

We will stand the assurance plane up over your actual deployment.