Sebastien Rousseau

QUANTUM-SAFE READINESS

From Awareness to Action: What Quantum-Safe Readiness Requires Now

EPAA's new white paper argues that banks get quantum-safe by naming an accountable executive and tracing one payment flow end to end, not by finishing a cryptographic inventory first.

15 min read
Banner for: From Awareness to Action: What Quantum-Safe Readiness Requires Now

Banks don't get quantum-safe by finishing a cryptographic inventory. They get there by naming an accountable executive, tracing one payment flow end to end, and using what that trace reveals about vendors, counterparties and shared infrastructure to decide what to do next.

Executive Summary

  • In July 2026, the Monetary Authority of Singapore published that it was issuing formal supervisory expectations, including progressive milestones for cryptographic inventories, migration prioritisation, and capability building.
  • Hong Kong's banking sector scored 2.3 out of 10 on the Quantum Preparedness Index. Half of authorised institutions had no structured plan for cryptographic upgrades, and the HKMA expects the sector to achieve full readiness by 2030.
  • The paper's central recommendation is to assign an accountable executive, authorise a limited first assessment, and trace one clearly defined payment flow from initiation through clearing and settlement.
  • Dependencies on middleware, managed services, fraud platforms, clearing houses, correspondent banks and counterparties may determine the pace of migration, so procurement, third-party risk management and network management belong in the readiness programme.
  • Some parts of the migration have no settled answer yet, and cross-border operators can't assume uniform algorithms, requirements or timetables across markets.

This is a reading of From Awareness to Action: What Quantum-Safe Readiness Requires Now, the November 2026 white paper from the Emerging Payments Association Asia's Quantum Safe Cryptography Working Group. Download the full paper.

What the regulators and the index are saying #

Start with the supervisors, because they've stopped treating this as a research topic. In July 2026, the Monetary Authority of Singapore published that it was issuing formal supervisory expectations. Those include progressive milestones for cryptographic inventories, migration prioritisation, and capability building. Three milestones, each one a deliverable a supervisor can ask to see.

Hong Kong's picture is less comfortable. The banking sector scored 2.3 out of 10 on the Quantum Preparedness Index. Half of authorised institutions had no structured plan for cryptographic upgrades, and half had not assessed whether technical infrastructure was ready for post-quantum security requirements. Among institutions that did have transition plans, the average implementation timeframe was 5.6 years. The HKMA expects the sector to achieve full readiness by 2030.

Put those figures next to each other and the tension is plain. A sector score of 2.3 out of 10, a regulator's stated 2030 expectation, and plans that average 5.6 years to implement describe an industry that hasn't yet reconciled its own timelines. I'd argue the interesting question isn't which algorithm to adopt. It's why half of the institutions covered had no structured plan at all.

One caution belongs here. The workshop participants behind part of this discussion were professionals who had already chosen to attend a session on the topic. They're an engaged group, not a random sample of the industry, so their views are a poor guide to how the typical institution is placed.

Accountability before architecture #

The paper draws a pointed conclusion from the Hong Kong findings, and it frames it with a hedge. The findings suggest that progress begins when someone becomes accountable for quantum safe readiness, rather than presuming it's an issue for technology teams to oversee. That's a suggestion, not a proven causal law, and I'd treat it that way. But it fits what the numbers show: where nobody owns the problem, half the institutions end up with no structured plan.

What does ownership look like in practice? The paper is specific. Senior leadership needs to assign clear ownership and authorise a limited first assessment. It also recommends appointing an accountable executive with sufficient authority to coordinate the work and bring decisions to the board. Authority matters as much as the title. An owner who can't convene architecture, security, procurement and risk teams, or who can't take a decision to the board, has a job description and nothing else.

The limited first assessment is the practical lever. The paper says it provides the evidence needed to set priorities, engage vendors, and develop a credible roadmap. That's a modest ask of a leadership team. It doesn't require approving a multi-year programme on the strength of a slide deck. It requires someone to say who's responsible and to permit a bounded piece of discovery work, which then produces the facts the larger decisions need.

