Post-Quantum Qualified Electronic Signatures

OVERVIEW

Post-quantum cryptography has moved from research into standardisation, federal migration planning, and security-assurance discussions. In August 2024, NIST finalised its first three post-quantum cryptography standards: ML-KEM for key establishment, ML-DSA for digital signatures, and SLH-DSA as a stateless hash-based signature scheme.

For organisations responsible for Qualified Electronic Signatures, this transition is not simply about replacing RSA or ECC with a new algorithm. Qualified signatures are designed to remain legally valid and evidentially reliable for many years, often decades. Their trust depends on a complete ecosystem of certificates, trust lists, timestamping, validation services, archival evidence, and regulatory compliance.

This creates a specific challenge for Qualified Trust Service Providers. A document signed today may still need to be verified long after today’s algorithms have been deprecated, validation policies have changed, and relying-party systems have evolved. The question is therefore not only which post-quantum algorithms to adopt, but how to preserve legal trust while the cryptographic foundations underneath that trust continue to change.

At the same time, operational pressure is increasing. AI does not break modern public-key cryptography, but it can accelerate the discovery and exploitation of weak operational controls: exposed secrets, unmanaged certificates, inconsistent cryptographic policies, outdated libraries, undocumented dependencies, and slow remediation processes.

Quantum computing introduces tomorrow’s cryptographic risk. AI increases today’s operational pressure. QTSPs need to prepare for both by strengthening cryptographic governance now and building infrastructure that can adapt as standards, policy, and relying-party expectations evolve.

This is why crypto-agility has become a strategic capability. For QTSPs, crypto-agility means being able to introduce, manage, validate, and replace cryptographic controls without redesigning every application or disrupting trusted services.

DIGITAL TRUST IS ENTERING A NEW ERA

Much of the debate around post-quantum cryptography begins with a technical question: when will quantum computers be able to break RSA and elliptic curve cryptography? That question matters. But for organisations delivering qualified trust services, the more practical question is this: how do we preserve trust while cryptography itself changes?

Encryption protects information while it is transmitted or stored. Once that purpose has been served, the cryptography can often be replaced with limited long-term impact. Qualified electronic signatures are different. A qualified signature creates evidence. It links a person or legal entity to a document, a transaction, or a legally significant action. That evidence may need to remain valid and independently verifiable ten, fifteen, or twenty years after the signature was created.

During that period, algorithms may be deprecated. Certificate policies may change. Trust lists may evolve. Timestamping requirements may mature. Validation services may need to interpret evidence created under older rules. Yet the signature must still be defensible. For QTSPs, this makes post-quantum migration a long-term trust problem rather than a narrow algorithm replacement project. Confidence depends not only on the signing algorithm, but on the surrounding infrastructure: certificates, timestamps, validation evidence, trust anchors, policies, audit trails, and governance processes.

The organisations that manage this transition well will be those that can preserve trust across the full signing and validation lifecycle.

AI INCREASES OPERATIONAL PRESSURE TODAY

Quantum computing represents a future cryptographic challenge. AI is adding pressure to an already difficult operational threat landscape.

AI does not invalidate RSA, ECC, or modern signature schemes. It does, however, increase the speed and scale at which attackers can identify and exploit weaknesses in how cryptography is managed.

For many organisations, the weakest point is not the algorithm itself. It is the operational environment around it: unmanaged certificates, exposed secrets, fragmented key management, inconsistent cryptographic policies, undocumented dependencies, outdated libraries, manual renewal processes, and slow remediation when risks are discovered.

For QTSPs, this matters because trust services depend on disciplined operational governance. A signing service may use strong algorithms, but if certificate lifecycles, key access, policy enforcement, logging, and validation controls are fragmented, the overall trust model becomes harder to defend.

AI increases the pressure to fix these weaknesses. Quantum computing increases the need to change cryptographic foundations over time. Both trends point in the same direction: organisations need stronger visibility, better policy control, and more adaptable cryptographic infrastructure.

WHY WAITING CREATES RISK

One common misconception is that post-quantum migration can wait until a clear “Q-Day” arrives. In practice, the transition will be less simple.

There may never be a single universal moment when today’s public-key cryptography becomes obsolete for every system. Quantum capability, regulatory response, vendor readiness, relying-party support, and sector-specific risk will mature at different speeds.

For QTSPs, waiting is especially risky because the documents they help protect often have long evidential lifetimes. A contract, power of attorney, public-sector filing, banking agreement, or regulated transaction signed today may still need to be verified long after the cryptographic environment has changed.

Migration planning cannot depend only on forecasts about when a cryptographically relevant quantum computer may arrive. QTSPs also need to consider how long signed documents must remain legally valid, how validation evidence will be preserved, when relying parties will support hybrid or post-quantum signatures, and how change can be introduced without disrupting live signing services.

Even a multi-year planning horizon can be tight for qualified trust infrastructure. These environments are deeply integrated into customer journeys, regulatory processes, relying-party systems, archival workflows, and audit models.

