Solutions · 04
Evidence your evaluators can verify line by line.
Fleet enrollment under annual agreements, with an evidence package your evaluators can verify line by line.
Take the asymmetric core, stated once
The conformance claim ships in one fixed wording, everywhere it appears:
Canonical wording — verbatim
CNSA 2.0 — asymmetric core conformant (ML-KEM-1024 + ML-DSA-87 at Category V; SHA-512 at or above the hash floor). Production AEAD today is ChaCha20-Poly1305 (RFC 8439), a documented deviation; the AES-256-GCM NSS suite is implemented and reserved as suite 0x0002, staged for rollout. Pre-evaluation checklist: 0 non-conformant findings, 3 documented deviations (NIAP ETR, 2026-05).
| Primitive | Standard | Role |
|---|---|---|
| ML-KEM-1024 | FIPS 203 | Key encapsulation, Category V |
| ML-DSA-87 | FIPS 204 | Identity signatures |
| X25519 | RFC 7748 | Classical hybrid component |
| ChaCha20-Poly1305 | RFC 8439 | Production AEAD (documented deviation) |
| AES-256-GCM | suite 0x0002 | NSS suite, implemented, staged for rollout |
| HKDF-SHA-512 | RFC 5869 | Key derivation |
The hybrid combiner concatenates the ML-KEM and X25519 shared secrets under HKDF-SHA-512, salted by the ciphertexts and bound to the public material — the NIST SP 800-227 §6.2 construction. Reading a recorded session requires breaking both components.
Read the evaluation posture without varnish
NIAP Common Criteria: READY WITH DEVIATIONS — not a completed EAL 4+ certification. The deviations are enumerated in the artifact bundle; formal evaluation is in progress. FIPS 140-3: Algorithm-conformant; implemented via a library lineage holding FIPS 140-3 cert #4631; QERYX's own module is not yet CMVP-certified.
The evidence package — Security Target, extended-components definitions, side-channel test evidence, SBOM, and audit history — is provided through the procurement channel and summarized in the Trust Center. We publish the caveats with the claims; an evidence package that hides its deviations is not evidence.
Deploy it on your own terms
The relay can be operated on your hardware, by your staff, inside your enclave — it holds ciphertext and opaque routing identifiers, so operating it grants no one the power to read. Fleet enrollment runs under annual agreements through the procurement lane; there is no public price card for government, by design.
The security floor your personnel get is the same floor every civilian gets. A session is as secure as its weakest end — so the floor is maximal for both ends, in every tier.
Ask for the field systems in the right room
Infrastructure-independent transports and field awareness surfaces — mesh radio, acoustic pairing, team coordination — exist as a separate line and stay out of the civilian messenger on purpose. They are briefed and scoped through procurement, not marketed on consumer pages.
05 / THE EVALUATOR’S QUESTIONS
Ask the four an evaluator opens with.
Where does QERYX stand on FIPS 140-3?
Algorithm-conformant; implemented via a library lineage holding FIPS 140-3 cert #4631; QERYX's own module is not yet CMVP-certified. Test vectors are pinned in the artifact bundle.
Is this an EAL 4+ certification?
No. The posture is READY WITH DEVIATIONS — the artifact bundle a testing laboratory would evaluate is complete, deviations are enumerated, and formal evaluation is in progress. We do not claim a certification we do not hold.
Why is the production AEAD ChaCha20-Poly1305?
It is the documented deviation in the canonical wording above: ChaCha20-Poly1305 (RFC 8439) performs consistently across heterogeneous devices without AES hardware. The AES-256-GCM NSS suite is implemented and reserved as suite 0x0002, staged for rollout.
Can we operate the backend ourselves?
Yes. The relay deploys from a compose file onto your hardware, and the carrier model means your operators hold no content keys — see the self-hosting docs and scope the rest through procurement.
Bring your evaluators.
The dossier answers in primitives, artifacts, and named deviations.