Why the exhaustive inventory stalls #

A cryptographic inventory is a record of where and how cryptography is used across an organisation. Nobody serious disputes its value. The trouble starts when it's treated as a gate. The paper notes that trying to identify every cryptographic asset before making changes can, in practice, leave organisations mapping indefinitely while the environment continues to change. That's hedged language, and fairly so: it describes a risk, not a certainty. But anyone who has watched an asset-discovery exercise outlive its own scope will recognise it.

The paper also makes a definitional point that sharpens the problem. An inventory is not a one-off deliverable and will need to develop as systems, vendors, standards, and threats evolve. If it's never finished by nature, then making it a precondition for action means action never starts. Singapore's milestones for inventories are described as progressive, which sits more comfortably with that reality than a single completion date would.

The alternative the paper offers is simple: the practical approach is to build knowledge and action together. A small team can begin by identifying where cryptography is used within a few important systems, then consider business and security risks to decide what to examine next. It also recommends using available tools to identify cryptography within a limited number of high-value systems rather than waiting for an enterprise-wide inventory. Knowledge and action advance in step, and each round of findings tells you where to look next.

I think this is the strongest practical idea in the material, because it removes a false choice. Teams often believe they must pick between doing a thorough survey and doing something useful. The paper's position is that you do the useful thing on a small scale and let it direct the survey.

Tracing a single payment flow #

The paper gets concrete about where to begin: with a clearly defined payment flow or service, selected according to risk and practical feasibility. Then trace it from initiation through clearing and settlement. Risk tells you where the exposure is worth the effort, and feasibility keeps the first attempt from collapsing under its own ambition.

There's a security reason to care about the exposure. The paper says that information captured in encrypted form today could potentially be decrypted in the future. That's a hedged statement and it should stay one, but it explains why payment flows carrying sensitive data deserve early attention. Data protected today may still matter later.

The paper is careful to say what the exercise is not. The objective isn't to select one payment rail and ignore the rest. It's to create a repeatable method that can be expanded across the wider estate. This distinction matters for founders and engineering leads deciding how to scope the work. The first flow is a rehearsal for a process, and the artefact worth keeping is the method: the questions you asked, the people you needed, the places where the trail went cold.

Why trace the whole flow rather than audit the payment application? Because following one payment flow from initiation through clearing and settlement often exposes dependencies that are not visible from the payment application alone. The word "often" is a hedge, but the logic is easy to follow. An application inspected in isolation shows its own cryptography. A flow shows everything the application relies on and everyone it talks to.

The paper proposes a test that I find unusually clear. Ask whether the bank could rotate the certificates supporting the flow without coordinating with multiple third parties or clients. If the answer is no, you've found a dependency, and you've found it with a question a non-specialist can understand. It's a better diagnostic than a long checklist because the answer either involves other organisations or it doesn't.

Dependencies the bank doesn't control #

Once the trace is underway, the same pattern keeps appearing: much of what determines readiness sits outside the institution. The paper lists several places this can happen, and all of it is framed with hedged verbs.

Middleware, managed services, fraud platforms, and other third-party products may contain cryptographic dependencies the bank does not control. Clearing houses, real-time gross settlement operators, payment schemes, correspondent banks, and their certification windows can finally determine when an end-to-end payment flow is ready to migrate. And because payment messages are signed or encrypted between parties, migration may move at the pace of the least-ready participant exchanging them.

Read together, those statements describe a chain whose slowest link sets the speed. A bank can finish its own internal work and still be unable to switch a flow over, because a scheme's certification window hasn't opened or a counterparty hasn't upgraded. The paper states the risk directly: without visibility into these dependencies, the least-prepared participant or supplier may determine the pace of migration for everyone connected to the flow.

This is where the single-flow method earns its keep. Mapping one payment flow makes dependencies more visible and shows why procurement, third-party risk management, and network management must be part of the readiness programme. Those functions rarely sit inside the technology team, which is exactly the point. A cryptographic dependency buried in a vendor contract is a procurement fact before it's an engineering one.

