Singapore just gave its banks a quantum deadline. The interesting part is what it left out

On 6 November 2026, the Monetary Authority of Singapore published Consultation Paper P019-2026, a proposed Circular that tells every financial institution in the country when it should be quantum-safe. The dates are clear. The plan deadline is 31 December 2027. Critical systems follow by 31 December 2030. Everything else is done by 31 December 2034. The consultation closes on 23 November, so the industry has barely two weeks to respond.

I read the paper the way I read most regulator documents now: looking for the gap between what it demands and what it actually enforces. This one has a real gap, and it is worth talking about, because Singapore is one of the first regulators to put calendar dates on a quantum migration, and other regulators will copy the shape of this document even if they change the dates.

What MAS actually asks for

The proposed Circular sets five expectations. A financial institution should have governance and accountability for the migration, a cryptographic asset inventory, a board-approved migration plan, tested implementation, and progress tracking with interim checkpoints and quantitative targets.

The timelines are tiered. The biggest players go first. Critical Information Infrastructure Owners, Domestic Systemically Important Banks, and NETS are expected to submit their migration plans to MAS by 30 June 2027. Critical Information Infrastructure Owners should finish migrating their critical infrastructure systems by 31 December 2029. Everyone else gets until the end of 2027 for a plan, the end of 2030 for critical systems, and the end of 2034 for the rest.

A critical system, in the paper's definition, is one whose failure would cause significant disruption to a firm's operations or materially affect its service to customers. That is a wide definition on purpose. A payments switch qualifies. So does the system that holds customer records for the next thirty years, which matters more than it sounds, for a reason I will come back to.

The paper builds on an advisory MAS issued in February 2024 about quantum-related cybersecurity risks. That advisory warned. This paper schedules.

The part that is missing

Here is the honest part. The proposed Circular is not legally binding. MAS says so itself. It is to be read as supplementary to existing Notices and Guidelines, including the Notice on Technology Risk Management and the Notice on Cyber Hygiene. It creates no penalty of its own. Institutions that run into technical or operational hurdles are expected to record the reasons for any deviation and put interim controls in place.

The paper also names no algorithm, no key size, and no protocol profile. It does not mention hybrid cryptography by name. It does not mention cryptographic agility. It does not mention harvest-now-decrypt-later. It does not refer to NIST's post-quantum standards, FIPS 203, 204, and 205, by name at all.

Instead, the technical work is delegated to a different document: the Cyber Security Agency of Singapore's Quantum-Safe Migration Handbook, version 1, published 16 July 2026, along with the CSA's Quantum Readiness Index. The handbook is described as informational. So the Circular sets the dates, and a non-mandatory handbook holds the technical guidance, and neither document by itself forces a bank to pick a specific algorithm.

I am not saying this makes the paper useless. A regulator that names dates changes budgets. A bank that has to produce a board-approved plan by the end of 2027 will hire people and buy tooling in 2026, because that is how planning cycles work. But there is a difference between a deadline and a standard, and this paper is a deadline without a standard. If a bank migrates its critical systems to something that turns out to be the wrong choice, the Circular gives it no cover and no correction, because it never specified the choice.

How it compares to what came before

Two comparisons put this in context.

The first is NIST. On 27 October 2026, NIST published the final version of IR 8547, its transition plan for post-quantum cryptography. That document deprecates every quantum-vulnerable public-key algorithm after 2030 and disallows them after 2035. Under Executive Order 14412, US federal high value assets and high impact systems must use post-quantum key establishment by 31 December 2030 and post-quantum signatures by 31 December 2031. The NIST dates and the MAS dates line up closely on purpose. Both end up at 2030 for the critical work. The difference is that NIST also names the algorithms, ML-KEM for key establishment and ML-DSA for signatures, and MAS does not.

The second comparison is Hong Kong. The Hong Kong Monetary Authority published a post-quantum toolkit for banks earlier this month. A toolkit tells you how. A Circular tells you when. MAS chose when. The HKMA chose how. A bank operating in both cities now has both halves of the picture, which is probably the point. Regulators talk to each other, and the Asian financial centres are converging on the same message from different directions: start now, finish the critical systems by 2030.

The inventory is the real work

Of the five expectations, one matters more than the other four combined: the cryptographic asset inventory.

