Are You Ready to Witness the Future of Data Security?
Platform
Resources
©2026 QuNu Labs Private Limited, All Rights Reserved.

Executive Summary:
- Most organisations cannot name every cryptographic algorithm running across their infrastructure.
- NIST's Cryptographic Agility guidance (CSWP 39, December 2025) identifies this inventory gap as the primary barrier to quantum migration.
- Without a complete cryptographic inventory, post-quantum readiness is not a programme. It is theatre.
A cryptographic inventory is a systematic, organisation-wide catalogue of every cryptographic algorithm, protocol, certificate, and key in active use — across all systems, applications, and infrastructure. It answers one deceptively simple question: what encryption does your organisation actually rely on?
The urgency is quantum computing. Shor's algorithm, running on a cryptographically relevant quantum computer, can break RSA and elliptic curve cryptography (ECC) — the two algorithms protecting the vast majority of enterprise data today. NIST has published replacement standards: FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA). But organisations cannot migrate to these standards without first knowing precisely what they are migrating from.
Cryptographic algorithms are embedded invisibly throughout enterprise infrastructure. They exist in TLS configurations, digital signatures on software updates, PKI certificates issued years ago, SSH keys for infrastructure access, VPN tunnels, database encryption layers, and hundreds of third-party libraries — each potentially using a different algorithm, version, or key size.
Over decades, organisations accumulated cryptographic dependencies organically, without systematic tracking. A 2024 IBM study estimated that the average large enterprise has cryptographic dependencies across more than 1,000 distinct systems. Fewer than 5% have a complete, current cryptographic inventory. This is not negligence. It is the consequence of a decades-long assumption that current algorithms were computationally unbreakable. That assumption no longer holds.
The cryptographic estate you cannot see is the cryptographic estate you cannot protect.
NIST CSWP 39 (December 2025) identifies cryptographic inventory as the foundational capability for achieving crypto-agility — the ability to rapidly replace cryptographic algorithms in response to new threats or standards changes. Without a complete inventory, an organisation cannot achieve crypto-agility, cannot migrate systematically, and cannot demonstrate compliance to auditors, regulators, or board-level risk functions.
The guidance identifies four asset categories requiring inventory: cryptographic algorithms in use (including key sizes and modes), cryptographic keys and their lifecycle status, certificates (expiry dates, issuing authorities, associated systems), and cryptographic dependencies in software libraries and third-party components.
Source: NIST CSWP 39 — Cryptographic Agility Guidance (December 2025)
A standard security audit assesses compliance against existing controls. A cryptographic inventory specifically maps algorithm-level exposure: every system using RSA-2048, every certificate expiring within a critical window, every TLS configuration permitting quantum-vulnerable cipher suites, and every software dependency relying on a cryptographic library not updated for post-quantum standards.
Deloitte's Cryptographic Resilience Profile (April 2025) identifies the cryptographic inventory as the single highest-value activity organisations can complete before beginning PQC migration. Organisations that skip this step routinely discover critical dependencies mid-migration — at the worst possible time.
→ Deloitte Cryptographic Resilience Profile (April 2025)
The highest-priority category is data with long confidentiality requirements — financial records, national security communications, healthcare records, and legal documents that must remain confidential for decades. These are the assets most exposed to harvest-now-decrypt-later (HNDL) attacks, in which encrypted data collected today is stored for future quantum decryption. Data collected in 2025 that must remain confidential until 2040 is already at risk under current adversary collection programmes.
The second priority is authentication infrastructure — PKI certificates, digital signatures, and identity verification systems. These underpin trust in everything from software distribution to financial authorisation. Migration here requires careful sequencing to avoid operational disruption.
In the US, NIST IR 8547 (November 2024) establishes deprecation timelines: RSA and ECC to be deprecated by 2030 for most applications, no later than 2035 for all. In the EU, NIS2 and DORA require demonstrable cryptographic resilience for critical infrastructure and financial entities. In India, the DPDP Act's 'reasonable security safeguards' standard creates implicit obligations: an organisation that encrypts personal data using an algorithm known to be quantum-vulnerable, and which has not undertaken an inventory to understand its exposure, faces a difficult position before the Data Protection Board if a breach occurs.
The answer 'we had not assessed our cryptographic estate' is not defensible in a post-NIST, post-DPDP environment. The inventory is a governance obligation.
A structured programme operates across four phases. Discovery identifies all cryptographic assets across infrastructure, applications, and third-party dependencies — typically combining automated scanning tools with manual review of legacy systems. Classification assigns each asset to a risk tier based on data sensitivity and algorithm exposure. Prioritisation sequences migration based on risk tier, system criticality, and migration complexity. Remediation executes migration to NIST-approved PQC algorithms in priority order, with ongoing monitoring to prevent the reintroduction of quantum-vulnerable dependencies.
The World Economic Forum's Quantum Readiness Toolkit (2024) and Singapore's CSA Quantum Safe Handbook (October 2025) provide two of the most operationally detailed public frameworks for cryptographic inventory methodology currently available.
Source:
→ Singapore CSA Quantum Safe Handbook (October 2025)
→ QNu Labs: Being Crypto-Agile in a Quantum World
For a large enterprise with complex legacy infrastructure, a comprehensive cryptographic inventory typically requires three to six months. The timeline depends on the breadth of legacy systems, the availability of automated scanning tools, and the quality of existing IT asset management records. A prioritised partial inventory — covering the highest-risk systems first — can yield actionable output within four to six weeks and is the recommended starting point for organisations under time pressure from regulatory or board-level deadlines.
Automated discovery tools can identify the majority of cryptographic dependencies in modern infrastructure — TLS configurations, certificate databases, and software library dependencies are well-suited to automated scanning. Legacy systems, bespoke applications, and operational technology (OT) environments often require manual review. NIST CSWP 39 recommends a combined automated and manual approach. The most reliable inventories treat automation as the discovery mechanism and manual review as the validation and gap-closing mechanism.
FIPS 140-3 certifies specific cryptographic module implementations. A cryptographic inventory is a broader exercise cataloguing all cryptographic dependencies across an organisation, regardless of certification status. The inventory identifies which FIPS-validated modules require upgrading to support post-quantum algorithms, and which existing deployments will need re-evaluation as PQC algorithm standards are incorporated into the FIPS programme. Inventory is the prerequisite for informed FIPS transition planning.
PQC replaces mathematically vulnerable algorithms with quantum-resistant alternatives at the software layer. QKD uses quantum physics to distribute encryption keys in a way immune to both classical and quantum eavesdropping. A comprehensive migration strategy may incorporate both: PQC for algorithm-layer protection across general enterprise infrastructure, and QKD for the highest-sensitivity communications where unconditional security is required. The cryptographic inventory identifies which systems and data categories require which level of protection.