Skip to content

The Randomness Processing Unit, entropy and cryptographic execution on one card

The Randomness Processing Unit is a card that generates entropy, verifies it at runtime, and executes cryptographic operations inside one boundary. Generate, verify, execute and deliver — one definition, held consistently, and all of it about cryptography.

The four functions

  • Generate. A quantum entropy source on the card, producing randomness where it is consumed rather than requesting it from elsewhere.
  • Verify. Runtime measurement of the physical quantities the entropy model depends on, so the entropy claim is current rather than inherited from an evaluation.
  • Execute. Cryptographic operations performed on the card, on key material that need not enter host memory.
  • Deliver. Results returned to the host across the card boundary — a local interface, not a network service.

Why one boundary rather than three components

Assembled separately, an entropy source, a verification mechanism and a cryptographic accelerator have interfaces between them. Entropy crosses one to reach the thing that consumes it. Health information crosses another to reach whatever interprets it.

Each crossing is a place to protect and a thing to justify to an evaluator. Inside one boundary they are internal, which is an argument that shows up in the programme cost as much as in the security analysis.

What verification adds that a certificate does not

A certificate says a source of this design met its requirements at evaluation. Runtime verification says this source, in this card, is within its modelled parameters now.

For a key generated this morning, only the second statement is about the key you actually hold — the observability distinction, in product form.

Where it fits

A server or appliance that generates keys, terminates sessions or signs at volume, and needs to be able to say something about the randomness underneath. That is a certificate authority, an HSM vendor building a platform, a telecom operator terminating subscriber sessions, or a data centre operator with an audit obligation.

The platform argument stated plainly is entropy and execution inside one boundary.