Loading the assay ledger
Analysis
Exposure is measured against the year your data must still be secret, not against the certificate's expiry. Move the horizon and every stored assay is re-rated by the engine.
Confidentiality horizon
The year by which traffic captured today must still be unreadable. Everything to the left of this mark is already inside your risk window.
2040
Use the arrow keys to step by a year. Press Enter, or use the button, to persist the horizon and re-rate every stored assay.
Projected exposure across the ledger
0 of 0 exposed
No assays yet. Run one from the ledger and it will appear on this scale.
A ninety-day certificate is the standard remedy for a leaked key, and it works against an adversary who has to break the key now. It does nothing against one who simply records the session and waits. The ciphertext they stored in March 2026 does not expire with the certificate that carried it.
So the question that matters is not when this certificate ends. It is whether the key behind the traffic you have already emitted will still be unbroken in 2040, the year by which anything captured today has to have become unreadable.
For most organisations that horizon is driven by data whose secrecy has to outlive a hardware refresh cycle: infrastructure signing keys, PKI roots, long-lived government or health records, code-signing material. NIST IR 8547 prioritises exactly those, naming PKI and code signing as the systems that carry the longest preparation lead time.
Assumptions behind the dial
Base physical qubit count anchored to publicly announced processor sizes (IBM Condor 1,121 qubits, Dec 2023); annual growth is a user-set assumption, not a forecast. Change any of these in settings.
Run one assay and it will appear on the scale above, with its projected break year marked against your horizon.
Run an assay