The Lock Is Welded Shut

NIST standardized post-quantum cryptographic algorithms in August 2024 (FIPS 203, 204, 205), but enterprise migration faces a systems-engineering bottleneck that Gartner estimates will exceed Y2K in complexity. Most enterprise systems embed cryptographic algorithms directly into business logic, firmware, and hardware without abstraction layers, making algorithm substitution impossibly expensive. 75% of deployed OpenSSH instances cannot support PQC algorithms. IoT devices, medical equipment, and industrial controllers have RSA hard-coded into hardware without update capability. The hybrid transition approach (running classical + PQC simultaneously) creates "zombie algorithms" — RSA and ECC that are cryptographically obsolete yet operationally alive, requiring continued maintenance throughout a migration estimated at 12–15 years for large enterprises.

The "harvest now, decrypt later" threat means nation-state adversaries are already archiving encrypted traffic for future quantum decryption, making this a present-tense data security problem. Only 5% of organizations have formal quantum-transition plans. PQC key sizes are 25–40× larger than classical equivalents (Kyber public key ~800 bytes vs. ECC ~32 bytes), creating bandwidth and storage issues in constrained environments like IoT and vehicle-to-vehicle communication. The longer migration takes, the larger the archive of harvestable data grows.

NIST's PQC standards provide the algorithms but not the migration pathway. Cryptographic inventory tools can catalog where algorithms are used, but 41% of organizations haven't even begun this process. Hybrid key encapsulation (using both classical and PQC algorithms together) protects data but doubles computational overhead and requires application-layer changes. Crypto-agility — designing systems with swappable algorithm modules — is the long-term solution but requires refactoring code that was never designed for it. 68% of organizations report difficulty finding PQC implementation skills. Hardware security modules (HSMs) are being updated by vendors, but the timeline for firmware updates across the installed base is years, not months.

Automated cryptographic inventory and migration tools that can scan enterprise codebases, firmware images, and network traffic to identify all cryptographic dependencies, then generate migration plans with dependency ordering and risk prioritization. Crypto-agility middleware that can intercept cryptographic calls and route them to either classical or PQC implementations without application changes — analogous to TLS's cipher suite negotiation but applied to application-layer cryptography. For constrained environments (IoT, embedded), lightweight PQC implementations that can fit within existing memory and bandwidth constraints. The migration tooling gap is the bottleneck, not the cryptographic algorithms.

A team could select a specific open-source application or protocol implementation, perform a complete cryptographic inventory, identify all hard-coded algorithm dependencies, and design a migration strategy including effort estimation and risk assessment. Alternatively, a team could prototype a crypto-agility wrapper that transparently routes cryptographic operations between classical and PQC implementations. Computer science, cybersecurity, and software engineering skills would be most relevant.