You cannot migrate what you cannot find. A bank that has been running for decades has RSA and elliptic curve cryptography in places nobody remembers. It is in TLS configurations, in database encryption, in signed firmware on ATMs, in the VPN that connects two branches, in a library a vendor shipped inside a product ten years ago and never updated, in backups that were encrypted with a key nobody can rotate without restoring the backup first.

I know this from a much smaller system. I build an end-to-end encrypted messenger with its own post-quantum protocol, and even at that scale the inventory is the hard part. The key exchange is one line of code. Finding every place a key is generated, stored, rotated, backed up, or logged is the actual job. The first time I listed every place my app touched a key, I found two I had forgotten. Multiply that by a bank with forty years of systems and you understand why MAS put the inventory second on its list and why the plan deadline is a full year away.

This is also why the 2034 date matters less than it looks. The systems that hold data with a long shelf life are the ones at risk today, not in 2034. An attacker can record encrypted traffic now and decrypt it later, once a capable quantum computer exists. Financial records, health records, and legal documents are kept for decades. A payment record encrypted with RSA today and stored by an adversary is a payment record exposed in ten years. MAS does not use the phrase harvest-now-decrypt-later in this paper, but the 2030 deadline for critical systems is the answer to it: migrate the long-lived data first, because the clock on that data started years ago.

What I would do with this paper if I ran a bank's migration

I do not run a bank. But I have done a migration of a live system to post-quantum key exchange, and the shape of the work is the same at any scale. If I were reading P019-2026 as an engineer instead of a commentator, here is what I would take from it.

First, build the inventory before arguing about algorithms. The inventory decides the plan. A team that starts by picking ML-KEM-768 versus ML-KEM-1024 before it knows where its RSA lives will pick wrong, because the constraint is never the algorithm, it is the oldest system in the fleet.

Second, go hybrid. Pair ML-KEM with X25519 for key establishment, the way browsers and TLS deployments already do. Hybrid means a break in the new lattice algorithm falls back to the classical algorithm you already trust, and a quantum computer breaks the classical half but not the lattice half. It is the only migration strategy that does not ask you to bet the bank on a single new primitive. The IETF published new hybrid cipher suites for Messaging Layer Security on 1 November 2026, and the same pattern applies to TLS. MAS does not require hybrid, which is a gap in the paper, but nothing in it forbids it either.

Third, treat the plan as a living document, not a deliverable. MAS says the timelines may be revised as threats and standards evolve. That is the regulator telling you the dates will move. A board-approved plan that cannot be revised is a plan that will be wrong. Build the migration so the algorithm can be swapped, because it will need to be. Cryptographic agility is not a feature. It is the whole point of doing this migration instead of the last one.

Fourth, submit a comment before 23 November if you are affected. This is a consultation, not a finished rule. The window is short, and the final Circular will be shaped by who shows up. The questions MAS is actually asking are whether the expectations are comprehensive enough and whether the timelines are realistic. If you run systems that cannot meet 2030, the time to say so is now, with reasons, not in 2029.

What to watch next

The consultation closes on 23 November 2026. After that, MAS will publish a final Circular, and the dates in it may shift. Watch three things: whether the final version names ML-KEM and ML-DSA, whether it makes the CSA handbook mandatory instead of informational, and whether it adds any requirement for independent assurance that the migration actually happened. The current paper asks for none of these. If the final version adds even one, it becomes a much stronger document.

The bigger pattern is the one to keep an eye on. NIST set the global dates in October. Hong Kong gave banks a toolkit. Singapore gave them a calendar. Australia's ASD, the US NSA, and CISA updated their joint vendor-readiness guidance in the same week. The regulators are no longer debating whether the migration happens. They are debating the paperwork around it. The engineering is now the easy part. The inventory, the budget, and the board meeting are the hard part, and the deadline for those is 2027, not 2034.

If you build anything that encrypts data someone else will want to read in ten years, that deadline is yours too, whether or not a regulator has sent you a letter yet.

Sources: MAS Consultation Paper P019-2026 (6 November 2026); CSA Quantum-Safe Migration Handbook v1 (16 July 2026); NIST IR 8547 final (27 October 2026); HKMA post-quantum toolkit for banks (November 2026).