Certificate management and PQC readiness
An operational PKI you can actually reason about: inventory, automated issuance and renewal, short lifetimes, and building the crypto-agility that a post-quantum transition will demand.
What to implement
Build a complete certificate inventory, automate issuance and renewal (ACME) to eliminate expiry outages, shorten lifetimes, protect CA and signing keys in HSMs, and design for crypto-agility now so you can add post-quantum and hybrid certificates without re-architecting. Expiry outages and unknown certificates are the everyday failures; PQC is the reason agility is no longer optional.
Most PKI incidents are mundane: an expired certificate takes down a service because no one knew it existed. Fixing the operational basics (inventory, automation, ownership) is the prerequisite for the harder task ahead, which is migrating the whole certificate estate to post-quantum algorithms as the NIST standards roll out.
Get the operational basics right first
- Inventory every certificate: public and internal, on load balancers, services, devices, and code-signing systems. Use certificate discovery / CT-log monitoring; unknown certs are the leading cause of expiry outages.
- Automate issuance and renewal with ACME wherever possible; manual renewal is the root cause of most outages.
- Assign an owner and an expiry alert to every certificate, well ahead of expiry.
- Shorten lifetimes. The ecosystem is moving toward much shorter maximum validity, which is only survivable with automation, so automate first.
- Protect private keys: CA roots/intermediates and signing keys belong in HSMs; never in a repo or on a shared drive.
- Maintain revocation (CRL/OCSP) and test it.
Short lifetimes without automation is a self-inflicted outage
Cutting certificate validity while still renewing by hand just multiplies the number of expiry incidents. Automate renewal (ACME) before you shorten lifetimes, not after.
Why PKI is a post-quantum priority
PKI relies on RSA and elliptic-curve cryptography, both broken by a sufficiently large quantum computer via Shor's algorithm. Certificates that authenticate long-lived systems, and especially anything protecting long-lived confidentiality, must move to post-quantum signatures. NIST has standardized ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) for signatures.
Design for crypto-agility now
The organizations that migrate to PQC easily are the ones whose certificate estate is already inventoried, automated, and abstracted behind agile issuance. Build that today (even before you issue a single PQC certificate) so the eventual algorithm swap is a configuration change, not a re-architecture. Plan for hybrid certificates (classical + PQC) during the transition for backward compatibility.
The PQC-readiness track
- Use the certificate inventory to build a cryptographic bill of materials (CBOM): which algorithms and key sizes are in use where.
- Prioritize by data/asset lifetime and exposure: long-lived roots and anything protecting harvest-now-decrypt-later data first.
- Pilot hybrid/PQC certificates in test environments; validate interoperability and performance (larger keys and signatures have real size/latency impact).
- Ensure your CA, HSMs, and clients support the new algorithms before committing production.
- Track vendor and library PQC support as a dependency in your roadmap.
PKI health and readiness evidence
Maintain: a discovered-vs-known certificate count (target: no unknowns), automated-renewal coverage percentage, expiry-caused incident count trending to zero, HSM protection confirmation for all CA/signing keys, and a CBOM showing current algorithms with a prioritized PQC migration order.