Post-quantum readiness should therefore be treated as a staged programme, not a future upgrade.

STANDARDS AND POLICY ARE MOVING BEFORE FULL ECOSYSTEM READINESS

Standards bodies and public authorities are not waiting for large-scale quantum computers to become commercially practical before acting. NIST has finalised its first post-quantum standards, and governments are increasingly pushing agencies, vendors, and critical suppliers to understand their cryptographic exposure and prepare migration plans.

This matters beyond government systems. As public-sector PQC planning moves into assurance, vendor-management, and procurement conversations, trust-service ecosystems will need to respond. QTSPs serving regulated sectors, government-linked customers, cross-border services, or critical digital infrastructure should expect post-quantum readiness to become part of security assurance, procurement, and compliance conversations.

In Europe, the implications for qualified trust services are especially important. eIDAS-governed services depend on a chain of trust that includes qualified certificates, trust lists, qualified timestamping, validation data, supervisory requirements, and long-term preservation of evidence. Post-quantum migration will need to fit into that legal and technical model.

This is why PQC readiness should not be treated as a purely technical initiative. It is becoming a governance issue. Boards, regulators, auditors, and customers will increasingly expect evidence that cryptographic infrastructure is understood, controlled, and capable of change.

For QTSPs, preparation involves more than deploying new algorithms. It requires visibility across cryptographic dependencies, policy-driven signing and validation controls, lifecycle governance, auditability, and a clear path for introducing change without weakening trust.

That capability is crypto-agility.

HYBRID CRYPTOGRAPHY IS THE PRACTICAL TRANSITION PATH

Few organisations are likely to move directly from today’s algorithms to fully post-quantum environments in one step. The industry is preparing for a prolonged hybrid phase, where classical and post-quantum algorithms operate together while standards, certifications, products, and relying-party systems mature.

For qualified signatures, hybrid cryptography is not just a matter of producing two signatures instead of one. It affects the full trust lifecycle: certificate issuance, trust anchors, signature creation, timestamping, validation policies, archival evidence, relying-party interoperability, audit documentation, customer support, and regulatory interpretation.

A test hybrid signature is one problem. Operating hybrid signatures as part of a qualified trust service, with long-term validation and relying-party acceptance, is another.

One of the first design questions is how hybrid credentials should be represented. Several approaches are being explored across the industry, including composite certificates, parallel certificates, and related models that combine or associate classical and post-quantum credentials in different ways. Each approach has implications for issuance, validation, interoperability, certificate chain size, and relying-party support.

QTSPs should be careful not to lock their infrastructure too tightly to one certificate model before the ecosystem has settled. The objective is not to predict the winning format. It is to build signing and certificate-management infrastructure that can support multiple models as standards and supervisory expectations mature.

Validation is the harder long-term challenge. Today’s hybrid models often assume that both the classical and post-quantum components should validate successfully. That may work while both algorithms remain trusted. But the situation becomes more complicated when one algorithm reaches end of life.

If RSA is deprecated, should a hybrid signature still require the RSA component to validate? Should validation depend on the signing date? Should it depend on the policy that applied when the document was signed? What happens when the relying-party system has been updated, but the evidence package was created years earlier?

These are not only technical questions. They carry legal and evidential consequences.

This is why validation architecture matters as much as signing architecture. QTSPs need policy-driven validation frameworks that can evolve over time, rather than fixed assumptions embedded inside applications.

INTEROPERABILITY & LONG TERM VALIDATION CANNOT BE ASSUMED

Even if a QTSP can create hybrid or post-quantum signatures, the wider trust ecosystem may not be ready to consume them. Many document readers, validation services, enterprise workflows, and relying-party systems still assume familiar certificate structures and single-algorithm validation models. Support for hybrid and post-quantum structures will improve, but adoption will not happen evenly.

This creates a practical risk. A signature may be technically valid but appear invalid to the recipient because the consuming software cannot interpret the certificate, algorithm, or validation model. For customers, that distinction may not matter. If the signature appears invalid, trust is damaged.

Long-Term Validation adds another layer of complexity. LTV already combines certificate chains, revocation data, validation evidence, and trusted timestamps into an evidence package that preserves trust beyond the lifetime of individual certificates. Post-quantum cryptography raises new design questions:

noun-evidence-8378652-8F3C97

Should validation evidence be periodically using newer algorithms?

noun-trusted-5433207-8F3C97

How should trust be preserved when one part of the evidence chain relies on an algorithm that later becomes deprecated?

WHY CRYPTO-AGILITY MATTERS MORE THAN ANY ALGORITHM CHOICE

Algorithm selection matters. QTSPs will need to understand which post-quantum standards apply to their services, how those algorithms perform, how they are certified, and how they fit into qualified trust-service regulation. But algorithm choice is not the hardest part of the transition.

