What the device measures while it runs.
A certificate describes a source at the moment it was evaluated. Runtime observability is the part that keeps speaking afterwards: measurement of the physical process against its model, and a health state saying whether the device remains inside its validated operating conditions.
Model first, then measurement.
A model of the physical process is written down before anything is measured, so the measurement has something specific to be compared against. Grading the output stream instead would tell you nothing: output from a well-seeded deterministic generator looks equally random.
- Step 01Physical process
A quantum-optical process with a known physical model generates the raw signal.
- Step 02Measurement
On-device metrology samples the parameters that describe how that process is behaving.
- Step 03Entropy estimate
Entropy is quantified within the defined physical model, rather than inferred from output statistics alone.
- Step 04Health state
The device reports whether it remains inside its validated operating conditions.
- Step 05Audit output
That health record reaches the host system, where operations and compliance can inspect it.
What is worth measuring.
Runtime measurement is not one number. It is a small set of quantities chosen because the physical model is written in terms of them, plus the health tests the standard requires of any validated entropy source.
The physical process
On-device metrology samples the parameters that describe how the quantum-optical process is behaving, because those parameters are what the physical model is written in terms of.
The entropy estimate
Entropy is quantified within the defined physical model rather than inferred from the output stream, so the figure means something specific about the source.
The health tests the standard requires
SP 800-90B requires an entropy source to run continuous health tests — a repetition count test and an adaptive proportion test — while it produces output. A source validated under SP 800-90B carries those tests by construction.
The operating envelope
The device reports whether it remains inside the operating conditions its model was validated against. Leaving that envelope is the signal that matters.
What a health state actually says.
It is a statement about the source, not a grade applied to the bits. The device is reporting whether the physical process still behaves the way the model it was validated against says it should.
Inside the envelope
The measured behaviour of the physical process is consistent with the model the source was validated against.
Nothing to do. The value of the signal is that it is being produced continuously rather than assumed.
Outside the envelope
One or more measured parameters have moved outside the validated operating conditions. The device says so rather than continuing silently.
The host decides what that means for its own policy — stop consuming, reseed from an alternative source, raise an operational alert, or record it and continue under a documented exception.
Health test failure
A continuous health test required by SP 800-90B has failed. The standard defines this condition; it is not a Quside-specific signal.
Treated as a source failure by the standard’s own rules. The consuming system should not treat output produced after such a failure as if nothing had happened.
These readings give you continuous visibility into entropy-source health — one input to your security posture, alongside key management, protocol design and implementation quality. They are the input that has had no signal at all until now.
Where the evidence goes.
The record is produced at the device and made available to the host system. What happens next is your architecture.
For the integrator
The health state is a device-level signal on the host interface, so it can be read by the same software that reads the entropy. The integration question is what your platform should do with it, and that is a policy decision rather than a hardware one.
Discuss an OEM integration →For operations
The record is produced by the device and available to the host, so it can be carried into whatever logging and monitoring you already run. It stays on your side: Quside does not receive telemetry from deployed devices.
Talk to an engineer →For compliance and audit
An auditor asking "how do you know the source is still behaving?" has something specific to look at: a per-device record produced during operation, against a documented model, alongside the certificate that established the model in the first place.
Request an architecture review →What we send on request.
Each is controlled per product and per revision, so we send the version that matches your build rather than a generic one.
Telemetry interface reference
Registers, driver calls and polling behaviour for the health and telemetry interface, per product. Tell us your target platform and we will send the applicable version.
Request it for your platform →Validated operating ranges
Operating conditions are stated per product and per revision in the datasheet and qualification package. Name the product and revision in your design.
Request the operating ranges →Logging and compliance integration
An engineer will work through your host operating system, driver model and logging stack, and show where the health record fits in it.
Book a working session →Tell us what your platform needs to see.
Host operating system, driver model, logging stack and the compliance regime you report into are usually enough for us to describe how the health record fits.
More in Assurance
- LOVELocally Verified EntropyEntropy generated inside your trust boundary and measured against a physical model while it runs.
- LevelsRNG assurance levelsFour levels for comparing what a random number generator can actually evidence.
- CertificatesCertificates and their scopeNIST SP 800-90B entropy certificate E178 and ENS Alta, with the scope of each.
- StandardsThe standards landscapeSP 800-90A, 90B and 90C, the post-quantum FIPS standards, and the European schemes.
- QualificationQualification evidenceSpace qualification evidence for Ruby™ N1 in GEO conditions, and the environmental and lifecycle record behind it.