The paper gives a useful way to sort what the trace turns up. Organisations need to distinguish between the changes they control, those that depend on vendors or payment participants, and those that cannot proceed until shared infrastructure is ready. Three buckets, three different management approaches. The first is a planning problem, the second a negotiation, and the third a waiting game where the right response is preparation.

A function-wide job, and a coordination job for operators #

The paper is blunt on ownership. Quantum-safe migration cannot be owned by the technology function alone. It cites a statement that quantum-safe readiness is not plug and play, meaning organisations can't simply buy an off-the-shelf solution and expect it to work.

The division of labour it describes is straightforward. Architecture and security teams need to understand the systems and cryptographic dependencies. Business and risk leaders need to assess the operational consequences, priorities, and investment required. Neither half can do the other's job. Engineers can say what a certificate chain touches but can't weigh the commercial cost of a delayed migration, and risk leaders can set priorities but can't see which of them rest on a protocol nobody has upgraded.

For a national payments infrastructure operator, the paper adds that migration is also a coordination challenge, because banks, payment providers, and vendors will have different capabilities and upgrade cycles. The operator can't wait for everyone to be ready, and it can't push everyone at the same speed. What it can do is make the transition legible, and the paper lists what that involves.

A dated roadmap should explain what each group needs to deliver, when testing and certification will be available, and how participants can migrate in stages. Common technical requirements should specify which cryptographic methods are permitted during the transition and when support for existing methods will end. The first stage should give participants a clear and achievable entry point, such as testing a defined connection or service. And where traditional and post-quantum methods are combined, or existing and upgraded systems operate alongside each other, the operator should explain how interoperability will be maintained and how problems will be managed.

Notice how much of that is about dates and boundaries rather than algorithms. When will testing be available? When does support for existing methods end? What's the smallest first step a participant can take? Those questions give a bank's own roadmap something to attach to. Participants can plan against dates and entry points, and they can't plan against a general intention to migrate.

What isn't settled, and why Asia-Pacific complicates it #

An honest account of this topic has to include the unresolved parts, and the paper includes them. Not every part of the migration has a settled answer. Some systems have a clearer route to post-quantum cryptography, while other environments may lack suitable implementations or depend on protocols that are still developing.

The paper's response isn't to wait. Organisations can still act by separating what can be changed now from what can only be prepared for. This is the same sorting logic as before, applied to maturity rather than control. Some work can be done today. Other work can only be readied, by knowing what's affected and what the dependencies are, so that when a route does exist the organisation isn't starting from zero.

Standards add another layer. Standards published by the US National Institute of Standards and Technology provide an important foundation, but organisations operating across the Asia-Pacific cannot assume that every market will adopt the same algorithms, requirements, or timetable. The paper then moves into hedged territory. Some jurisdictions may favour their own cryptographic standards or place different levels of reliance on standards developed elsewhere. Geopolitical considerations could reinforce those differences as post-quantum requirements develop.

I'd resist reading more into those hedged statements than they say. They don't predict a particular divergence. They warn against assuming convergence. For anyone running payments across several markets, that's a planning constraint: design for the possibility of difference.

That's where cryptographic agility takes on a wider meaning. For cross-border payments, the paper says it may mean more than preparing for future updates, as systems may also need to support different algorithms or standards across the markets in which they operate. Agility, in this reading, isn't only the ability to swap an algorithm later. It may be the ability to run different ones side by side, depending on where a payment goes.

Singapore's formal expectations and Hong Kong's 2030 target are a small illustration of why this matters. Two supervisors are moving, and the paper doesn't claim they're moving identically. A group operating in both has to keep two sets of expectations in view.

First steps a leadership team can take #

The paper closes its guidance with actions that follow from everything above. They're modest, and that's their strength.

