Hardware makers are adding post-quantum cryptography (PQC) to secure controllers, cryptographic accelerators and microcontroller platforms. The goal is to support functions such as secure boot, firmware-update verification, attestation and authentication with algorithms designed to resist attacks by future quantum computers. These product announcements show implementation paths, not proof of broad deployment or a cross-vendor performance advantage.
How are hardware makers implementing post-quantum cryptography?
There are three main approaches: place PQC in a dedicated root-of-trust controller, build support into an embedded controller, or provide acceleration and software libraries for microcontroller platforms. The right approach depends on where a product anchors trust and which cryptographic operations its firmware and update process need.
As an Amazon Associate I earn from qualifying purchases.
Dedicated root-of-trust controllers
In an announcement dated April 28, 2026, Microchip described its TS1800 as an external platform root-of-trust controller for secure boot, secure firmware updates, attestation and certificate handling. Microchip said the TS1800 includes hardware-accelerated ML-DSA, LMS signature verification and ML-KEM. These are manufacturer-described capabilities; the announcement is not independent validation of performance or deployment. Microchip’s TS1800 and TS50x announcement
Recommended Free Tools
Embedded controllers
On May 15, 2025, Microchip described its MEC175xB embedded controllers as having immutable PQC support, with configurable signature verification for secure boot and firmware updates. An embedded implementation can put verification close to the device’s startup and update path, but buyers still need to confirm supported algorithms, configuration options and lifecycle requirements for the specific product. Microchip’s MEC175xB announcement
#1 Best Overall
Accelerators and software libraries
STMicroelectronics described hardware cryptographic accelerators and associated software libraries for general-purpose and secure microcontrollers, targeting firmware updates, secure boot and authentication. The announcement does not identify a part number here, so a specific device should not be inferred. This model combines hardware and software support rather than making every PQC function a dedicated controller feature. STMicroelectronics’ PQC announcement
Which hardware needs to change for post-quantum cryptography?
Potentially more than the processor that runs an algorithm. NIST’s November 12, 2024 initial public draft, IR 8547, says cryptographic hardware modules such as hardware security modules (HSMs) and trusted platform modules (TPMs) may need upgrades or redesign. It notes that PQC can involve larger keys and greater computational demand, and calls out implementation optimization and side-channel protection. NIST’s exact statement is: “Hardware modules must be upgraded or redesigned to support PQC algorithms, which often have larger key sizes and require more computational resources.” This is draft guidance, not final transition policy. NIST IR 8547 initial public draft
Rank #2
The system around the cryptographic operation matters too. A device might verify a signature during boot, authenticate a firmware update, store keys in a secure module, or rely on certificates and protocols handled elsewhere. A new controller cannot, by itself, make every dependency in that chain PQC-capable.
Can PQC run in a secure boot controller?
Yes. Manufacturer announcements describe PQC support for secure-boot and firmware-update signature verification in embedded and root-of-trust controllers. The distinction to keep in mind is between a stated product capability and independently tested results: the announcements establish that manufacturers are building or offering these functions, but they do not establish comparative speed, power use, certification, or broad customer deployment.
It also helps to distinguish the algorithms involved. NIST published three principal PQC standards on August 13, 2024: ML-KEM for key establishment, and ML-DSA and SLH-DSA for digital signatures. Secure boot and update verification commonly concern signatures; ML-KEM is not an encryption or signature algorithm. NIST’s post-quantum cryptography standards
What should you compare when choosing a PQC-ready hardware platform?
Start with the device’s role and migration needs rather than the phrase “PQC-ready.” NIST’s National Cybersecurity Center of Excellence (NCCoE) frames migration as identifying where vulnerable public-key cryptography is used across hardware, software and services, then managing risk and prioritizing changes. Its work also covers interoperability and benchmarking. NIST NCCoE migration project
Rank #4
- Algorithm coverage: Ask which standardized algorithms are implemented and whether hybrid operation is supported where your migration plan requires it.
- Implementation location: Determine whether operations run in hardware, firmware/software libraries, or a combination. Check where keys and trust anchors reside.
- Security integration: Confirm support for the product’s actual needs, such as boot verification, update signatures, attestation, authentication, and certificate or key handling.
- Resource and side-channel evidence: Request memory, compute, bandwidth and power measurements for your workload, along with details of side-channel protections. Compare only results obtained under sufficiently similar conditions; the sources here do not establish a vendor speed or power ranking.
- Interoperability and migration: Check how the platform fits existing protocols, provisioning, certificate infrastructure and update systems, and what can be changed later through a crypto-agile migration path.
- Validation status: Ask what testing or validation applies to the exact part and configuration. Marketing language alone does not establish a particular certification.
Why inventory comes before a hardware swap
A PQC migration reaches beyond hardware. The NCCoE’s approach emphasizes cryptographic visibility across systems and services so organizations can identify vulnerable public-key use and dependencies before prioritizing replacements or redesigns. For a device maker, that means tracing where algorithms are used in boot, updates, authentication, key storage and connected services. The inventory helps determine whether a controller can be updated, a module must be replaced, or a protocol or service must change as well.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
