6. Post-Quantum Cryptography (PQC)¶
A large enough quantum computer would be able to break the public-key algorithms used in certificates today, such as RSA and ECDSA. Post-quantum algorithms are designed to resist that. NIST has published the first standards:
ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) - digital signature algorithms, the kind used for certificate keys.
ML-KEM (FIPS 203) - a key encapsulation mechanism, used to agree on encryption keys.
TrustView has the groundwork in place for post-quantum certificates:
It shows whether each certificate it monitors has a post-quantum key - see Post-quantum status of certificates.
It can generate ML-DSA keys and CSRs when ordering certificates - see Ordering certificates with ML-DSA keys.
It lets you control which key types each issuer may be used with - see Allowed key types per issuer in Settings.
Note
Whether you can actually get a post-quantum certificate depends on the issuer. Support for post-quantum certificates among certificate authorities, browsers, servers and other software is still at an early stage, and it varies. Check with your issuer, and test with the systems that will use the certificate, before relying on it.
6.1. Post-quantum status of certificates¶
The certificate details of a certificate - for example on an SSL certificate’s page, and in the certificate history of
Other certificates - include a Post quantum line. It shows either The certificate is Post Quantum Ready or
The certificate is not Post Quantum Ready.
The status is based on the algorithm of the certificate’s own public key. It says nothing about the algorithm the issuing CA used to sign the certificate, or about the rest of the certificate chain.
For a post-quantum key, the public key information also names the algorithm, its NIST security level and the key size,
for example ML-DSA-65 NIST Level 3 (1952 bytes). TrustView recognises:
Algorithm |
Standard |
Variants |
|---|---|---|
ML-DSA |
FIPS 204 |
ML-DSA-44, ML-DSA-65, ML-DSA-87, and the pre-hash variants (HashML-DSA) |
SLH-DSA |
FIPS 205 |
All SHA2 and SHAKE variants, and the pre-hash variants (HashSLH-DSA) |
ML-KEM |
FIPS 203 |
ML-KEM-512, ML-KEM-768, ML-KEM-1024 |
Keys from before the standards were final are also recognised, and are marked (pre-standard). This covers draft versions of
ML-DSA (Dilithium) and an ML-DSA-65 + RSA-3072 composite key. Pre-standard keys do not work with software that implements the
final standards, so certificates with them should be replaced.
A post-quantum algorithm that TrustView does not know yet - for example one standardised later - is still recognised as
post-quantum, and shown as Unrecognised post-quantum together with its OID.
6.2. Ordering certificates with ML-DSA keys¶
TrustView can generate ML-DSA key pairs and CSRs, in three sizes:
Key type |
NIST security level |
Notes |
|---|---|---|
|
2 |
Smallest keys and signatures |
|
3 |
A common middle ground |
|
5 |
Highest security level, largest keys and signatures |
ML-DSA keys and signatures are much larger than RSA and ECDSA ones. A certificate with an ML-DSA key can only be used where the software on both sides supports it.
The ML-DSA key types are offered wherever a key type is chosen - when ordering a certificate, and in Automation tasks - but only for issuers that allow them. TrustView never assumes that an issuer signs ML-DSA:
For a certificate authority or ADCS template, ML-DSA becomes available when the issuer reports that it supports it.
For an ACME endpoint (including custom ACME issuers) or the Manual issuer, which report nothing, ML-DSA must be enabled by an administrator.
See Allowed key types per issuer for how this is set up.
Note
In an Automation task, the key container must also be able to hold an ML-DSA key. A key generated by TrustView, or an externally supplied CSR, can be ML-DSA. Azure Key Vault and Citrix NetScaler do not support ML-DSA keys, so ML-DSA is not offered with those key containers.
If you provide your own CSR with an ML-DSA key, the same rule applies: the issuer must allow ML-DSA, or the order is rejected.
6.3. Getting ready¶
Even before post-quantum certificates are widely available, TrustView can help you prepare:
Know your certificates - use TrustView’s discovery and monitoring to get a complete overview of the certificates in use, their key types and their issuers. The
Post quantumline shows which ones already have a post-quantum key.Automate - certificates that are renewed through automation can be moved to a new key type or issuer centrally, instead of one by one.
Control key types - use Allowed key types per issuer to decide which key types may be used, and with which issuers.