Post-Quantum Cryptography for Canadian SMBs: Why the Clock Is Already Running

Most quantum computing coverage falls into one of two failure modes: breathless predictions about an imminent Q-Day catastrophe, or dismissal because "quantum computers can't break anything yet." Both misread the threat. The question that matters for Canadian SMBs is not whether quantum computers can break your encryption today. It is whether the data you are transmitting *right now* will still be sensitive in 2032 — and whether adversaries are collecting it today for later.

What Post-Quantum Cryptography Means

Almost everything that secures internet traffic — TLS connections, VPN tunnels, SSH server access, email signing, document certificates — is built on mathematical problems that classical computers cannot solve in practical time. RSA-2048, ECDSA, and Diffie-Hellman key exchange have protected communications for decades because factoring large primes would take a classical computer longer than the age of the universe.

A sufficiently powerful quantum computer changes that entirely. Shor's algorithm, published in 1994, can solve both problems exponentially faster on quantum hardware. The same TLS session protecting a client contract, the VPN tunnel carrying health records, the certificate authenticating a financial transaction — all of it becomes readable.

Post-quantum cryptography (PQC) is a new generation of cryptographic algorithms designed to be secure against both classical and quantum computers. They rely on lattice-based mathematics, hash-based signatures, and code-based structures rather than prime factorization or elliptic curves. In August 2024, the U.S. National Institute of Standards and Technology finalized the first three PQC standards:

• FIPS 203 (ML-KEM): Replaces RSA and ECDH for key exchange in TLS, VPNs, and messaging.
• FIPS 204 (ML-DSA): Replaces ECDSA and RSA for digital signatures — certificates, code signing, authentication.
• FIPS 205 (SLH-DSA): A hash-based signature standard with more conservative mathematical assumptions as a fallback.

Canada's Cryptographic Module Validation Program (CMVP) is jointly managed by the Canadian Centre for Cyber Security (CCCS) and NIST — which means NIST's PQC standards automatically become the Canadian standard for validated cryptographic modules. (NIST — Post-Quantum Cryptography Standards)

The Attack Already Under Way: Harvest Now, Decrypt Later

The quantum computer capable of breaking RSA-2048 does not exist today. But the attack that exploits it has already begun.

Nation-state adversaries are collecting and archiving encrypted network traffic at scale — TLS sessions, VPN packets, authentication tokens — with the explicit intent to decrypt it once quantum hardware becomes available. This is the Harvest Now, Decrypt Later (HNDL) attack model, and Five Eyes intelligence agencies treat it as an active ongoing threat, not a hypothetical.

As Palo Alto Networks describes it: "adversaries with access to encrypted network traffic can store ciphertext today and decrypt it once a cryptographically relevant quantum computer becomes available."

The implication for Canadian SMBs is direct: if your business transmits data today that will still be sensitive in 2032 — client health records, legal privileged communications, competitive intelligence, government-related documents, financial histories — that data is a valid HNDL target right now. The collection happens silently. There is no breach notification. The clock starts the day a capable quantum computer comes online.

How Close Is Q-Day?

Expert consensus has tightened considerably. IBM's quantum roadmap projects fault-tolerant systems with hundreds of logical qubits by 2029 and 100,000+ physical qubit systems by 2033 — a scale at which breaking RSA-2048 could become feasible in hours or days. Industry consensus places the probability of a cryptographically relevant quantum computer existing by 2035 at greater than 50%. (Quantum Zeitgeist, 2026) More concerning: three papers published between May 2025 and March 2026 reduced the estimated quantum resources needed to break RSA-2048 from 20 million qubits to fewer than one million — a significant compression of the risk timeline. (The Quantum Insider, 2026)

The 2030–2035 window matters for one specific reason: that is approximately how long a migration takes. Organizations that wait for confirmed Q-Day will not have time to respond. The CCCS, NIST, and every major signals intelligence agency agree on this point.

Canada's Timeline and What It Means for Private Sector SMBs

The CCCS Roadmap: ITSM.40.001

On June 23, 2025, the CCCS published ITSM.40.001, Canada's formal roadmap for government-wide post-quantum cryptography migration. (CCCS — ITSM.40.001) It sets four hard milestones:

The roadmap requires departments to build a comprehensive cryptographic inventory first — identifying all instances of public-key cryptography across servers, laptops, smart cards, printers, VoIP phones, network appliances, and cloud services — before assigning migration priority.

The Contract Clause That Reaches Private Sector Vendors

Here is where the government's deadline becomes a direct private sector obligation.

On September 1, 2025, the CCCS published ITSM.00.501 — Recommended Contract Clauses for Cryptography. (CCCS — ITSM.00.501) A subsequent Treasury Board Security Policy Implementation Notice (SPIN) issued October 9, 2025 made the practical effect clear: contracts with a digital component entered after April 1, 2026 are expected to include clauses requiring vendors to support PQC-compliant key establishment and digital signature schemes by end of 2026, use CMVP-validated cryptographic modules, and maintain cryptographic agility — the ability to reconfigure algorithms, parameter sizes, and key lengths. (Government of Canada — PQC SPIN)

This is not limited to large defence prime contractors. Any Canadian SMB providing software, managed services, cloud hosting, IT services, or data processing to a federal department or agency — or subcontracting to a company that does — falls within scope on contracts signed or renewed after April 1, 2026. The requirement propagates through the entire federal supply chain.