First, appoint an accountable executive with enough authority to coordinate the work and bring decisions to the board. Second, use available tools to identify cryptography within a limited number of high-value systems rather than waiting for an enterprise-wide inventory. Third, ask critical vendors for their post-quantum roadmaps, expected support dates, testing arrangements, and dependencies. Fourth, for contracts approaching renewal, consider requirements for cryptographic agility, migration support, and evidence of compatibility with your systems.

The vendor and contract steps deserve attention from founders in particular, whether they're buying or selling. If you supply middleware, a managed service or a fraud platform to banks, expect to be asked for your roadmap, your support dates and your testing arrangements. Your customers have been told that their readiness may depend on what you've built into your products. If you're buying, a renewal is a rare point of use, and the paper suggests using it to secure agility, migration support and compatibility evidence while the contract is still open. Having those terms written down is worth far more than having to ask for them after a problem appears.

None of these steps require the inventory to be finished. Each one produces something: a named owner, a first set of findings, vendor answers, contract language. And each feeds the next round of questions, which is the knowledge-and-action loop the paper recommends.

The open question: does the timeline add up? #

The cleanest way to see the stakes is to return to the numbers. The HKMA expects the sector to achieve full readiness by 2030. Institutions that have transition plans report an average implementation timeframe of 5.6 years, while half of authorised institutions had no structured plan for cryptographic upgrades at all. The sector scored 2.3 out of 10. The paper doesn't say how those figures reconcile, and I won't pretend they do.

What they do suggest is where to look. If migration may move at the pace of the least-ready participant, then the sector's timeline depends less on its best-prepared banks than on its slowest links: the vendors, schemes and counterparties that sit inside every flow. The single-flow method is a way of finding out who those links are before the clock decides for you.

The question the paper leaves open is whether a first traced flow, repeated across the estate, can compress a 5.6-year average into a regulator's window. Whether the repeatable method scales faster than the dependencies it uncovers is something the next round of supervisory milestones should begin to answer. In Singapore, those milestones are already published.

The EPAA Quantum Safe Cryptography Working Group #

From Awareness to Action is published by the Emerging Payments Association Asia (EPAA) and was developed through its Quantum Safe Cryptography Working Group. The working group draws its members from IBM, KPMG, HSBC, PayPal, CBA, Idemia, Monash University, Australian Payments Plus, PayNet and Quantum Chain, among others. I'm one of them. The views in the paper are EPAA's own and don't necessarily represent those of individual working group members or their organisations.

The paper picks up where the working group's 2025 workshops left off. In those sessions, only 20% of participants said their senior stakeholders were very familiar with the quantum threat, while 44% said they were not very familiar or not familiar at all. The working group's earlier white paper, Quantum-Safe Payments: Why the Payments Industry Must Act Now, made the case for urgency. This one is about what to do first.

The full paper, with its appendix of government, regulatory, standards and industry guidance on post-quantum migration, is free to download: From Awareness to Action: What Quantum-Safe Readiness Requires Now.

Frequently Asked Questions #

What does the EPAA paper recommend as the first step towards quantum-safe readiness? Senior leadership should assign clear ownership and authorise a limited first assessment. The paper recommends appointing an accountable executive with sufficient authority to coordinate the work and bring decisions to the board. The first assessment then provides the evidence needed to set priorities, engage vendors and develop a credible roadmap.

Why not start with a complete cryptographic inventory? Trying to identify every cryptographic asset before making changes can leave organisations mapping indefinitely while the environment continues to change. An inventory is not a one-off deliverable; it develops as systems, vendors, standards and threats evolve. The paper's alternative is to build knowledge and action together, starting with a few important systems.

Why trace a single payment flow? Following one payment flow from initiation through clearing and settlement often exposes dependencies that are not visible from the payment application alone. The objective is not to select one payment rail and ignore the rest, but to create a repeatable method that can be expanded across the wider estate.

What did the HKMA's Quantum Preparedness Index find? Hong Kong's banking sector scored 2.3 out of 10. Half of authorised institutions had no structured plan for cryptographic upgrades, and half had not assessed whether technical infrastructure was ready for post-quantum security requirements. Among institutions with transition plans, the average implementation timeframe was 5.6 years. The HKMA expects the sector to achieve full readiness by 2030.

