Skip to content
Assurance

Entropy you can inspect while it runs.

Every key, nonce, seed and token depends on unpredictability, and it has to come from a physical process somewhere. Quside measures that process against a defined model while the device runs, and reports what it finds. That is Locally Verified Entropy.

The gap

Validated once, then assumed.

An entropy source is tested before it ships and the result is treated as permanent for the life of the device. Hardware sources move with temperature, voltage and age, and a source can be worked on directly by an attacker. A certificate issued at procurement reports none of that.

How entropy is usually evidenced

Validated once, then assumed

  • An entropy source is evaluated at a point in time, before deployment.
  • The certificate travels with the product for the life of the device.
  • Temperature, voltage and ageing move the source; nothing reports it.
  • The first sign of a problem is usually downstream, in a key.
What Quside adds

Measured while it runs

  • The physical process has a written model, so there is something specific to measure against.
  • On-device metrology tracks the parameters that describe its behaviour.
  • The device reports whether it remains inside its validated operating conditions.
  • That record reaches the host, so operations and compliance can inspect it.

What that gives you is continuous visibility into entropy-source health, alongside key management, protocol design and implementation quality. Approved deterministic mechanisms remain sound constructions; what they depend on is strong seeding, correct construction and appropriate reseeding from trusted entropy sources — and that is the layer Quside sits at.

The loop

Five stages, in this order.

Locally Verified Entropy describes a loop that runs while the device is powered. The order matters: the model is written first, and the measurement is taken against it.

  1. Step 01
    Physical process

    A quantum-optical process with a known physical model generates the raw signal.

  2. Step 02
    Measurement

    On-device metrology samples the parameters that describe how that process is behaving.

  3. Step 03
    Entropy estimate

    Entropy is quantified within the defined physical model, rather than inferred from output statistics alone.

  4. Step 04
    Health state

    The device reports whether it remains inside its validated operating conditions.

  5. Step 05
    Audit output

    That health record reaches the host system, where operations and compliance can inspect it.

Due diligence

Worth asking any entropy supplier.

Ask them of us too. These are the answers.

Q01

Where is the entropy generated?

Inside the device and inside your trust boundary, on the same board as the cryptography that consumes it. Randomness arriving over a network cannot be verified where it is used, which is why Quside does not sell entropy as a service.

Locally, Verified, Entropy →
Q02

How is its quality verified?

Against a defined physical and statistical model of the source, while the device runs — not by grading the output stream, which cannot distinguish a healthy physical source from a deterministic generator having a good day.

What the device measures →
Q03

Who can observe that verification?

The health record is available to the host system, so the operator and the auditor are looking at the same evidence rather than at a certificate issued once at procurement.

The assurance levels →
Q04

What has an independent party actually established?

NIST SP 800-90B entropy certificate E178, scoped to Quside PCIe One and FMC One, and ENS Alta — the highest of the three categories of the Spanish scheme — for the same two products. Each is set out with the scope you can quote in a submission.

Certificates and scope →

Bring us the requirement you have to satisfy.

Send the certification scheme, the evaluation deadline, the target platform and the environment. An engineer will come back with the evidence that covers it and what would still have to be produced.