The Global Standards & Regulatory Alignment Matrix
This matrix lists the standards whose algorithms or formats Crypto Service Suite implements. "Implemented" means the algorithm is available in the code; it is not a certification. No module in the suite is FIPS 140-3 validated, and the post-quantum algorithms come from @noble/post-quantum, which is not independently audited.
| Standard / Regulation | Authority | Mandate & Scope | Implementation in Suite | Status |
|---|---|---|---|---|
| NIST FIPS 203 | NIST (United States) | Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM) | @sebastienrousseau/crypto-lib (512, 768, 1024) | Implemented (not validated) |
| NIST FIPS 204 | NIST (United States) | Module-Lattice-Based Digital Signature Algorithm (ML-DSA) | @sebastienrousseau/crypto-lib (ML-DSA-44, 65, 87) | Implemented (not validated) |
| NIST FIPS 205 | NIST (United States) | Stateless Hash-Based Digital Signature Algorithm (SLH-DSA) | @sebastienrousseau/crypto-lib (SHA-2 & SHAKE variants) | Implemented (not validated) |
| NIST SP 800-38D & RFC 8439 | NIST & IETF | Authenticated symmetric ciphers (AES-GCM; ChaCha20-Poly1305 in HPKE; XChaCha20-Poly1305 in crypto-lib, crypto-prisma and crypto-typeorm) | @sebastienrousseau/crypto-lib, crypto-prisma, crypto-typeorm | Implemented (not validated) |
| RFC 9180 | IETF | Hybrid Public Key Encryption (HPKE), base and PSK modes, checked against the RFC 9180 test vectors. The post-quantum suite is X-Wing (KEM 0x647A, draft-connolly-cfrg-xwing-kem), tested against the draft's vectors; the earlier x25519-ml-kem-768 suite is deprecated. | @sebastienrousseau/crypto-lib (X-Wing, X25519, P-256) | Implemented (not validated) |
| Composite ML-DSA (IETF draft) | IETF LAMPS | Hybrid signatures in which neither half verifies alone (draft-ietf-lamps-pq-composite-sigs, revision 19) | @sebastienrousseau/crypto-lib (ML-DSA-44 and ML-DSA-65 with Ed25519) | Implemented against a draft (not validated) |
| Hybrid KEM combiner (project ADR 0004) | Crypto Service | X25519 + ML-KEM-768 secrets combined once (v2), binding both ciphertexts and both public keys; used by the sealed box, multi-recipient envelope and post-quantum streams. RFC 10024's TLS group names are exported as reference constants only and are not implemented. | @sebastienrousseau/crypto-lib | Project-specific construction |
| EU DORA (Regulation 2022/2554) | European Commission (EBA/ESMA) | ICT risk management framework and related technical standards (including encryption and key management) | @sebastienrousseau/crypto-cbom & crypto-kms | Supporting tools only; no compliance claim |
| NSA CNSA 2.0 | National Security Agency | Commercial National Security Algorithm Suite requirements (2025–2030) | @sebastienrousseau/crypto-lib (ML-KEM-1024, ML-DSA-87 available) | Algorithms available; not validated |
| CycloneDX 1.6 & SPDX 3.0 | OWASP Foundation / Linux Foundation | Cryptographic Bill of Materials (CBOM) machine-readable spec | @sebastienrousseau/crypto-cbom CLI & API | Generator available (not run in CI) |
Deep Technical Invariants & Assurance Floors
All 18 packages enforce 100% statement, branch, function and line coverage in CI (c8 with mocha). Coverage shows what the tests execute, not that the code is correct.
@sebastienrousseau/crypto-lib has seven runtime dependencies: @noble/ciphers, @noble/curves, @noble/hashes, @noble/post-quantum, openpgp, @openpgp/web-stream-tools and eckey-utils (which OpenPGP.js needs for Brainpool curves). Lattice operations, NTTs and hash functions come from these libraries, or from the runtime's OpenSSL where Node.js 24.7 and later provides them; they are not implemented in crypto-lib.
The suite makes no constant-time guarantee and has not been evaluated against timing side channels. @noble/post-quantum does not guarantee constant-time execution, and not every secret comparison in crypto-lib is constant-time.
crypto-lib exports wipeMemory() and SecureBuffer for callers, but its own APIs do not call them. Keys are mostly handled as hex strings, which JavaScript cannot wipe, so key material can remain on the heap until garbage collection.
Plan Your Post-Quantum Migration
Talk to the maintainers about architecture reviews, cryptographic inventories for DORA work, and deploying hybrid post-quantum key exchange.