EXA20
— Migrate off legacy crypto —
Certificate Migration
Move signing keys to post-quantum algorithms one at a time, with the audit trail preserved.
The problem to solve
NIST has finalised the post-quantum standards (FIPS 203/204), CNSA 2.0 puts national-security systems on a 2035 PQC deadline, and UK NCSC + EU regulators have started laying out migration runways for critical infrastructure. The migration involves regenerating every certificate, re-issuing through every CA, updating every server, and testing every integration. For most organisations this is a multi-year programme — and the project becomes worthless if any audit trail breaks across the migration.
The solution it enables
Polymonial lets you import each existing key and migrate key by key. The previous signature stays valid through the transition, and each move carries an audit-trail record.
What it looks like
An organisation has 10,000 TLS certificates across 200 servers. NIST FIPS 203/204 + CNSA 2.0 + NCSC guidance put RSA and EC on a multi-year migration runway. Today that means: generate new key pairs, obtain new certificates, update every server, test every integration, coordinate a rollout window. With Polymonial: each key moves on its own schedule, with an audit-trail record of each move. The migration becomes a programmatic rollout, scheduled at the operator's pace.
“Each key moves on its own schedule. The audit trail survives the algorithm change.”
Who’s this for you?
We have this problem.
Your organisation needs this for its own data, product or programme of work.
We deliver this for clients.
A consultancy, integrator, service provider, industry programme or technology vendor.