What should banks ask their vendors? Ask critical vendors for their post-quantum roadmaps, expected support dates, testing arrangements and dependencies. For contracts approaching renewal, consider requirements for cryptographic agility, migration support and evidence of compatibility with your systems.

References #

Last reviewed .

Syndicate this article

Format for Medium

# From Awareness to Action: What Quantum-Safe Readiness Requires Now

> Originally published at [https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/](https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/)

EPAA's quantum-safe readiness paper: name an accountable executive, trace one payment flow end to end, and let dependencies on vendors and counterparties set the plan.

Read the full article on sebastienrousseau.com: https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/

Format for Mastodon

From Awareness to Action: What Quantum-Safe Readiness Requires Now

EPAA's quantum-safe readiness paper: name an accountable executive, trace one payment flow end to end, and let dependencies on vendors and counterparties set the plan.

https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/

Copy formatted for LinkedIn

From Awareness to Action: What Quantum-Safe Readiness Requires Now

EPAA's quantum-safe readiness paper: name an accountable executive, trace one payment flow end to end, and let dependencies on vendors and counterparties set the plan.

Here are the key strategic takeaways:

- What the regulators and the index are saying. Start with the supervisors, because they've stopped treating this as a research topic.
- Accountability before architecture. The paper draws a pointed conclusion from the Hong Kong findings, and it frames it with a hedge.
- Why the exhaustive inventory stalls. A cryptographic inventory is a record of where and how cryptography is used across an organisation.
- Tracing a single payment flow. The paper gets concrete about where to begin: with a clearly defined payment flow or service, selected according to risk and practical feasibility.

What is your organisation's approach to the challenges outlined in this piece?

→ https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/

#QuantumSafeReadiness #PostQuantumCryptography #Epaa #EmergingPaymentsAssociationAsia #CryptographicInventory

Sebastien Rousseau | CC-BY-4.0
Cite this article

From Awareness to Action: What Quantum-Safe Readiness Requires Now

EPAA's quantum-safe readiness paper: name an accountable executive, trace one payment flow end to end, and let dependencies on vendors and counterparties set the plan.

BibTeX

@online{rousseau2026from,
  author  = {Rousseau, Sebastien},
  title   = {{From Awareness to Action: What Quantum-Safe Readiness Requires Now}},
  year    = {2026},
  url     = {https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/},
  urldate = {2026}
}

RIS

TY  - GEN
AU  - Rousseau, Sebastien
TI  - From Awareness to Action: What Quantum-Safe Readiness Requires Now
PY  - 2026
UR  - https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/
ER  -

Vancouver

Rousseau S. From Awareness to Action: What Quantum-Safe Readiness Requires Now. sebastienrousseau.com. 2026 Nov 16. Available from: https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/

Chicago

Rousseau, Sebastien. "From Awareness to Action: What Quantum-Safe Readiness Requires Now." sebastienrousseau.com. November 16, 2026. https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/.

APA

Rousseau, S. (2026, November 16). From Awareness to Action: What Quantum-Safe Readiness Requires Now. sebastienrousseau.com. https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/

Republish this article

From Awareness to Action: What Quantum-Safe Readiness Requires Now

EPAA's quantum-safe readiness paper: name an accountable executive, trace one payment flow end to end, and let dependencies on vendors and counterparties set the plan.

This article is licensed under Creative Commons Attribution 4.0 International. Republication requires attribution to the canonical URL.

From Awareness to Action: What Quantum-Safe Readiness Requires Now

EPAA's quantum-safe readiness paper: name an accountable executive, trace one payment flow end to end, and let dependencies on vendors and counterparties set the plan.

Originally published at https://sebastienrousseau.com/2026-11-16-quantum-safe-readiness-epaa/ by Sebastien Rousseau.
Licensed under CC-BY-4.0.