Rows of server rack cabinets with networking cables in a data centre

Cryptographic Debt: Paying It Down on the Road to PQC

Every large organisation runs cryptography that someone chose years ago, for reasons nobody wrote down, in places nobody fully mapped. Some of it has since been deprecated. Some is hard-coded into applications and devices never designed to change algorithm. Most of it works, so nobody touches it. That accumulated gap is what we mean by cryptographic debt.

Algorithms used to be retired one at a time, and even then the debt took decades to clear. The post-quantum transition replaces every public-key algorithm at once. NIST’s final NIST IR 8547 (October 2026) notes that the journey from standardisation to full integration “can take 10 to 20 years”, and puts quantum-vulnerable public-key algorithms on a path to deprecation after 2030 and disallowance after 2035.

This article looks at what cryptographic debt is in practice, why post-quantum cryptography (PQC) turns it into a deadline, and how the Enterprise Cryptographic Exposure Management (ECEM) model gives a structure for paying it down without running it up again.

What Cryptographic Debt Looks Like

“Cryptographic debt” is an industry term, not one defined by a standards body. NIST, the NCSC and CISA describe the problem without using the phrase. A plain definition: cryptographic debt is the cryptography an organisation still depends on that it would not choose today, plus the cost of not knowing where it is or how hard it will be to replace.

It has three parts: the weak or deprecated cryptography itself, the missing record of where it lives, and the rigidity of algorithms fixed in code, firmware or long-lived certificates. The UK NCSC’s PQC migration timelines guidance points to the same problem: “particularly in older systems, cryptographic services have evolved over many years in sometimes haphazard ways,” which makes both discovery and mitigation harder.

Past transitions show how long the debt lingers:

  • Triple DES. AES was standardised in 2001, yet NIST’s CSWP 39 on crypto agility (December 2025, updated June 2026) records that Triple DES “continued to be used in many applications until it was finally disallowed in 2024,” and that “the complete transition from Triple DES to AES took 23 years.” SP 800-131A Rev. 2 had set three-key TDEA encryption as disallowed after 2023.
  • SHA-1. A serious collision attack was announced in 2005, and in 2006 NIST urged federal agencies to stop relying on SHA-1 digital signatures by the end of 2010. In December 2022 NIST announced it will transition away from SHA-1 for all applications by 31 December 2030.
  • RSA key sizes. CSWP 39 notes the minimum RSA modulus for signatures rose from 1024 bits in 2000 to 2048 bits in 2013. Under SP 800-131A Rev. 2, RSA signature generation below 2048 bits is disallowed, and keys of 1024 to 2047 bits are allowed only for verifying existing signatures as legacy use. A device not designed to move to a larger key size during its lifetime, CSWP 39 says, “will need to be replaced.”

None of these were surprises. The debt persisted because organisations could not find every instance, or could not change the ones they found.

Why PQC Turns the Debt Into a Deadline

Previous transitions replaced one algorithm at a time. CSWP 39 says this one “will be much larger in scale than previous transitions because all public-key algorithms will need to be replaced rather than just a single algorithm.” NIST IR 8547 lists RSA, ECDSA, EdDSA and finite field and elliptic curve Diffie-Hellman as quantum-vulnerable, all deprecated after 2030 and disallowed after 2035 at 112 bits of classical security strength and above (128 bits for EdDSA).

The UK timetable is similar. The NCSC expects organisations to complete discovery and an initial migration plan by 2028, carry out their highest-priority migrations by 2031, and complete migration by 2035. It also warns that “those who do not migrate in a timely way will end up running significant legacy estates.” Missing the dates leaves the quantum risk open and creates the next generation of cryptographic debt at the same time.

If Triple DES took 23 years, a full public-key replacement on a ten-year clock leaves no room for a first phase spent rediscovering the estate. NIST IR 8547 reaches the same conclusion: treat PQC migration as a current operational priority, “beginning with cryptographic inventories, migration planning, and early deployments of PQC-enabled products and services.”

