All articles
    Cryptography· 16 May 2026· 7 min read

    Crypto agility: the prerequisite for any PQC migration

    Every credible post quantum cryptography programme runs into the same wall in month three: the systems being migrated were never designed to have their cryptography swapped out. Crypto agility is the engineering discipline that fixes this. It is also the single largest piece of work in a real PQC migration.

    What crypto agility actually means

    Crypto agility is the ability to change cryptographic algorithms, parameters and primitives across your estate with minimal code, configuration and downtime change. It is not the same as having a config file. It is a property of the system as a whole: protocol negotiation, certificate authorities, key management, libraries, vendor SDKs and operational tooling.

    Why it matters now

    NIST has standardised the first wave of post quantum algorithms (ML-KEM, ML-DSA, SLH-DSA) in FIPS 203, 204 and 205. It will standardise more. Some of today's choices will be tightened or deprecated within five to ten years as cryptanalysis matures. An organisation that needs a multi year programme to swap an algorithm is structurally exposed.

    Five engineering moves that build agility

    Crypto agility is unglamorous infrastructure work, but it pays back the day you need to migrate again.

    • Centralise cryptographic primitives behind a single internal library or service.
    • Adopt hybrid handshakes (classical + PQC) so rollback is always available.
    • Treat certificate authorities and HSMs as algorithm parameterised, not algorithm hard coded.
    • Add cryptography to your software bill of materials (SBOM) and vendor due diligence.
    • Bake algorithm rotation into chaos engineering and disaster recovery drills.

    Where it usually breaks

    The hardest layer is almost never your own application code. It is third party SaaS, embedded firmware, payment terminals, industrial control systems and document signing tooling. Build vendor PQC readiness into procurement now, even if you do not start the technical migration for another year.

    Frequently asked questions

    Is crypto agility the same as PQC migration?

    No. Crypto agility is the capability that makes PQC migration possible without a multi year rewrite, and that protects you against the next algorithm change after that.

    Can we wait for vendors to handle this?

    For some pure SaaS workloads, partially. For anything you operate, integrate or hold long lived data on, no. Vendor readiness is part of your responsibility, not a substitute for it.

    Want a tailored view for your organisation?

    Get in touch and qubion will match you with marketplace vendors who can map your quantum exposure, opportunities and a 12 to 36 month plan.

    Find a vendor

    Keep reading

    Cryptography

    Harvest now, decrypt later: what UK CISOs need to know

    Adversaries are capturing UK encrypted traffic now to decrypt once quantum arrives. The threat model, data most at risk, and a 12-month CISO plan.

    Cryptography

    Quantum safe encryption explained: a 2026 enterprise guide

    What quantum safe encryption actually is, the NIST standardised algorithms, how hybrid deployments work, and how UK enterprises should plan their migration.