Skip to content

Crypto agility in hardware, why programmable beats fixed silicon

If cryptographic algorithms are committed to fixed silicon, every standards revision becomes a board respin and a new qualification cycle. In programmable hardware the same revision is a firmware update to a card that is already deployed and already qualified.

The two ways to build it

Fixed function. The algorithm is implemented directly in silicon. Fastest, smallest, most power-efficient, and correct for an algorithm that is not going to change — AES is a reasonable candidate.

Programmable. The algorithm runs on reconfigurable hardware or a specialised processor. Some efficiency is traded for the ability to change what it computes after manufacture.

Why the trade looks different now

Fixed function is the right answer when an algorithm is stable. Post-quantum algorithms are not yet stable in the relevant sense: FIPS 203, 204 and 205 are final, and parameter sets can be revised, national schemes will diverge, hybrid constructions will change, and cryptanalysis continues.

Committing to fixed silicon is a bet that nothing changes for the life of the device. For a device with a ten-year deployment, that is a long bet on a young standard.

What a respin actually costs

Not just the silicon. New hardware means requalification, recertification of the module, a new evaluation for any FIPS or Common Criteria claim, updated documentation, a customer upgrade programme, and inventory to manage across two versions.

A firmware update to a programmable device means new firmware, a delta assessment against the existing evaluation, and a distribution mechanism you already have. The difference is not incremental.

Where the efficiency argument lands

Fixed function is genuinely faster and lower power, and for a high-volume constrained device that can be decisive. The honest position is that this is a real trade rather than a one-sided argument.

What tilts it is deployment life and change probability. A short-lived, cost-dominated, high-volume device favours fixed function. A long-lived appliance in a regulated estate during a standards transition favours programmability, and by a wide margin.

Where this leads

To hardware that executes cryptography as a workload rather than as a fixed circuit — which is what the acceleration pillar is about, and why agility and acceleration turn out to be the same design decision viewed from two directions.