Skip to content

NIST SP 800-90B explained, what entropy source validation proves

SP 800-90B specifies how to validate an entropy source: a documented physical model, min-entropy estimated with a defined suite of estimators, and continuous health tests. An ESV certificate records that a specific source, in a specific configuration, met those requirements at evaluation.

What the standard requires

  • A documented model of the noise source — the physical process and why its output is unpredictable.
  • A min-entropy estimate produced with the standard's estimator suite, taking the minimum across those that apply.
  • Continuous health tests — repetition count and adaptive proportion at minimum — running on raw output in service.
  • Restart testing, to establish that the source does not produce correlated output across power cycles.

It is a good standard. It asks the right questions and it asks for a model rather than a number, which is more than most schemes require.

What an ESV certificate proves

That a named source, in a stated configuration, was evaluated against those requirements and met them. That is a real and useful statement, and it is narrower than "this source is certified random" — a claim no certificate makes.

Quside holds ESV certificate E178, covering our PCIe and FMC entropy source implementation. Stating the scope precisely is the point: a certificate covers what it covers, and a vendor who is vague about scope is telling you something.

What it does not establish

Three things, none of which is a criticism of the standard.

It describes evaluation-time behaviour on evaluated units, not your unit today. Its mandated health tests catch a stopped or stuck source, not a degraded one. And validation of an entropy source says nothing about the DRBG or the module around it — those are separate questions that 90C addresses.

Reading a certificate properly

Check the version, the laboratory, the configuration and the scope. Then ask the question the certificate cannot answer: what evidence is there that this source still matches its model now? Runtime health testing is where that answer has to come from.