- Industries & Communities
- Banking & Finance
- Licensed Engineers & Surveyors
- Enterprise & Corporate
- Government
- Healthcare
- Manufacturing
- Personal & Professional
Image
Post-Quantum Cryptography Explained: Why Your Digital Certificates Are Already at Risk
August 6, 2026 • Marcus Stilwell
Post-Quantum Cryptography Explained: Why your Digital Certificates Are Already at Risk
The phrase “harvest now, decrypt later” sounds like something out of a spy thriller. But it describes a very real strategy that adversaries are already using against organizations that haven’t started thinking about post-quantum cryptography (PQC).
Here’s how it works: a bad actor intercepts and stores encrypted data today, then waits until a quantum computer powerful enough to crack current encryption becomes available. The data may be locked right now, but if the underlying cryptographic algorithm protecting it can eventually be broken, time is the only thing standing between an attacker and your assets.
Quantum computers capable of breaking today’s encryption standards aren’t widely available yet. However, Google’s cryptography migration timeline puts that window as early as 2029, and government deadlines are making the urgency concrete. A June 2026 executive order directs federal agencies to transition their highest-priority systems to PQC encryption by December 31, 2030, and PQC digital signatures by December 31, 2031. Additional FPKI and DoD requirements may push certain deadlines earlier. Private sector timelines are less prescribed, but the underlying pressure is real regardless of who sets the clock. Organizations that start their cryptographic inventory now will have options that late movers won’t.
Every industry is exposed. The data at risk is the same data that organizations depend on every day: encrypted communications, authenticated sessions and TLS-protected web traffic. No sector gets a pass, and partial compromise is enough to cause damage. A hospital whose systems are made temporarily inaccessible can be held for ransom just as easily as one whose patient records are fully stolen.
What Post-Quantum Cryptography Actually Is
Most encryption in use today, including RSA (Rivest-Shamir-Adleman) and ECC (Elliptic Curve Cryptography), relies on mathematical problems that are extremely time-consuming for traditional computers to solve. Factoring a large number into primes, for example, would take a classical computer longer than the age of the universe at sufficient key lengths. That’s the foundation of the security model.
Quantum computers do math differently. Using principles like superposition and entanglement, they can evaluate many possible solutions simultaneously. What would take a classical computer millions of years could take a sufficiently powerful quantum computer a matter of hours. Under that model, RSA and ECC become breakable.
Post-quantum cryptography refers to a new class of cryptographic algorithms designed to resist attacks from quantum computers. In 2024, NIST finalized its first set of PQC standards, establishing the baseline that industries and governments are now building around. Organizations like the CA/Browser Forum are taking their cues from these standards as they update requirements for certificate authorities (CAs) and browsers.
What PQC Means for Digital Certificates
Digital certificates are issued using the same mathematical algorithms that quantum computers will eventually be able to break. When those algorithms change (and they will), certificates will have to change with them. A couple of things shift at once:
- Hardware and software that rely on current cryptographic algorithms, such as cards, tokens, HSMs, servers and browsers, will need to be updated to support the new PQC algorithms because the underlying math is different.
- Key recovery and issuance infrastructure must be rebuilt to support the new PQC algorithms, with one example being Google’s Merkle Tree Certificates project
- Certificate lifecycles accelerate, meaning the rate at which certificates must be requested, renewed and replaced increases exponentially
Post-quantum certificates are already available in private PKI if your organization manages its own certificate authority, you can configure it to issue PQC-enabled certificates today. As public-trust standards catch up, separate requirements are forming for government issuance under FPKI and for public trust under the CA/Browser Forum. Certificates in each channel will look somewhat different from one another.
What Organizations Should Be Doing Now
Most organizations aren’t making a calculated decision to deprioritize PQC. They’re just not thinking about it yet. And at this stage, that gap is the biggest risk.
Stay Current as the Standards Evolve
PQC guidelines aren’t a one-time publication. NIST’s standards will continue to evolve. The CA/Browser Forum’s requirements will tighten. Staying current means building that awareness into your workflow now, not scrambling to catch up when a hard deadline hits. A simple starting point: add NIST’s PQC publications and the CA/Browser Forum updates to an RSS feed. It takes five minutes and will save real headaches in the future because by the time a new requirement makes headlines, you will already be ahead of the curve.
Know Where You Stand with the Post-Quantum Cryptography Maturity Model
One of the harder parts of PQC preparation is knowing where to start and how to measure progress once you do. The PKI Consortium’s PQC Working Group is developing a framework specifically for that purpose: the Post-Quantum Cryptography Maturity Model (PQCMM).
Still in draft form and open for industry feedback, the PQCMM gives organizations and vendors a shared, standardized language for describing PQC readiness. Its six-level scale covers the full spectrum, from no capability at all to full optimization:
- Level 0 — None: No PQC capability in place
- Level 1 — Initial: Early awareness, limited or no formal PQC activity
- Level 2 — Foundational: PQC capabilities available for testing and evaluation
- Level 3 — Advanced: PQC can be configured, typically manually or through beta options
- Level 4 — Managed: PQC is actively managed with documented processes
- Level 5 — Optimized: PQC enabled by default, with benchmarked performance and certified implementations
For procurement and vendor risk teams, the practical value is immediate. Rather than sending lengthy security questionnaires and receiving inconsistent answers, teams can use the PQCMM as a common scale to evaluate vendor readiness more quickly and objectively.
Invest in Automation Before You Need It
The PQC transition touches every certificate type, from TLS to human identity certificates used for document signing and encrypted email. Managing that volume of change across an entire certificate inventory without automation isn’t a realistic strategy.
A practical starting point is a gap analysis against NIST’s PQC standards:
- Where are your current cryptographic dependencies?
- Which systems rely on RSA or ECC?
- Where are your certificates stored, and who manages them?
Answering those questions now puts you ahead of the organizations that won’t start asking until 2027.
The Bottom Line
You don’t need a quantum computer to have a PQC problem. The organizations preparing now will have the time and flexibility to make thoughtful decisions. The ones waiting for a crisis to force the issue will find the options considerably narrower.
Follow the standards as they develop. Get your certificate management automated before the deadlines arrive. And when PQC certificates are ready for your environment, know where to get them.
IdenTrust participates in the CA/Browser Forum and is involved in the policy discussions underway, alongside other industry professionals who are actively building the PQC framework. As those standards finalize across government (FPKI) and public trust channels, IdenTrust will issue certificates that meet each set of requirements.