Cryptographic standards evolve. Algorithms that were once considered strong eventually become deprecated. Implementation guidance changes. Certification requirements mature. New vulnerabilities appear. Regulatory expectations shift. The organisations that handle these transitions best are not necessarily those that pick the “perfect” algorithm first. They are the ones that can change safely.

Crypto-agility is the ability to introduce, replace, and govern cryptographic controls without redesigning business applications or disrupting critical services.

For QTSPs, this means more than supporting a list of algorithms. It means having centralised cryptographic governance, policy-driven signing controls, flexible certificate management, configurable validation policies, clear key and certificate lifecycle visibility, standards-based interoperability, and audit trails that show how cryptographic decisions were made and enforced.

These capabilities reduce operational risk today and create the foundation for post-quantum migration tomorrow.

A PRACTICAL ROADMAP FOR QTSPs

QTSPs do not need to wait until every standard, product, and supervisory position is finalised before preparing. The most effective migration programmes begin with visibility, architecture, and controlled experimentation.

Organisations need to understand their cryptographic estate. QTSPs need to know which public-key algorithms are used, where certificates are issued, where keys are generated and protected, which services depend on specific algorithms, which documents require long-term validation, and which relying-party systems consume the signatures. Without this visibility, prioritisation is impossible.

Cryptographic policy should be separated from application logic. Signing policy, key handling, algorithm selection, certificate policy, and validation rules should be managed through governed infrastructure rather than embedded directly into every consuming service. This separation is the practical foundation of crypto-agility.

QTSPs should prepare for a long hybrid phase. Classical, hybrid, and post-quantum models are likely to coexist for years. Preparation should include certificate-model evaluation, interoperability testing, validation-policy design, time stamping strategy, archival planning, and customer communication.

Security, engineering, compliance, legal, and commercial teams need a shared migration view. PQC migration affects product roadmaps, compliance obligations, customer contracts, certification planning, service operations, and relying-party expectations.

Organisations should build experience before migration becomes mandatory. Controlled pilots can test hybrid certificates, signing workflows, validation policies, timestamping models, and relying-party behaviour before large-scale production change is required.

HOW CRYPTOMATHIC HELP ORGANISATION PREPARE

Preparing for post-quantum cryptography requires more than selecting new algorithms. It requires an architecture that can support controlled cryptographic change while maintaining operational stability, compliance, and customer trust. Cryptomathic works with banks, payment providers, Qualified Trust Service Providers, and other highly regulated organisations that depend on cryptography for critical digital services.

Across these environments, one lesson is consistent: long-term resilience depends less on predicting which algorithm will dominate and more on building infrastructure that can adapt as standards evolve. For QTSPs, the practical starting point is to reduce hard-coded cryptography in customer applications. Signing policy, key handling, certificate controls, and validation-related decisions should be governed centrally rather than duplicated across every consuming service.

Cryptomathic Signer is designed around this principle. It centralises signing policy and key management behind a governed interface, allowing organisations to manage cryptographic controls in a consistent, auditable, and operationally controlled way. This separation between cryptographic policy and application logic is what makes crypto-agility practical. As post-quantum standards, certificate models, validation requirements, and interoperability expectations evolve, QTSPs will need infrastructure that allows change to be introduced without rebuilding the trust service around every new requirement.

Post-quantum migration should not force organisations to redesign their signing infrastructure each time cryptographic guidance changes. A crypto-agile foundation allows change to be introduced in a controlled, auditable, and predictable way.

CONCLUSION

Post-quantum cryptography represents one of the most significant changes to digital trust in decades. For Qualified Trust Service Providers, the challenge extends far beyond adopting new algorithms.

QTSPs must preserve the legal validity, interoperability, and evidential value of qualified electronic signatures while cryptographic standards, certificate models, validation policies, relying-party systems, and regulatory expectations continue to evolve.

The transition will unfold over years. Hybrid cryptography will mature. Validation models will change. Relying-party software will gradually adapt. Regulators and auditors will ask for stronger evidence of cryptographic governance. Customers will expect trusted services to remain stable throughout.

Organisations that treat post-quantum cryptography as a one-time migration project risk repeating the same disruption each time standards or requirements change. Organisations that invest in crypto-agility will be better positioned to adapt continuously while protecting trusted services and long-term legal assurance.

The future of qualified electronic signatures will not be determined only by which algorithms are adopted. It will be determined by how effectively organisations can manage cryptographic change without compromising trust.

cryptomathic_symbol_purple_positive_transparent-1

PREPARING FOR POST-QUANTUM CRYPTOGRAPHY STARTS WITH UNDERSTANDING YOUR CURRENT CRYPTOGRAPHIC LANDSCAPE

Speak to a Cryptomathic expert to explore how a crypto-agile signing infrastructure can help your organisation prepare for the post-quantum transition while preserving security, compliance, and long-term trust.

PREPARING QUALIFIED ELECTRONIC SIGNATURES FOR THE POST-QUANTUM ERA

Why Crypto-Agility Will Define The Future Of Digital Trust