EnactTrust can use any TPM 2.0: the one already on your board, the firmware TPM inside your processor, or the chip you add next. It runs on everything from bare-metal and RTOS microcontrollers to Linux systems.
TPM 2.0 used to be the hard choice. EnactTrust makes it the easy one.
A discrete chip on your board, a firmware TPM built into your processor, or one you're adding.
A statically built binary plus ready-to-use integration code. It runs on your device's main processor and talks to the TPM.
Link it into your bare-metal, RTOS or Linux build. No TPM software stack, the smallest footprint possible.
Already shipping a TPM, replacing a secure element or adding hardware security for the first time.
Put the TPM you already pay for to work: automatic updates, device identity, secure storage and secure GPIO.
See the productsAn open standard from many vendors, so you are not tied to one chip, without the TPM complexity.
Why TPM 2.0Start your Cyber Resilience Act (CRA) work with TPM 2.0. Your processor may already include a firmware TPM.
Where to startFour products, delivered as firmware components or software for your system.
EnactTrust eliminates all vendor-specific steps and TPM chip updates run in a single step, with version-control visibility across your fleet.
A hardware-locked identity for every device. It can't be copied, cloned or stolen, so only genuine devices get in.
Tamper-resistant storage inside the chip for the data that matters most. Protected, lockable and rollback-proof.
Hardware switches that follow TPM policy, not software. Sensitive functions stay physically disabled until the TPM's conditions are met.
TPM 2.0 ships in devices across these industries. Wherever your fleet runs, EnactTrust keeps its TPMs current.
Already shipping a TPM 2.0 or planning your first design? In a free discovery call we'll map the fastest path to TPM 2.0 security on your platform.
Book a free discovery call