Quantum-safe banking, from card to core

Payments, card keys, interbank links and decades of customer records all rest on RSA and elliptic curves. We find every use of them across your bank, rank what to fix first and hand you a roadmap your supervisor can follow.

DORA has asked banks to keep cryptography in step with cryptanalysis
Since 2025 DORA has asked banks to keep cryptography in step with cryptanalysis
how often PCI DSS 4.0 wants your cipher suites and protocols reviewed
12 months how often PCI DSS 4.0 wants your cipher suites and protocols reviewed
EU date for moving high-risk use cases
End-2030 EU date for moving high-risk use cases

Why it matters now

The domed trading hall of a historic stock exchange, seen from the gallery
01

Records outlive the encryption

Account histories, credit files and contracts must stay confidential for a decade or more. Traffic copied today can be decrypted once a quantum computer exists.

02

Payments run on long-lived keys

EMV card certificates, HSM key hierarchies and SWIFT PKI rest on RSA and elliptic curves, and take years to roll over across a card base and a branch network.

03

Supervisors already ask

DORA wants cryptography updated as cryptanalysis develops, PCI DSS a yearly review of what you run, and the EU roadmap dates high-risk systems for 2030.

04

Your timeline is partly someone else’s

Card schemes, core-banking vendors, HSM makers, cloud providers and correspondent banks all have to move with you. Their readiness belongs in your plan.

Where the cryptography sits in a bank

Each card is a system we inventory. Its coloured edge shows how exposed its cryptography is.

CUSTOMERS AND CHANNELS YOUR DATA CENTRE COUNTERPARTIES Online and mobile banking TLS 1.3 · ECDHE · RSA Open-banking partners (PSD2) mTLS · QWAC · JWS ATMs and card terminals EMV RSA · TLS Branches and staff IPsec VPN · IKEv2 API gateway and web edge TLS · RSA/ECDSA X.509 Payment and card switch TLS · PIN 3DES/AES Identity and PKI Kerberos · PKI · LDAPS Core banking and mainframe TLS · PKI · AES HSMs and key management RSA/ECC · KEK/ZMK Data warehouse and archives AES-128/256 · TDE SWIFT and interbank SWIFT PKI · TLS Card schemes TLS · IPsec Cloud providers TLS · KMS HNDL HNDL HNDL
Public-key cryptography a quantum computer breaks Symmetric keys or legacy algorithms to check HNDLTraffic worth recording today to read later Illustrative, a typical estate rather than a client’s.

What you receive

  • A CBOM of the whole bank, in CycloneDX 1.7
  • Risk-ranked findings with HNDL flags
  • A tailored migration roadmap with dates and owners
  • Evidence for DORA and PCI DSS reviews, and for your supervisor
  • A readiness list for card schemes and for core-banking, HSM and cloud vendors

An actionable plan, not a list of intentions

Every action in the roadmap says what to change, why - the finding behind it - who owns it, how long it takes and in which quarter. Opened up, it adds the steps, what it waits on, how done is proven and which rule it serves.

Migration roadmap Banking · Q1–Q4 2027
Estimated completion
Q2 2029
Actions this year
12
Open work
41engineer-weeks
HNDL links still open
2
PreparationBaseline understandingPlanning and executionMonitoring and evaluation
Q1 2027 8 wk
A-01 Done

Name an accountable executive and adopt a cryptography policy

No owner for cryptographic change

CISO · 2 wk

A-02 In progress

Complete the CBOM across channels, payments, core and HSMs

31% of hosts not yet scanned

Platform team · 4 wk

A-03

Rank systems by how long their data must stay secret

Customer records kept 10+ years

Business owners · 2 wk

Q2 2027 11 wk
A-04 HNDL

Hybrid TLS on the online-banking edge

F-014 · ECDHE only on 14 internet endpoints

Network team · 6 wk

A-05

Retire TLS 1.0 and 1.1 on legacy endpoints

F-021 · 9 endpoints on old protocol versions

Platform team · 2 wk

A-06 Vendor

Get PQC dates from card schemes, core-banking and HSM vendors

11 suppliers without a published PQC plan

Procurement · 3 wk

Q3 2027 17 wk
A-07 HNDL

Move branch VPNs to hybrid IKEv2 with ML-KEM

F-009 · DH group 14 on 120 branch tunnels

Network team · 8 wk

A-08 Vendor

Upgrade payment HSM firmware for ML-DSA

F-030 · RSA-2048 key hierarchy

PKI team · 5 wk

A-09

Pilot ML-DSA certificates from the internal CA

Issuing CA signs with RSA-2048, 10-year validity

PKI team · 4 wk

Q4 2027 7 wk
A-10

Re-wrap archive keys and move data at rest to AES-256

F-041 · 128-bit keys on 25-year archives

Data platform · 4 wk

A-11

Re-scan and update the CBOM

Confirm the Q2–Q3 changes

CISO · 1 wk

A-12

Evidence pack for the DORA and PCI DSS reviews

Annual review of protocols in use

Compliance · 2 wk

A-04

Hybrid TLS on the online-banking edge

Network team · 6 engineer-weeks · Q2 2027

HNDL

Why

F-014 · 14 internet-facing endpoints negotiate ECDHE only. The sessions carry customer data kept for 10+ years, so traffic recorded today is the exposure (HNDL).

Steps

  1. Upgrade the load balancers to a release with ML-KEM
  2. Offer X25519MLKEM768 first, keep X25519 as the fallback
  3. Test the mobile app and partner clients in staging
  4. Roll out endpoint group by group, watching handshake errors
  5. Re-scan
Waits on
Load-balancer firmware with ML-KEM support
Done when
A re-scan shows hybrid key exchange on all 14 endpoints, and the CBOM is updated
Serves
DORA ICT-risk RTS, Art. 6 · EU roadmap, high-risk by 2030
Illustrative: actions, findings and figures are invented for this page, in the format the platform produces.

See your bank’s cryptography in one view