Skip to content
Great Lakes AI Week 2026 is happening now. November 10 to 12, 2026 · Great Lakes AI Week, produced by Enterprise Technology Association.See the agenda

Free preview. This lesson is part of a paid course that earns the ETA Specialist: Quantum-Safe Readiness for Leaders credential. About this course

Lesson 2 of 21 · Reading

Why this is a leadership program now

In this lesson you'll

  • Explain why post-quantum migration is a leadership program, not an IT ticket
  • State the dates that now drive the work: NIST IR 8547's 2030 and 2035 and the federal 2027 and 2035 milestones
  • Use Mosca's inequality to explain why some data is already at risk today

Welcome

This specialist course from the Enterprise Technology Association (ETA) is for the people who have to make the move to post-quantum cryptography happen: CIOs, CISOs, IT and security managers, risk and compliance owners, procurement leads and the executives who fund them. When you finish the course and pass the final assessment, including a reviewed capstone, you earn the ETA Specialist: Quantum-Safe Readiness for Leaders credential.

The course builds on Quantum-Safe Security: Foundations, ETA's free beginner course. We reuse its vocabulary without re-teaching it: public-key and symmetric cryptography, harvest now, decrypt later, the NIST standards (ML-KEM, ML-DSA, SLH-DSA) and ETA's five Quantum-safe readiness steps: inventory, prioritize, ask vendors, build crypto agility, migrate and test. This course turns those steps into a funded, owned, multi-year program.

Why this is a leadership problem

A large, error-corrected quantum computer would break RSA and elliptic curve cryptography, the public-key methods behind HTTPS, VPNs, sign-in, email security, code signing, certificates and many devices. Nobody can give you a firm date for that machine. That uncertainty tempts organizations to wait. Three facts make waiting the expensive choice:

  1. The deadlines are set even though the machine isn't. In October 2026, NIST finalized NIST IR 8547, Transition to Post-Quantum Cryptography Standards. Quantum-vulnerable public-key algorithms are deprecated after 2030 and disallowed after 2035, at every key size. The final version tightened the 2024 draft: stronger settings such as P-256 and RSA-3072 no longer get a pass until 2035.
  2. Federal buyers move first. National Security Memorandum 10 set 2035 as the goal for federal systems, and the NSA's CNSA 2.0 guidance expects new national security system acquisitions to use quantum-resistant algorithms from 2027. If you sell to government or to their suppliers, questionnaires will ask about your plans long before 2030.
  3. The work is slow. Cryptography is embedded in thousands of places: libraries, appliances, certificates, contracts and devices that last 10 to 20 years. Large migrations, such as the move away from SHA-1 certificates, took about a decade.

None of that is solved by a single purchase. It needs an owner, a budget, decisions about risk and steady pressure on vendors, which is leadership work.

Mosca's inequality: is your data already at risk?

Michele Mosca's rule of thumb is the clearest way to explain the risk to a board. Estimate three numbers in years:

  • X: how long your data must stay confidential
  • Y: how long it will take you to migrate the systems that protect it
  • Z: how long until a quantum computer can break today's public-key cryptography

If X + Y is greater than Z, you have a problem today: someone can record your encrypted traffic now and decrypt it once the machine exists. This is harvest now, decrypt later.

You don't need to know Z to use the rule. Suppose patient records must stay confidential for 25 years (X) and your migration will take 5 years (Y). Unless you are confident a capable quantum computer is more than 30 years away, data you send today over quantum-vulnerable connections is already exposed. Few experts would make that bet.

Signatures work differently. A forged signature only matters once forgery is possible, so the risk there is about how long it takes to replace signing keys, certificate authorities and the devices that check them.

What a program delivers

By the end of this course you will be able to run a program with five outputs your executives can see:

  • A named owner, a budget line and a governance rhythm (Module 1)
  • A cryptographic inventory with priorities (Module 2)
  • Vendor answers, contract terms and crypto agility requirements (Module 3)
  • A migration plan with tests, metrics and a roadmap to 2030 (Module 4)
  • A capstone: your organization's quantum-safe readiness plan, reviewed by ETA

Workplace example: a regional health system

A health system's CISO uses Mosca's inequality in a ten-minute board briefing: records must stay private for decades, migration will take years, so exposure starts now. She asks for an executive owner and a planning budget rather than a big purchase. The board approves both and asks for a first inventory by the next quarter.

Try it

Write your own Mosca estimate for one important data set.

  1. Pick a data set your organization holds (for example, customer contracts, health records, legal files, research or employee records).
  2. Estimate X (how long it must stay confidential) and Y (how long migrating its systems might take).
  3. Write two sentences explaining what the total means for a leader who has never heard of quantum computing. Ask an approved AI tool to check the sentences for jargon, without pasting confidential details.

Key takeaways

  • NIST IR 8547 (final, October 2026) deprecates quantum-vulnerable public-key algorithms after 2030 and disallows them after 2035, at every key size.
  • Federal milestones arrive earlier for national security buyers (2027 for new acquisitions under CNSA 2.0).
  • Mosca's inequality: if shelf life plus migration time exceeds time to a quantum computer, data sent today is already at risk.
  • Post-quantum migration is a funded, owned, multi-year program, and leaders have to start it.

Sources

Report a bug or suggest a feature

It goes straight to the ETA team with the page you're on, so you don't need to send screenshots.

What kind of feedback?