Some of the debt is already accruing interest. Data intercepted today can be stored and decrypted later, the “harvest now, decrypt later” threat covered in understanding post-quantum threats. And CSWP 39 adds that “this PQC transition will certainly not be the last transition required.” Swapping RSA for ML-KEM by hard-coding the new algorithm in the same places refinances the debt rather than clearing it.

The ECEM Model in Brief

Enterprise Cryptographic Exposure Management is the model Quantum Sentinel builds its platform around. Its ECEM whitepaper defines it as “the discipline of discovering, understanding, and reducing cryptographic exposure – the business risk created by unknown, weak, outdated, or quantum-vulnerable cryptography across an organisation.” “Unknown, weak, outdated, or quantum-vulnerable” is a fair description of what most organisations owe.

The model runs as a cycle of six stages: Discover cryptographic assets across endpoints, servers, applications, databases, PKI, HSMs, cloud environments and source code repositories; Inventory them in a living Enterprise CBOM; Assess exposure using business context and guidance including NIST and CNSA 2.0; Prioritise remediation where it most reduces exposure; Transition to post-quantum cryptography with a phased roadmap; and Monitor posture as the environment changes.

For debt, the important line in the whitepaper is this: “exposure changes as infrastructure changes, so ECEM is a standing capability, not a one-time audit.” A one-off inventory project gives the balance on one day. A standing capability shows whether the balance is going up or down. (Selection criteria for platforms are covered in our guide on choosing a cryptographic exposure management platform.)

Using the Lifecycle to Pay Down Cryptographic Debt

Discover and inventory: establish what you owe

No finance team would restructure a loan book without a list of the loans. The cryptographic equivalent is a CBOM, which we covered in building the inventory. To work as a debt register rather than a snapshot, it has to be readable by others and has to track change over time.

The platform’s CBOM page states that its CBOM exports as CycloneDX 1.7 JSON, and that each entry carries a fingerprint so “a rescan updates the existing entry rather than adding a duplicate, which is what makes first seen and last seen timestamps meaningful.” CycloneDX 1.7, released by the OWASP Foundation on 21 October 2025, expanded the standard’s CBOM capabilities. An open format means an auditor or regulator can read the register without the tool that produced it.

Assess and prioritise: find the debt that charges interest

A SHA-1 hash in an internal checksum tool and RSA key exchange on a link carrying decades-old customer records are both findings. Only one is urgent. NIST IR 8547 says systems that protect data with long-term confidentiality needs “warrant the earliest transitions.”

Its PQC migration planning page describes how the platform makes that distinction: each finding gets a migration priority and a named replacement algorithm, harvest-now-decrypt-later exposure is “recorded as its own field per finding,” and the score is weighted by asset criticality, environment and external exposure. A daily sweep also raises priorities as the 2030 deadline approaches.

Transition: repay in the right order

The NCSC lists the options for each system: migrate in place, re-platform, retire the service, run it to end of life, or tolerate the risk. That choice is a business decision. The vendor is open about where its role ends: it “does not hold your migration plan,” with “no waves, no target dates, no task owners.” It supplies prioritised evidence and raises tickets in Jira, ServiceNow ITSM and BMC Helix ITSM. The plan stays with your programme, and our article on planning your PQC migration journey covers how to build it.

Stopping New Debt: Monitoring, Drift and Crypto Agility

Paying down debt achieves little if new debt arrives at the same rate. In cryptography it arrives quietly: a server rebuilt from an old template, a load balancer profile changed during an incident, a new application that pins an algorithm in code.

The platform’s automated discovery page describes a “crypto drift event,” recorded when a rescan finds an entry has got worse: “a weaker algorithm, a lower TLS version, a changed cipher suite, a smaller key, or a higher quantum risk score, with the old and new values kept side by side.” Alert rules can send drift and policy violations to Slack, Teams, email or a SIEM over syslog. The same page states the limits: drift is recorded for degradation only, and scanning is scheduled rather than real-time.