If you hold a federal contract or your clients do, this is a compliance requirement with a current-year date attached.

Canada's G7 Commitments

The CCCS has formally endorsed the G7 Cybersecurity Working Group's statement on preparing for post-quantum cryptography migration. (CCCS — G7 Statement) In January 2026, the G7 Cyber Expert Group published a coordinated quantum roadmap targeting the financial sector specifically, setting expectations for quantum-resilient systems across G7 economies. (G7 CEG Quantum Roadmap) Canada's 2025 National Cyber Security Strategy embeds quantum resilience as a national security priority. (ISED — National Quantum Strategy)

Which Canadian SMBs Carry the Highest Exposure

Not all businesses face equal HNDL risk. The organizations that should prioritize PQC planning most urgently:

Federal vendors and subcontractors. Contract clauses from April 2026 onward require PQC compliance. Existing contracts face the same requirements on renewal.

Healthcare and life sciences. Patient records, genomic data, and insurance claim histories are exactly the long-lived sensitive data HNDL attacks are designed to exploit. PIPEDA and provincial health privacy legislation will apply to retroactive exposure of health records just as they apply to live breaches.

Legal and professional services. Solicitor-client privilege attaches to communications for decades. Encrypted email and document transfers containing privileged communications are high-value HNDL targets.

Financial services. Transaction histories, account credentials, and loan documents carry multi-decade sensitivity. Canadian financial regulators are tracking the G7 Quantum Roadmap closely.

Technology and SaaS companies. Code-signing keys, API authentication, and customer data pipelines all rely on the cryptographic primitives being replaced. Companies that sell into enterprise or government markets face both direct exposure and supply chain obligations from their customers.

What to Do in 2026

The full migration is a multi-year project. But the work this year is defined and manageable.

Build a cryptographic inventory. Identify every place public-key cryptography is in use: TLS certificates, VPN and SSH configuration, code-signing certificates, email signing, API authentication tokens, database encryption keys, and vendor or cloud services you depend on. CISA, working with NSA and NIST, provides a migration playbook that covers automated discovery approaches for environments where manual enumeration is impractical.

Classify your data by sensitivity lifetime. For each major data category, ask how long it must remain unreadable to be safe. Data whose confidentiality needs to hold beyond 2030 is an HNDL risk today and should be prioritized in migration planning.

Assess your software and vendor stack. Which vendors have published PQC migration timelines? Azure Key Vault and Azure Managed HSM are on track for PQC support in 2026. OpenSSL 3.2+ includes PQC-enabled TLS support. If a critical vendor has no PQC roadmap, document it as a risk and raise it in your next contract review.

Plan for hybrid cryptography during transition. The recommended approach is to run classical and post-quantum key exchange simultaneously — a TLS handshake using both ECDHE and ML-KEM provides protection against both classical and quantum attacks while PQC libraries and infrastructure are validated and deployed across the stack. The CCCS and NIST both recommend this hybrid approach for the migration window.

Review your federal contract terms. If you hold government contracts, determine whether they fall under the April 2026 compliance expectation and build PQC readiness into upcoming renewals and new bids as a standard deliverable.

Post-quantum cryptography is not a future problem. The HNDL attack is already running. Canada's compliance timeline is already active. Organizations that begin their cryptographic inventories and vendor assessments now are the ones that will navigate this transition without crisis — and without a last-minute scramble to satisfy contract clauses in 2028.

Sources

• Canadian Centre for Cyber Security. *Roadmap for the migration to post-quantum cryptography for the Government of Canada (ITSM.40.001).* cyber.gc.ca
• Canadian Centre for Cyber Security. *Recommended Contract Clauses for Cryptography (ITSM.00.501).* cyber.gc.ca
• Canadian Centre for Cyber Security. *G7 Cybersecurity Working Group Statement on preparing for a post-quantum cryptography migration.* cyber.gc.ca
• Government of Canada. *Migrating the Government of Canada to Post-Quantum Cryptography: Security Policy Implementation Notice.* canada.ca
• ISED. *National Quantum Strategy Roadmap: Quantum Communication and Post-Quantum Cryptography.* ised-isde.canada.ca
• NIST. *Post-Quantum Cryptography Standards (FIPS 203, 204, 205).* nist.gov
• CISA. *Post-Quantum Cryptography Initiative.* cisa.gov
• Palo Alto Networks. *Harvest Now, Decrypt Later: Quantum Security Risk.* paloaltonetworks.com
• Quantum Zeitgeist. *Cryptographically Relevant Quantum Computer: Complete 2026 Guide.* quantumzeitgeist.com
• The Quantum Insider. *"Harvest Now, Decrypt Later": Why Should You Care?* thequantuminsider.com
• G7 Cyber Expert Group. *G7 CEG Quantum Roadmap.* home.treasury.gov

Post-quantum cryptography migration starts with knowing where quantum-vulnerable cryptography lives in your environment. Cloud Forces helps Canadian SMBs build cryptographic inventories, assess vendor PQC readiness, and develop a migration plan aligned with CCCS guidance and federal supply chain requirements. Explore our Cybersecurity services or contact us to book a no-cost PQC readiness assessment.