The Day Encryption Breaks — And Why Almost No German Industrial Company Is Prepared

An analysis of the quantum threat, Germany’s standing in international comparison, and the architectural answer hardly anyone is preparing for: crypto-agility.

The Wrong Question

Over the past eighteen months, quantum computing has arrived in the boardrooms. That is the good news. The bad news: the debate is centered on the wrong question.

What gets discussed is when powerful quantum computers will break today’s standard encryption methods — RSA-2048, ECC, classical key exchange protocols. Estimates range from 2030 to 2040. The answer to that question does not interest me. It cannot be answered seriously anyway.

The right question is:

Are you able to replace cryptographic algorithms across your system landscape — without rebuilding half your IT?

Anyone who has no clear answer to that question does not have a quantum problem. They have an architecture problem. And that is acute, not academic.

Picture a typical scenario — an automotive Tier-1 supplier with 800 suppliers, twelve SAP systems, EDI connections to 40 OEMs, a machine park with over 2,000 networked controllers, and a long-term archive for signed engineering data with a statutory retention period of ten years. This company is real. We will return to it throughout this article.

The Problem: Three Waves, Not One

The quantum transformation will not arrive as a single event. It arrives in three waves that overlap in time.

The first wave is already running — today, right now. It is called Harvest Now, Decrypt Later. State actors and organized groups have been collecting encrypted traffic for years that they cannot decrypt today — but will be able to decrypt in ten or fifteen years. What is protected today by SSL/TLS, encrypted email, and VPN tunnels is not protected forever. It is protected until the mathematical foundation breaks.

For our Tier-1 supplier, this means concretely: every engineering drawing, every bill of materials, every price calculation that travels over public networks today can be decrypted tomorrow or in ten years. The confidentiality period of a patent is twenty years. The economic half-life of a platform strategy in automotive is the same. Anyone who thinks today, “it won’t take that long anymore,” has not understood the half-life of their own protected assets.

The second wave is the algorithm break itself. When it comes, nobody knows. That it will come, the cryptographic community knows with high certainty. The U.S. NIST standardized the first post-quantum algorithms in 2024. The German BSI updated its national recommendations the same year. The algorithms are on the table. The question is no longer whether they will come — but how fast they can be migrated into industrial systems.

The third wave is industrial application. This is where competitiveness is decided. Whoever makes it through the first two waves without architectural pain will be able to use quantum-supported optimizations for materials science, logistics, and simulation in the third. Whoever drowns in the first two waves will have no resources left for the third.

Germany in International Comparison: A Lot of Discussion, Little Preparation

The international comparison is sobering.

The United States set clear transition deadlines with National Security Memorandum 10 in 2022 and the CNSA 2.0 mandate in 2024: federal agencies must complete the migration to post-quantum cryptography by 2035. More important than the date is the mechanism: the requirement cascades through the Defense Industrial Base into the supply chains — and therefore into German companies that supply into the U.S. defense environment.

France, through ANSSI, has published a national PQC roadmap with three phases: hybrid phase until 2025, transition phase until 2030, full migration by 2035. The roadmap is not just a document — it is binding for critical infrastructure.

The United Kingdom, through the NCSC, published a migration guideline in autumn 2024 with three milestones: inventory by 2028, critical systems migrated by 2031, full migration by 2035.

Germany. The BSI has published technically excellent recommendations. What is missing is the binding, cross-sectoral migration plan with dates. What is missing is the political bracket that turns recommendation into action. The consequence: German industrial companies can orient themselves around international frameworks — but they have no national clarity about what becomes mandatory when.

This is not a reproach to the BSI. It is an observation about the governance gap between technical expert level and industrial-policy commitment.

What This Means Economically — The Board-Level Exit Point

If you have read this far as a board member, CDO, or COO, you know the essentials. The following sections are for your architects and CISOs. What you need to know fits into five sentences:

The threat is real, but staggered in time. You have years, not months — but you do not have twenty years.
Migration is not a crypto project, it is an architecture project. It affects every system that uses encryption, signatures, or certificate management — which means practically everything.
Your supplier dependency is your largest risk. If your ERP, MES, or PLM vendor has no PQC roadmap with a date, you have none.
Ownership inside the company is unresolved. CISO, CIO, and CDO each point to the others. This is the most common and most dangerous form of quantum risk.
The answer is crypto-agility. Not which algorithm — but how exchangeable algorithms are in your architecture.

If you read on from here, we change altitude.

The Four Building Principles of Crypto-Agility

Crypto-agility is not a product. It is an architectural property. It rests on four principles.

