Skip to content
Whitepapers and reports

Four subjects. Tell us which one you need.

Each one answers a different decision: whether the assurance argument holds, whether the standards line up, what the integration costs, and what changes where the trust boundary cannot depend on a network.

The subjects

Pick the subject you are working on.

Paper 01

Entropy assurance

The case for measuring an entropy source while it runs rather than validating it once and assuming it holds, and what that measurement establishes.

Questions it answers
  • What a physical model buys you that output statistics cannot
  • Min-entropy estimation against a model, and the boundaries of the result
  • The runtime loop: physical process, measurement, entropy estimate, health state, audit output
  • Where continuous visibility into source health sits among the other inputs to a security posture
Paper 02

Standards and certification

How the standards fit together, what each certificate actually covers, and how to write entropy requirements into a specification without overstating what any of them prove.

Questions it answers
  • SP 800-90A, 90B and 90C, and how a validated source becomes a random bit generator
  • BSI AIS 20/31 and the Common Criteria evaluation route, and what each one asks of a source
  • FIPS 203, 204 and 205, finalised August 2024, and where entropy enters each scheme
  • Reading a certificate scope statement, including what E178 does not cover
Paper 03

Ecosystem and scale

The engineering and commercial path from a first evaluation card to entropy designed into your own platform, and what carries across each step.

Questions it answers
  • Choosing an integration point: PCIe, FMC or embedded module
  • Seeding and reseeding an approved deterministic mechanism from a local source
  • What qualification work carries across a product family, and what has to be repeated
  • What transfers when the integration point changes: software, evidence and method
Paper 04

High-assurance deployment

Entropy in environments where the trust boundary cannot depend on a network: space, defence, government and QKD systems, and the regulated infrastructure that follows them.

Questions it answers
  • Why randomness delivered over a network cannot be verified where it is used
  • Sovereignty, availability and audit as architectural properties, not policies
  • Qualification evidence for constrained and long-lifecycle environments
  • Mapping the properties of an entropy architecture onto NIST and BSI requirements
Read first

Shorter reading on the same ground.

The explainers cover what min-entropy measures and what it cannot tell you, the physics behind the silicon, and where entropy sits in a post-quantum architecture. The assurance section carries certificate scope and its boundaries, the mapping between SP 800-90A, 90B and 90C, BSI AIS 20/31 and the FIPS 203, 204 and 205 family, and how a device reports its own health while it runs.

Ask for the material you need.

Tell us which questions you need answered and who has to be convinced, and an engineer sends the material behind them.