India · Cryptography Migration
Crypto Migration in India — From Classical to Post-Quantum
Cryptography migration in India is how banks, NBFCs, fintech platforms, and custody operators move from classical encryption and signing to quantum-resistant algorithms. It is not a single cutover — it is a sequenced program: inventory (CBOM), prioritize risk, hybrid staging, then production waves aligned with RBI Q-SAFE and NPCI timelines.
What does a crypto migration program include?
| Stage | Activity | Deliverable |
|---|---|---|
| Discover | CBOM inventory, readiness assessment | Crypto exposure map, risk matrix |
| Prioritize | HNDL scoring, payment-rail dependencies | Migration wave plan |
| Stage | Hybrid ML-KEM-768 pilots in sandbox | Staging proof, vendor scorecards |
| Deploy | Production cutover by system priority | PQC-enabled TLS, HSM paths, on-prem if required |
Which classical algorithms must Indian banks migrate first?
Priority targets: RSA < 2048, ECDH/ECC on external TLS, SHA-1 and MD5 in signing chains, TLS < 1.2, and weak cipher suites on payment APIs. Long-retention encrypted archives face harvest-now-decrypt-later risk even before quantum computers reach operational scale.
How does VajraShield run crypto migration in India?
VajraShield sells one migration program in three stages on IBM Cloud India: assisted CBOM and readiness, live PQC APIs (ML-KEM-768 / ML-DSA) in a native Rust core, and Vajra Box on-prem when sovereignty requires keys on the customer's rack. Same codebase from sandbox to enterprise — no rewrite.
What is the 90-day crypto migration starter?
See the detailed PQC migration roadmap for India (2026–2033) for phased timelines. A practical 90-day starter:
- Days 1–30: deepen CBOM for top 10 critical systems
- Days 30–60: ML-KEM-768 sandbox encrypt/sign proof
- Days 60–90: risk committee readout + 2028 production wave proposal