First: Abstraction. Cryptographic operations are never wired directly into application logic. They are encapsulated behind an abstraction layer (crypto service provider, cryptographic library with a defined interface). The algorithm becomes a replaceable implementation behind a stable interface.

Second: Inventory. Every use of cryptography in the company — certificates, keys, signatures, encryption endpoints — is managed in a central Crypto-BOM (Bill of Materials). What is not inventoried cannot be migrated.

Third: Hybrid capability. During the transition phase, systems must be able to operate classical and post-quantum algorithms in parallel. This is not trivial: it doubles key material, bandwidth, and storage requirements. But it is the only bridge that avoids a big-bang migration.

Fourth: Governance. A named role with mandate, budget, and reporting line to executive leadership is required. Crypto-agility without ownership is a slide, not a project.

The Crypto-Agility Maturity Model — Five Stages

This is the core of this article. Place your company honestly.

Stage 0 — Crypto Unknown. No inventory of cryptographic components exists. Encryption has grown organically over decades and nobody has the overview. The question “Where do we use RSA-2048?” cannot be answered. The most common maturity level in the German mid-market.

Stage 1 — Crypto Visible. An initial inventory exists, usually as an Excel list produced for an ISO 27001 audit. It is incomplete, unversioned, unmaintained. Crypto is visible, but not steerable. The most common maturity level in mid-sized to large industrial companies.

Stage 2 — Crypto Inventoried. A complete Crypto-BOM exists, is maintained, and is linked to the CMDB. Supplier components are captured, including the algorithms they use. A named role is accountable. Algorithm exchange is not yet possible system-wide, but the precondition is in place.

Stage 3 — Crypto Abstracted. In-house applications use cryptographic operations exclusively through an abstraction layer. Algorithms are exchangeable in configuration, not in code. Hybrid operation (classical + PQC) has been piloted. For our Tier-1 supplier, this would mean: SAP connectors, the EDI gateway, and the internal PKI run through central crypto services that can be switched via configuration.

Stage 4 — Crypto Agile. Algorithms can be exchanged across all critical systems — own and procured — within defined deadlines. Suppliers are contractually obligated to PQC readiness. The company can react to new cryptographic threats without setting up a migration project. It has turned a project into a capability.

In German industry, the overwhelming majority is between Stage 0 and Stage 1. Stage 3 has been reached in individual large enterprises. Stage 4 is, as far as I can see, not operationally established anywhere in the German-speaking industrial space today.

That is not a disgrace. It is a baseline.

The Three-Question Diagnostic

If you want a rough estimate of your position without commissioning a full maturity assessment, answer these three questions honestly:

Question 1 — Inventory. Can you produce, within 14 days, a complete list of every place in your system landscape where RSA, ECC, or other quantum-vulnerable algorithms are used — including the components operated by your suppliers? If not: you are at Stage 0 or 1.

Question 2 — Suppliers. Which of your five most strategic software and infrastructure suppliers have provided you with a PQC roadmap with a concrete date? If the answer is “none” — and I suspect it is — then that is not the suppliers’ problem. It is yours. You never demanded it.

Question 3 — Ownership. Who in your company holds the mandate to steer the crypto migration? If the CISO says “that’s architecture”, the CIO says “that’s security”, and the CDO says “that’s infrastructure” — then you have no owner. You have a gap. That gap does not close by itself.

Closing: The Wave That Is Running Today

The first wave of the quantum transformation is not in the future. It is running. Encrypted data is being collected today to be decrypted tomorrow. This is not a hypothesis. It is the standing assumption of every serious threat model.

The second wave — the algorithm break — is coming. When exactly, nobody knows. That preparing for it takes years is known by anyone who has ever migrated a PKI.

The third wave — industrial application — will decide who is technologically capable of acting in the 2030s. It will not be won by whoever has the fastest quantum computers. It will be won by whoever has an architecture that can absorb cryptographic breaks without having to reinvent itself.

Do not start with the migration. Start with the inventory. Whoever does not know what they have cannot replace what they need.

The task is large. But it is solvable — if it is understood for what it is: not a crypto question, but an architecture and leadership question. Exactly where the “Industrial Translator” perspective begins: between technological possibility and operational reality.

E-Mail: sven.vollmer@business-quotient.com

Sven Vollmer is “The Industrial Translator.” He bridges the gap between industrial operational reality (SAP, supply chain) and the possibilities of generative AI. His focus is on value-creating applications—beyond the hype.

Transparency Note: This article was created with editorial support from AI (Gemini/Claude). The ideas, technical validation, use case selection, and adult supervision were 100% authored by Sven Vollmer.

LinkedIn: www.linkedin.com/in/sven-vollmer-bq