TOOL 003 / QUANTUM READINESS · BETA
LuniQ Risk
Will the data you encrypt today still be secret when a quantum computer can break RSA and elliptic-curve encryption?
Attackers can record encrypted traffic now and decrypt it later (“harvest now, decrypt later”). This calculator applies Mosca’s rule: secret-lifetime + migration-time > time-to-Q-day ⇒ at risk. Everything runs in your browser; nothing is sent or stored on a server.
01 / YOUR DATA
How long must it stay secret?
Add the kinds of data your organization encrypts, and how many years each must stay confidential. Values are starting points; edit them.
02 / MIGRATION TIME
How long to switch to post-quantum crypto?
03 / Q-DAY ASSUMPTION
When could RSA be broken?
No one knows. Pick the assumption you want to plan for; long-lived secrets deserve a cautious date.
04 / RESULT
Your quantum exposure
| Data | Secret for | Secret until | Margin | Status | Latest start |
|---|
Deadlines
Next steps
Educational estimate, not security, legal or compliance advice. Your answers are kept only in this browser so the page remembers them; “Reset” deletes them.
METHOD & SOURCES
How this works
Mosca’s rule. Let x be how long data must stay secret, y how long your migration to post-quantum cryptography takes, and z the years until a cryptographically relevant quantum computer exists. If x + y > z, data encrypted with RSA or elliptic-curve keys before your migration finishes can be recorded today and read later.
Q-day. Expert opinion, not a fact. In the Global Risk Institute’s 2025 survey of 26 experts, the chance of a quantum computer able to break RSA-2048 within about 24 hours was estimated at roughly 28–49% within 10 years and 51–70% within 15 years.
Deadlines. NIST IR 8547 (final, October 2026) marks RSA, ECDSA, EdDSA and (EC)DH as deprecated after 2030 and disallowed after 2035. Executive Order 14412 (June 22, 2026) requires US federal high-value assets and high-impact systems to use PQC for key establishment by Dec 31, 2030 and for digital signatures by Dec 31, 2031.
Migration estimate. A transparent rule of thumb (years added per answer, shown above). Real programs vary widely; override it when you have your own plan.
Not covered. Symmetric encryption (AES-256) and hashes are not the main concern here; the risk is public-key cryptography used for key exchange and signatures.