Company · Blog

Your first TPM 2.0: where to start

A practical path for teams adding hardware-backed security for the first time, from choosing a TPM to shipping it, often driven by the Cyber Resilience Act (CRA).

Many device makers are adding hardware-backed security for the first time, often because of the EU Cyber Resilience Act (CRA). TPM 2.0 is a strong choice: it is an open standard, it is made by many vendors, and it covers identity, protected storage and secure updates in one component.

Here is a practical path from no hardware security to a working TPM 2.0.

1. Decide what you need to protect

Start from the risks, not the chip:

  • Device identity. Only genuine devices should connect to your network, cloud or services. See Strong Identity.
  • Critical data. Certificates, configuration, serial numbers and root secrets must not be read, changed or rolled back. Anti-rollback counters block older, vulnerable firmware, which supports CRA requirements. See Secure Storage.
  • Physical actions. Motors, radios and tamper switches can be controlled by TPM policy instead of software. See Secure GPIO.
  • Keeping the TPM current. TPM firmware needs patches for the whole product life. See TPM Updater.

2. Choose your TPM 2.0

You have two options:

  • Firmware TPM (fTPM). Some processors include a TPM 2.0 in firmware, so there is no extra chip. Its protection relies on the security of the host platform. Check your processor documentation.
  • Discrete TPM. A dedicated, certified chip from vendors such as Infineon, Nuvoton, STMicroelectronics and SEALSQ, connected over SPI or I²C. It is required for Secure GPIO and for TPM firmware updates with TPM Updater.

Strong Identity and Secure Storage work with either.

3. Integrate without becoming TPM experts

This is where most first projects slow down: TPM software stacks, key hierarchies and authorization policies. EnactTrust is ready-to-use software that removes that work. It ships as a statically built binary with integration code for your platform, needs no TPM software stack, and runs on everything from bare-metal and RTOS microcontrollers to Linux systems.

If you are designing in your first TPM, our support packages can include help choosing the chip and reviewing your hardware design.

Talk to us

Planning your first TPM 2.0 design? Book a free discovery call with one of our TPM engineers.

Talk to a TPM engineer, not a sales deck

Book a working session - we'll map the fastest path to automatic TPM updates on your platform in 45 minutes.

Expert-led demo