Regulators Hand Banks a Quantum Deadline and a Crypto Inventory Checklist

Archi4 min read

cryptographyregulationquantumbanks

Contents
  1. The New Deadline Is a Paper Trail
  2. What the Rules Ask For
  3. Who Moves First and Why
  4. The Failure That Examiners Expect
  5. What Enforcement Will Look Like
  6. The Practical Start

The New Deadline Is a Paper Trail#

Regulators in the United States, Europe, and Asia are moving cryptography from an IT audit footnote to a board-level risk item. They are not predicting a quantum computer next year. They are telling banks, insurers, and payment firms to prove which algorithms protect which data, and how they will change them.

The shift appears in guidance from the European Banking Authority, statements from the Bank of England's Prudential Regulation Authority, and exercises run by the Monetary Authority of Singapore. In the US, the Federal Reserve, the OCC, and the FDIC treat cryptographic weakness as an operational risk, not a vendor problem.

What the Rules Ask For#

The common thread is three requirements: an inventory, a risk assessment, and a migration plan.

The inventory must cover every algorithm, key length, certificate, and hardware security module the institution touches. That includes TLS certificates on public websites, keys inside payment terminals, code-signing keys for mobile apps, and old HMAC secrets in batch files that nobody has opened since 2019.

The risk assessment asks a time-based question. A transaction record cleared in 30 days needs different protection than a pension record that must stay confidential for 40 years. The phrase "harvest now, decrypt later" appears in supervisor notes because an attacker can capture encrypted traffic today and decrypt it after a quantum capability exists.

The migration plan must name a target algorithm, usually ML-KEM (FIPS 203) for key agreement and ML-DSA (FIPS 204) for signatures, and assign a sequence to systems by the confidentiality period of the data they handle.

Who Moves First and Why#

The European Union is the furthest along because DORA, the Digital Operational Resilience Act, has applied since January 2025. It requires financial entities to test their resilience to ICT incidents and report them. Quantum migration is not named in the law, but the European Banking Authority's guidelines treat crypto-agility as part of sound ICT risk management.

The Bank of England's Prudential Regulation Authority has raised quantum risk inside its operational resilience work. The Monetary Authority of Singapore has run key replacement exercises with major banks.

The US picture is split. NIST sets standards but does not regulate banks. The Treasury and the banking agencies have focused on digital asset risks, while the Securities and Exchange Commission's disclosure rules force public companies to describe material cybersecurity risks. A bank that cannot say when it will replace RSA-2048 has a disclosure problem.

National security rules point the same way. The NSA's CNSA 2.0 timeline requires software to migrate by 2030 and hardware by 2033 for systems that handle classified data. Banks that serve government agencies or defense contractors inherit those dates.

The Failure That Examiners Expect#

The first problem is not cryptography. It is the inventory. Most institutions have thousands of cryptographic assets, and many are undocumented. Branches closed, vendors changed, and acquiring another bank adds certificates, APIs, and hardware that nobody reclassified.

Examiners probe three soft spots. The first is shadow cryptography: encryption inside business applications that the security team never reviewed. The second is legacy hardware with firmware that cannot run ML-KEM without a physical upgrade. The third is third-party code. A payment processor's SDK or a card network's certification schedule can dictate a bank's timeline more than NIST can.

Regulators have made clear that a vendor's failure does not move a bank's compliance date. The contract, not the optimism, is what counts.

What Enforcement Will Look Like#

No regulator has proposed a fine for using RSA-2048. The enforcement angle runs through operational resilience rules, DORA's incident reporting, and the SEC's disclosure regime.

Consider the sequence. A bank that cannot migrate before a data exposure becomes reportable under DORA must describe the incident and its root cause. A public company that faces a harvest-now-decrypt-later exposure must state the risk in its annual filing if the risk is material. The penalties are less dramatic than a fine for an unsafe algorithm and more practical: higher capital costs, supervisory attention, and public reporting.

The most direct tool is the exam finding. Supervisors can require remediation plans, restrict business lines, or demand external reviews. The deadline is not a date on a calendar. It is the next examination cycle.

The Practical Start#

An institution that wants to stay ahead can act without waiting for an exam. Appoint a single owner for the cryptographic inventory. Build a spreadsheet, or buy a tool, but make it complete. Include every TLS endpoint, every HSM, and every signature key. Add a column that reflects the data's confidentiality period, not the certificate's validity.

Then label each asset by migration priority. Systems that protect data for longer than 20 years, or that connect to government networks with CNSA 2.0 dates, go first. Internal analytics with short-lived data can wait.

The standards exist. FIPS 203 and 204 are final, and major TLS libraries ship implementations. The cost is not research. It is counting, deciding, and paying for replacements.

Regulators will not announce a global switch-off date. They will ask for the inventory, compare it to the firm's claims, and measure progress in the next cycle. That is the deadline that matters.

More articles