Post-Quantum Cryptography (PQC) & CBOM: The Indian CISO's IDRBT Migration Roadmap & HNDL Defense

🇮🇳 Indian Banking & Financial Security Directive: IDRBT Post-Quantum Cryptography Roadmap & CBOM Blueprint

In 2024, the US National Institute of Standards and Technology (NIST) finalized the primary standards for Post-Quantum Cryptography (PQC): FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA). For Indian financial institutions regulated by the Reserve Bank of India (RBI) and guided by the Institute for Development and Research in Banking Technology (IDRBT), quantum readiness is no longer an academic exercise—it is a mandatory operational imperative.

1. The Existential Threat: "Harvest Now, Decrypt Later" (HNDL)

Many enterprise executives assume that because commercially viable quantum computers capable of running Shor's algorithm (Cryptanalytically Relevant Quantum Computers, or CRQCs) may not arrive until 2029–2032, post-quantum planning can be deferred. This assumption overlooks the active, global adversary tactic known as Harvest Now, Decrypt Later (HNDL):

# Threat Actor Kill Chain: Harvest Now, Decrypt Later (HNDL)

1. Adversary intercepts encrypted TLS / VPN / SSH traffic crossing sovereign transit nodes.

2. Exfiltrated ciphertext (trade secrets, biometric data, UPI keys, SWIFT/SFMS archives) is stored in cold storage.

3. In 2029+, adversary executes Shor's Algorithm on a 4,000+ logical qubit quantum system:

→ Breaks RSA-2048 in ~8 hours; breaks ECC-256 (secp256r1) in ~2 hours.

4. Retroactive decryption reveals historic sovereign intelligence and proprietary intellectual property.

2. The IDRBT 3-Phase Quantum Migration Blueprint

The IDRBT paper "Quantum Safe Cryptography for Banking and Financial Sector" establishes a phased transition model for Indian financial rails (SFMS, RTGS, NEFT, and NPCI UPI):

Phase	Timeline	Primary Objective	Key Deliverables & Artifacts
Phase 1: Discovery	Immediate (Months 1–12)	Automated inventory of all cryptographic algorithms, keys, and certificates.	Machine-Readable CBOM, Certificate Discovery Map, HSM Audit Dossier.
Phase 2: Hybrid Mode	2026 – 2028	Deploy hybrid classical-quantum schemes (dual-encryption) across edge perimeters.	Dual-handshake TLS 1.3 (X25519 + ML-KEM-768), PQC VPN tunnels, updated API proxies.
Phase 3: Full PQC	2029 – 2030	Complete retirement of RSA, DSA, and ECC across all core banking software.	Pure ML-KEM, ML-DSA, and SLH-DSA production verification; Attestation certificates.

3. What is a CBOM (Cryptography Bill of Materials)?

Traditional Software Bills of Materials (SBOMs) catalog open-source libraries and licenses (e.g. log4j:2.14.1). However, an SBOM cannot answer critical cryptographic questions: Where is the 1024-bit RSA private key stored? Which TLS ciphers are negotiated by our payment API? Is our AES implementation using insecure ECB mode?

A CBOM (Cryptography Bill of Materials) is a specialized, structured inventory that maps:

Cryptographic Algorithms: Specific ciphers (e.g. RSA-2048, AES-256-GCM, SHA-256) and mode of operation.
Asset Locations: Source code line numbers, compiled binary routines, TLS termination configs, and HSM hardware keys.
Key Lifecycles: Key lengths, issuance dates, expiration timestamps, and rotation schedules.
Quantum Vulnerability Rating: Clear classification of each asset as Quantum Vulnerable (Breakable by Shor's), Slightly Impacted (Grover's half-strength), or Quantum-Resistant.

4. NIST Standardized PQC Algorithms: The Core Replacement Matrix

FIPS 203: ML-KEM

Module-Lattice Key Encapsulation

Formerly CRYSTALS-Kyber. The primary global standard for general key exchange and TLS handshakes. Delivers high performance and small ciphertext sizes.

Replaces: RSA Key Exchange, Diffie-Hellman, ECDH

FIPS 204: ML-DSA

Module-Lattice Digital Signatures

Formerly CRYSTALS-Dilithium. The primary standard for digital signatures across certificates, code signing, document signing, and identity tokens.

Replaces: RSA Signatures, DSA, ECDSA, Ed25519

FIPS 205: SLH-DSA

Stateless Hash-Based Signatures

Formerly SPHINCS+. Built entirely on secure hash functions (SHA-2/SHAKE). Serves as the backup signature standard if lattice assumptions face theoretical breakthroughs.

Use Case: Firmware Signing & Long-Term PKI Roots

5. Good News: Symmetric Encryption & AES-256

Shor's algorithm breaks asymmetric cryptography (RSA and ECC). However, symmetric cryptography (AES) and cryptographic hash functions (SHA-2, SHA-3) are only subject to Grover's algorithm, which provides a quadratic speedup (effectively halving the key length). Therefore:

AES-128 is reduced to 64-bit effective security (computationally vulnerable to quantum brute force).
AES-256 is reduced to 128-bit effective security (remains fully quantum-safe and practically unbreakable).

✓ Immediate Action: Standardize on AES-256-GCM for all databases, block storage, and S3 buckets across your AWS Mumbai and Azure India workloads.