NIST PQC / CNSA 2.0 mapped

Encryption built for the quantum era.

Quanten Security delivers post-quantum cryptography as a drop-in fabric — from TLS handshakes to sovereign key storage.

256-bit
Classical security level
< 4 ms
PQC handshake latency
3 paths
Deployment patterns
PQC Handshake · Session 0x8F3A
KEM ML-KEM-1024 KAT CHECKED
Sig ML-DSA-87 + Ed25519 KAT CHECKED
Shared 7f 3a c2 ··· 9e 4b 1d SEALED
Entropy QRNG · vacuum-shot 98.4%
Standards and evidence signals
Standards mapping NIST PQC / CNSA 2.0 mapped Migration scope TLS, PKI, firmware signing Key custody FIPS 140-3-ready HSM paths Evidence review Readiness artefacts on request

Three pillars. One crypto-agile fabric.

Platform overview
01

Post-Quantum Key Exchange

ML-KEM-1024 replaces ECDH across every session — TLS, SSH, and proprietary tunnels.

  • FIPS 203 aligned
  • Hybrid ECDH + ML-KEM mode
  • < 4 ms latency overhead
  • Drop-in HSM support
02

Lattice-Based Signatures

ML-DSA and SLH-DSA sign every packet and firmware image with quantum-safe math.

  • FIPS 204 / 205 aligned
  • Dual-signature bridge mode
  • Hardware-rooted trust chain
  • Zero-trust policy engine
03

Crypto-Agility Engine

Algorithm profiles hot-swap without downtime. Quantum or classical — the fabric adapts.

  • Algorithm negotiation API
  • CNSA 2.0 policy templates
  • Live migration support
  • Audit trail + SIEM export

NIST-standardised. Deployment-mapped.

Full algorithm matrix
A.01
ML-KEM-1024CRYSTALS-Kyber · FIPS 203
LatticeACTIVE
A.02
ML-DSA-87CRYSTALS-Dilithium · FIPS 204
LatticeACTIVE
A.03
SLH-DSA-SHA2-256sSPHINCS+ · FIPS 205
HashACTIVE
A.04
FN-DSA (Falcon)FIPS 206 in development
LatticePENDING
A.05
HQC-256NIST-selected backup KEM
CodePENDING
A.06
Classic McElieceResearch-only code-based KEM
CodePENDING
Q-Day planning horizon 1,288 days

Migration planners commonly model cryptographically relevant quantum risk across a 2029–2033 window.

Post-quantum encryption
ML-KEM-1024 FIPS 203 key encapsulation
Hybrid TLS 1.3 ECDH + ML-KEM migration mode
AES-256 Symmetric data encryption remains safe
ML-DSA / SLH-DSA Post-quantum identity signatures
RSA-2048 BROKEN
ECC-P256 BROKEN
AES-256 SAFE
ML-KEM SAFE
Quantum Physics

Why lattice math survives quantum attack.

Shor's algorithm solves the discrete-logarithm and integer-factorisation problems in polynomial time on a quantum computer. Every algorithm that relies on these problems — RSA, ECC, DH — falls.

Lattice problems such as Learning With Errors (LWE) have no known quantum speedup. ML-KEM and ML-DSA are built on LWE hardness, giving post-quantum security without sacrificing performance.

Security model
IND-CCA2
Lattice problem
Module-LWE
Classical bits
256
PQ bits
232

Three paths. Zero forklift upgrades.

Deployment guide

On-Premises HSM

Air-gapped key generation and storage. FIPS 140-3-ready HSM workflow with tamper evidence.

qs-keygen --algo ml-kem-1024 --hsm

Sovereign Cloud

Single-tenant deployment in your jurisdiction. National data-residency requirements met.

qs deploy --mode sovereign --region eu-west

Zero-Trust Overlay

Drop the PQC fabric over existing infrastructure. mTLS + ML-KEM without forklift upgrades.

qs overlay --target 10.0.0.0/8 --pqc hybrid

Common questions. Direct answers.

Full documentation
Q.01

When does our current PKI become quantum-vulnerable?

Migration planners commonly model cryptographically relevant quantum risk across a 2029–2033 window. RSA-2048 and ECC-P256 would be broken retroactively once a capable quantum computer exists — any encrypted traffic captured today can be decrypted then.

Q.02

What is “harvest now, decrypt later”?

Nation-state adversaries are recording encrypted sessions now. Once a quantum computer arrives, stored ciphertext becomes plaintext. PQC migration cannot wait until Q-Day arrives.

Q.03

Does PQC add latency?

ML-KEM-1024 handshakes add less than 4 ms over baseline TLS 1.3 on commodity hardware. Key-share payloads are larger (1,568-byte encapsulation key plus 1,568-byte ciphertext, vs 32 bytes for ECDH), but modern networks absorb the roughly 3.1 KB PQC exchange.

Q.04

Is hybrid PQC + classical mode available?

Yes. Quanten's fabric runs dual-algorithm sessions — classical ECDH alongside ML-KEM — so you remain protected against both classical and quantum attackers during the migration window.

Latest from the blog

All posts
Quantum computing chamber facing encrypted infrastructure and a post-quantum migration horizon. 01

The 2029 quantum-security wake-up call

3 min read

Google and Cloudflare have pulled their post-quantum migration targets toward 2029. The lesson for enterprises is not panic; it is that authentication, signing, and crypto inventory need executive attention now.

Read post
SECURE CONTACT CHANNEL

Begin your quantum-safe migration.

Share your environment, timeline, and regulatory context. The team will route your request to the right specialist without collecting unnecessary telemetry.

Do not include classified material, credentials, private keys, or regulated secrets in this form.