How should banks prioritise post-quantum cryptography work?

Why This Matters for Security Teams

Post-quantum cryptography is not a single migration project. For banks, it is a sequencing problem: protect the data and trust flows that must remain confidential or verifiable long after today’s algorithms weaken. That includes customer records with long retention periods, signing services, key exchange on external interfaces, and the identity systems that authenticate machines and services. The practical risk is that quantum exposure arrives unevenly, so some controls need to move long before full ecosystem support exists.

Current guidance suggests treating cryptographic agility as a governance issue, not just a technology refresh. The NIST post-quantum transition work and PCI DSS v4.0 both reinforce the need to identify where cryptography is used and how quickly it can be replaced. That aligns with broader non-human identity risk: the Ultimate Guide to NHIs from NHI Mgmt Group shows how often service accounts, API keys, and other machine identities remain exposed or over-privileged for far too long. In practice, many security teams discover weak crypto dependencies only after a system inventory is needed for an incident, audit, or major platform change, rather than through intentional planning.

How It Works in Practice

The strongest prioritisation method is to rank crypto dependencies by business impact and replacement difficulty. Banks should start with external trust paths, then move inward to internal workloads, archives, and legacy integrations. The goal is to reduce quantum exposure where retroactive repair will be hardest.

A practical sequence usually looks like this:

• Map all cryptographic dependencies, including TLS, VPN, signing, code integrity, HSM workflows, and machine-to-machine authentication.
• Classify data by confidentiality lifespan. Information that must stay secret for years or decades moves first.
• Prioritise externally exposed APIs and partner links, because those are hardest to coordinate once a transition starts.
• Review identity and signing systems for banks, especially service accounts, certificate authorities, and automated key issuance.
• Introduce cryptographic agility so algorithms can be swapped without redesigning the whole platform.

For implementation detail, security teams should rely on standards that separate inventory from migration. NIST’s post-quantum transition guidance, alongside implementation resources such as CISA quantum readiness resources, supports phased planning rather than a hard cutover. At the same time, the NHI angle matters because machine identities are often the hidden dependency behind certificates, tokens, and signing keys. The Ultimate Guide to NHIs notes that many organisations still lack full visibility into their service accounts, which makes crypto discovery incomplete from the start.

Where possible, banks should separate “must be quantum-safe soon” from “can remain on legacy crypto during controlled sunset.” That distinction helps avoid wasting effort on low-retention, low-exposure systems while critical trust anchors remain unchanged. These controls tend to break down in large banks with fragmented ownership, because application, infrastructure, and identity teams often maintain different inventories and no single system of record exists.

Common Variations and Edge Cases

Tighter prioritisation often increases coordination overhead, requiring banks to balance fast risk reduction against migration complexity. That tradeoff is most visible in legacy core banking platforms, card ecosystems, and vendor-managed services where algorithm replacement depends on third parties.

There is no universal standard for exact migration order yet, but current guidance suggests a few consistent exceptions. Short-lived data with low regulatory sensitivity may not justify early replacement, while long-retention records, signing roots, and cross-border trust channels usually do. Banks also need to distinguish between “crypto at rest” and “crypto in motion” because transport protections, document signatures, and identity assertions fail in different ways under quantum risk.

Another edge case is dependency drift. A system may look low priority on paper but still support higher-value workflows through hidden API calls, embedded certificates, or shared service identities. That is why crypto inventory should be linked to machine identity governance, not treated as a one-time architecture review. In practice, the hardest cases are multi-vendor payment and identity stacks where no single team owns the whole trust chain.

Related resources from NHI Mgmt Group

• When should security teams prioritise post-quantum readiness work?
• How should security teams prioritise NHI remediation in cloud environments?
• Should organisations prioritise external exposure or internal credential governance first?
• How should organisations prepare IAM for post-quantum cryptography?