Policy closes the other door. The migration planning page says a crypto policy can ban named algorithms, TLS versions and cipher suites, set minimum key sizes and require post-quantum cryptography. The posture monitoring page describes a Quantum Readiness Score tracked over time, so progress can be reported to leadership as a trend.

Monitoring catches debt after it appears. Crypto agility stops it forming. NIST CSWP 39 defines crypto agility as “the capabilities needed to replace and adapt cryptographic algorithms in protocols, applications, software, hardware, firmware, and infrastructures while preserving security and ongoing operations.” Its strategic plan is a repeating loop of governance, inventory, tool gap analysis, a prioritised asset list and implementation, with a policy-informed engine that will “continuously measure, monitor, and report on the state of cryptography within the enterprise.” The NCSC likewise advises choosing solutions that offer cryptographic agility.

The practical rule: migrate every system to PQC in a way that lets the algorithm change again without a rebuild. Otherwise 2035 arrives with a fresh layer of debt already in place.

Lining the Lifecycle Up With NCSC and NIST Milestones

The ECEM stages map onto the published milestones without much forcing:

  • By 2028 (NCSC): define goals, complete discovery and build an initial plan. This is Discover, Inventory, Assess and Prioritise. The NCSC asks organisations to record the data they hold “including its expected lifetime and its value to an adversary”, the input that separates urgent debt from tolerable debt.
  • After 2030 (NIST IR 8547): quantum-vulnerable public-key algorithms are deprecated, which means the data owner must examine the risk and decide whether to keep using them. A current inventory is the only way to know which systems that decision covers.
  • By 2031 (NCSC): carry out the highest-priority migrations and refine the plan into a full roadmap. This is Transition for the top of the queue.
  • By 2035 (NCSC and NIST IR 8547): migration complete in the UK timeline, with the algorithms disallowed under NIST standards after 2035. Proving nothing quantum-vulnerable remains is a job for Monitor.

The NCSC also asks for metrics: “you should be able to quantify how many of your software clients are using PQC, and be able to identify those that are not.” That means seeing post-quantum cryptography already deployed, not only legacy algorithms. Its CBOM page says the network discovery identifies hybrid key exchange such as X25519MLKEM768 by completing a real handshake, and its migration planning page lists a NIST IR 8547 transition assessment among its reports.

What Tooling Will Not Clear on Its Own

An ECEM platform shortens the slowest part of the problem, which is finding the debt. It does not settle the account by itself.

  • Some cryptography is invisible to scanners. CISA’s strategy for automated cryptography discovery and inventory tools warns that embedded cryptography in software packages, customised applications and certain operating systems “may not be discoverable using automated tools”. Quantum Sentinel states it does not inspect operating system packages, language dependencies or SBOMs. Supplier questionnaires and contract clauses still matter.
  • Decisions stay with people. The platform has no risk-acceptance workflow, by its own account, so formal exceptions with expiry dates belong in your governance process.
  • Verification is a separate step. The NCSC advises checking that systems use PQC cipher suites “and not falling back to traditional cryptography.” Post-migration verification is not tracked in the platform either, so the migration plan needs its own verification step.
  • Some legacy cannot move. The NCSC notes some legacy systems “are not capable of being transitioned to support PQC.” That debt is cleared by replacement, isolation or retirement, and the inventory’s job is to make sure each one is counted and owned.

How Sinevis Can Help

Sinevis helps organisations turn cryptographic debt into a scheduled programme. Our post-quantum cyber readiness service follows the same arc as the model above: discover assets and the cryptography protecting them, assess and prioritise quantum-vulnerable risk, build the cryptographic inventory and CBOM, develop the remediation plan and policies, implement post-quantum cryptography and crypto agility, and monitor the result.

For discovery and inventory at enterprise scale we use Quantum Sentinel, one of our technology partners. Where scanners cannot see, such as cryptography embedded in supplier products, we work through the supplier and architecture questions with your teams and fold the answers into the same roadmap, aligned to the NCSC 2028, 2031 and 2035 milestones.

For a quick external view, try our free PQC compliance check for websites. To discuss a cryptographic debt assessment for your organisation, contact the Sinevis team.