Quantum Age Readiness: Why Security starts long before

Quantum computers will continue to improve in stability, scale, and error correction (for example, see this recent advancement that could slash errors by up to 100 times), while cryptographic standards (algorithms and protocols) are evolving in parallel. Algorithms that are considered safe today may be deprecated tomorrow, not only because of quantum threats, but also due to classical cryptanalytic advances or implementation weaknesses. 

This reality demands a level of adaptability that many IT landscapes were never designed for. Cryptography in most organizations is deeply embedded, scattered across applications, libraries, devices, cloud services, and third-party software, often without clear ownership or documentation. When change becomes necessary, the challenge is often not knowing what to change, but even knowing where cryptography is being used in the first place.

This is why meaningful post-quantum preparation does not begin with cryptographic standards, but with understanding data. Before discussing strategies, migration paths, or new algorithms, organizations must first know which data they process, where it flows, and how long it needs to remain protected. Cryptography was never meant to protect data indefinitely; it protects it only for as long as the underlying algorithms remain secure. If certain data must stay confidential for decades, then its cryptographic protection must already account for future threats today. This is especially relevant in the context of so-called “harvest now, decrypt later” attacks, where encrypted data is collected today with the expectation that it can be decrypted once sufficiently powerful quantum computers become available.

Many companies already maintain partial data inventories for regulatory reasons such as the Swiss FADP (Federal Act on Data Protection) or GDPR, but these are rarely connected to concrete cryptographic requirements. Yet this connection is crucial, because not all data justifies the same level of cryptographic effort, and over-securing everything can be as harmful as under-securing critical assets, especially when performance, availability, and operational complexity are considered.

Once data criticality and protection horizons are understood, cryptography can be treated as what it truly is: a business-critical infrastructure capability rather than a purely technical detail. This is where governance becomes unavoidable. Cryptographic decisions affect compliance, availability, vendor dependencies, and long-term risk exposure. In practice, this means that cryptography cannot remain fragmented across isolated development teams or hidden inside infrastructure silos.

Many organizations therefore move toward establishing a cryptographic center of excellence (CCoE) or similar governance structure that defines policies, approves cryptographic standards, and coordinates transitions across departments and platforms. Such a function also becomes the natural interface to external vendors, cloud providers, and software suppliers, whose cryptographic roadmaps directly influence an organization’s own ability to migrate in time. Post-Quantum Readiness is therefore not just an internal transformation but an ecosystem challenge, where customer pressure, procurement requirements, and even contributions to open-source projects may be necessary to accelerate adoption.

However, strategy and governance alone are powerless without technical visibility. One of the most underestimated problems in cryptography today is not weak algorithms, but unmanaged cryptography.  For example, routine audits often uncover SHA-1 or outdated TLS versions still in use across production systems, even in 2026, many years after they were declared insecure.

Hard-coded keys, expired certificates, undocumented protocol usage, and unapproved libraries are rarely the result of malicious intent, but of missing oversight. Without continuous visibility into where cryptography is used, which algorithms are deployed, and how systems depend on each other, every migration effort becomes reactive, slow, and risky. This is why cryptographic inventories are gaining so much attention: not as static documentation, but as living systems that continuously discover cryptographic assets, map dependencies, and provide data that can be queried for compliance, risk analysis, and operational planning. Only when such visibility exists can organizations move from theoretical security strategies to concrete, prioritized action.

With visibility and governance in place, migration becomes an engineering problem rather than a crisis response. Even then, cryptographic transitions are rarely simple replacements. Data must be re-encrypted, keys rotated, protocols upgraded, and systems tested in ways that avoid outages or data loss. In many cases, hybrid approaches are necessary, where classical and post-quantum algorithms coexist to ensure compatibility and gradual rollout. This phase also presents opportunities such as deleting obsolete data that no longer needs to be protected instead of migrating, reducing both risk and cost. Migration therefore becomes not only a security exercise, but also a chance to reduce long-standing technical debt.

Yet even successful migrations only solve today’s problems if systems are not designed to change again tomorrow.  This is where cryptographic agility becomes essential: Algorithms and keys can be interchanged through configuration and managed migration flows (such as re-keying), without rewriting entire code bases or rebuilding underlying architectures and infrastructure components (such as HSMs)

Practically, this requires cryptography to be decoupled from business logic, relying on centralized key management systems, hardware security modules, and well-designed APIs rather than embedded code. It also requires automation, because manual key handling and configuration changes do not scale and inevitably lead to errors. When cryptography becomes an interchangeable service rather than a fixed implementation detail, organizations gain the ability to respond quickly not only to quantum threats, but also to new vulnerabilities, regulatory changes, and evolving security standards.

What ultimately determines whether these technical capabilities translate into real progress, however, is organisational readiness. This includes leadership awareness of cryptographic risk, willingness to invest in tooling and skills, availability of specialized expertise, and the ability to align internal teams and external suppliers around common security objectives. Without this readiness, inventories may remain incomplete, architectural guidelines might be ignored, and migrations might be perpetually postponed by competing priorities. With it, even complex transitions become achievable because they are treated as long-term programs rather than emergency responses.

Taken together, post-quantum security can therefore be viewed as the result of a few core factors reinforcing each other. In a simplified and symbolic way, it can be expressed as:

PQS ≈ ((Visibility × Agility)^Organisational Readiness)+PQC

Again, this is not mathematics, but a way of illustrating relationships:

• Visibility represents how well cryptographic usage is discovered, monitored, and understood across systems and dependencies.
• Agility reflects how easily cryptographic mechanisms can be changed without refactoring source code or redesigning architecture.
• Organisational Readiness captures awareness, skills, funding, governance, and vendor alignment that allow technical change to happen at scale.
• PQC represents the availability and maturity of post-quantum algorithms and implementations that can be deployed when required.
   

The multiplication indicates that both visibility and agility are necessary; weakness in either severely limits progress. The exponent reflects how strongly organisational readiness amplifies or constrains what is technically possible. And the addition of PQC acknowledges that new algorithms are essential, but only become effective once an organization can deploy them in practice.

Ultimately, post-quantum security is not a single project with a fixed end date. It is the continuous ability to adapt cryptographic protections to threats as technologies and regulations evolve. Organisations that start building this capability now will not only be better prepared for the presence of cryptographically relevant quantum computers, but also more resilient against today’s very real cryptographic risks. Waiting until quantum computers become powerful enough is no longer a neutral choice. Data can already be “harvested now and decrypted later,” putting sensitive information at risk even today. Those who delay further may discover that the hardest part was never the mathematics, but the organisational readiness to change.