Post-quantum encryption

Quantum-safe today, not “on the roadmap.”

Hybrid post-quantum cryptography — ML-DSA signatures and ML-KEM key exchange alongside classical primitives, encrypted on-device with zero service-held keys. Protection that defeats harvest-now, decrypt-later for the data finance, government, and defence must keep secret for decades.

Hybrid
ML-KEM + ML-DSA with classical primitives
On-device
Encryption before data reaches Glassbreak
0
Service-held decryption keys
Agile
Versioned, rotatable key model
Book a demoStart for free

The clock already started

“Post-quantum” on most vendors’ roadmaps is a slide, not a shipping primitive. But the threat is not in the future for data you keep for decades: adversaries are harvesting encrypted archives today to decrypt once a cryptographically-relevant quantum computer arrives. If your protection only becomes quantum-safe after that machine exists, the secrets captured in the meantime are already lost. For long-retention finance, government, and defence data, the migration has to be done — not planned.

How the cryptography works

Each card pairs the cryptographic risk with the concrete mechanism. The full model — key hierarchy, primitives, and the zero-knowledge guarantee — is documented on the security page.

Hybrid, not bet-the-farm

The risk

A pure post-quantum scheme is a single bet on young algorithms; a pure classical scheme is a known bet against a future quantum adversary. Neither is prudent for data you must protect for decades.

Glassbreak supplies

Glassbreak runs the standardised post-quantum primitives — ML-KEM for key encapsulation and ML-DSA for signatures — in hybrid with battle-tested classical algorithms. An attacker must break both to win. You inherit the quantum resistance without giving up the classical assurance.

Defeats harvest-now, decrypt-later

The risk

Adversaries are already capturing encrypted traffic and archives to decrypt once a cryptographically-relevant quantum computer exists. For long-retention secrets, the threat is today even though the decryption is years out.

Glassbreak supplies

Because the key-establishment is already hybrid post-quantum, ciphertext harvested today is not decryptable by a future quantum machine. The protection has to be in place before the adversary captures the data — and on Glassbreak it already is.

Encrypted on-device, zero service keys

The risk

Quantum-safe transport is hollow if the server can read the plaintext. The strongest algorithm does not help if the provider holds a decryption key.

Glassbreak supplies

Content is encrypted on the client before it ever reaches Glassbreak, and the service holds zero decryption keys. Even with full database access, a Glassbreak operator — or a future quantum adversary who compromised the provider — sees only ciphertext.

Crypto-agility built in

The risk

Post-quantum standards will keep evolving. An encryption design welded to one algorithm becomes a migration project the day the parameters change.

Glassbreak supplies

The key model is versioned and algorithm-aware, so primitives can be rotated and re-wrapped as standards mature — without re-architecting. Crypto-agility is a property of the design, not a future ticket.

Quantum-safe quorum access

The risk

The encryption only matters if access control is just as strong. A quantum-safe vault with a single phishable unlock is not quantum-safe in practice.

Glassbreak supplies

Long-retention secrets are protected by T-of-N multi-party approval with WebAuthn-gated approvers. The cryptography and the access policy are both hardened — there is no weak link to pull.

Evidence for the assessor

The risk

Finance, government, and defence buyers increasingly have to show a credible post-quantum migration posture, not just claim one.

Glassbreak supplies

The encryption model is documented publicly, and every key event is recorded in the immutable audit log — the artefacts an assessor or supervisory authority asks for when reviewing cryptographic controls.

Built for long-retention data

Where the decades-long confidentiality horizon makes quantum-safe-today a requirement, not a nice-to-have.

Financial services

Trading keys, settlement credentials, and customer records carry retention horizons measured in decades. Regulators expect a documented post-quantum migration posture; harvest-now, decrypt-later is a board-level risk, not a hypothetical.

Government & public sector

Classified-adjacent material, citizen data, and signing keys must stay confidential far beyond the arrival of quantum computing. National guidance is already pushing departments and suppliers toward quantum-safe primitives.

Defence & critical infrastructure

Long-lived operational secrets, certificate authorities, and command credentials are exactly the assets an adversary harvests today to read later. Quantum-safe protection has to be in place before capture, not after.

Strong algorithm, strong everything else

Quantum-safe cryptography is necessary but not sufficient. On Glassbreak it sits inside a zero-knowledge model, T-of-N quorum access, and an immutable audit trail — and the broader control alignment is mapped for ISO 27001 and SOC 2.

← Back to the Enterprise hubFor incident managers →ISO 27001 alignment →SOC 2 alignment →

Frequently asked questions

What post-quantum algorithms does Glassbreak use?

The standardised primitives: ML-KEM for key encapsulation and ML-DSA for digital signatures, run in hybrid alongside established classical algorithms. Hybrid means an attacker must break both the post-quantum and the classical scheme to compromise the data.

What is harvest-now, decrypt-later — and why does it matter today?

Adversaries capture encrypted data now and store it to decrypt once a cryptographically-relevant quantum computer exists. For data with a long retention horizon, the protection must be in place before the data is captured. Glassbreak’s key-establishment is already hybrid post-quantum, so ciphertext harvested today is not exposed by a future quantum machine.

Why hybrid instead of pure post-quantum?

Pure post-quantum stakes everything on relatively young algorithms; pure classical is knowingly vulnerable to a future quantum adversary. Hybrid combines both so that breaking the data requires breaking both schemes — you gain quantum resistance without surrendering decades of classical assurance.

Does post-quantum encryption mean Glassbreak can read my data?

No. Content is encrypted on your device before it reaches Glassbreak, and the service holds zero decryption keys. The algorithm strength is in addition to a zero-knowledge model — a Glassbreak operator with full database access sees only ciphertext.

What is crypto-agility and does Glassbreak have it?

Crypto-agility is the ability to rotate cryptographic primitives as standards evolve without re-architecting. Glassbreak’s key model is versioned and algorithm-aware, so primitives can be rotated and re-wrapped as post-quantum standards mature, with each change recorded in the audit log.

Make your long-retention data quantum-safe

Book a demo to review the hybrid post-quantum model and crypto-agility against your retention and assurance requirements, or start free and store a secret under hybrid encryption today.

Book a demoStart for free

ML-KEM and ML-DSA refer to the NIST-standardised post-quantum primitives. This page describes the platform’s cryptographic design for transparency and does not constitute a certification or legal advice.

Stay Updated

Get product updates and security insights. No spam, unsubscribe anytime.

We respect your privacy. See our privacy policy.