Data at Rest vs Data in Transit: Quantum Threats

Quantum threats affect data differently depending on whether it is at rest or in transit — and the defences differ. Understanding both is essential to a complete quantum-safe posture.

Data at Rest

Data at rest is stored data: files on disk, databases, backups, archives, cloud storage.

The Quantum Threat

• If encrypted with AES-256, data at rest is quantum-resistant. Grover's algorithm halves its strength to ~128 bits, still secure.
• If encrypted with AES-128, quantum reduces it to ~64 bits — not safe for long-term storage.
• If encrypted with RSA or ECC (some legacy systems wrap keys this way), it is vulnerable once a quantum computer can break the key-wrapping layer.
• If stored unencrypted, it is at risk from any compromise — quantum or not.

The Defence

• Standardise on AES-256 for all data at rest.
• Use strong key derivation (PBKDF2, Argon2) for password-based encryption.
• Protect the key-encryption layer with quantum-resistant methods.
• For your most sensitive files, encrypt them independently with a zero-knowledge tool like CryptShield before storage, so even a compromised storage provider cannot read them.
• Rotate keys and re-encrypt long-term archives as standards evolve.

Data in Transit

Data in transit is data moving over networks: web traffic, API calls, VPNs, email, messaging.

The Quantum Threat

• Most transit security uses TLS with ECDH key exchange — vulnerable to harvest-now-decrypt-later.
• VPNs using Diffie-Hellman or ECDH are similarly vulnerable.
• Encrypted email (PGP, S/MIME) using RSA or ECC is vulnerable.
• Messaging apps using ECDH (Signal protocol) are vulnerable in their key agreement.

The threat is acute because transit data can be intercepted and stored by adversaries at network backbones — exactly the harvest-now-decrypt-later scenario.

The Defence

• Deploy hybrid post-quantum TLS (ECDH + ML-KEM) so recorded handshakes cannot be decrypted.
• Upgrade VPNs to hybrid post-quantum key exchange.
• Use forward secrecy so each session uses fresh keys.
• For the most sensitive transit, encrypt the file independently before sending — the transport layer's future compromise then does not expose the content.
• Migrate email and messaging to post-quantum or hybrid key agreement over time.

The Key Difference

• At rest: the threat is mostly about the algorithm (use AES-256, not AES-128 or RSA-wrapped keys). The data is not being intercepted continuously.
• In transit: the threat is about key exchange (use hybrid post-quantum KEM). The data is being intercepted and stored by adversaries right now.

Both need attention, but transit is more urgent because of harvest-now-decrypt-later — the interception is happening today.

The Combined Strategy

A complete quantum-safe posture protects both:

1. In transit: hybrid post-quantum TLS + forward secrecy.
2. At rest: AES-256 with strong key derivation.
3. End-to-end: for the most sensitive data, encrypt independently with a zero-knowledge tool so protection does not depend on the transport or storage layer at all.

This third layer — independent file encryption — is the belt-and-suspenders approach. Even if your TLS is later broken and your cloud provider is compromised, the file itself remains protected by a quantum-resistant symmetric cipher and a key only you hold.

Bottom Line

Data at rest and data in transit face different quantum threats and need different defences: AES-256 for storage, hybrid post-quantum key exchange for transit. And for your most valuable data, independent encryption with a tool like CryptShield protects it regardless of what happens to the networks and servers in between.