1-minute read
What a defender needs to know
Microsoft’s October 8 post gives PKI owners a certificate-discovery task: its post-quantum TLS pilot is running in closed testbeds. The seven pilot roots added in August support interoperability tests with ML-DSA-87 certificates, which have no public trust. Keep those roots out of production trust stores and public websites.
The issuer, trust store, client application, TLS stack, inspection appliance, HSM and renewal process can each make assumptions about algorithms or chain size. Microsoft points to larger certificates and chains as possible pressure on handshake size, storage, transmission and inspection limits. On appropriately configured Windows 11 test systems, Microsoft identifies KB5101681 (28000.2608) for 26H1 and KB5101684 (26200.8973 or 26100.8973) for 25H2 as the starting updates for supported tests; verify Schannel and application prerequisites too.
Map issuers, trust anchors and validators for a representative application and a long-lived appliance. Ask the certificate provider about pilot access and build an isolated testbed. Check the installed Windows build against the pilot starting points for your supported version, and record which lab trust store contains the pilot root. Keep production trust stores unchanged.
Run the pilot chain through the real application and its inspection path. Record the certificate-validation result, handshake size, latency and renewal result next to a baseline test with the existing chain. A pass means the application completes a handshake, the renewal workflow succeeds and the pilot root stays inside the lab trust store. If the client rejects the chain or an intermediary fails, take that result to the responsible vendor before planning a rollout.