Inferensys

Glossary

Trusted Platform Module (TPM)

A Trusted Platform Module (TPM) is an international standard for a secure cryptoprocessor that provides hardware-based, tamper-resistant generation and storage of cryptographic keys, along with remote attestation capabilities.
Developer working on RAG retrieval system, document chunks visible on screen, technical workspace with code editor.
EMBEDDED SECURITY FOR TINYML

What is Trusted Platform Module (TPM)?

A foundational hardware security component for microcontroller and embedded systems, providing a cryptographically secure root of trust.

A Trusted Platform Module (TPM) is an international standard (ISO/IEC 11889) for a secure cryptoprocessor—a dedicated microcontroller or integrated circuit—that provides hardware-based, tamper-resistant generation, storage, and management of cryptographic keys, along with capabilities for remote attestation and integrity measurement. It establishes a hardware root of trust for the device, enabling secure boot, device identity, and data protection by performing cryptographic operations within its isolated, shielded environment.

In TinyML deployment, a TPM or its microcontroller-optimized equivalents (like a Secure Element) are critical for securing model inference, protecting intellectual property in compressed neural networks, and enabling secure over-the-air (SOTA) updates. It provides the foundation for firmware attestation, ensuring only authorized, unmodified code executes, and safeguards cryptographic keys used for authenticated encryption of sensor data or model outputs, directly addressing the physical attack surface of constrained edge devices.

HARDWARE ROOT OF TRUST

Core Functions of a TPM

A Trusted Platform Module (TPM) is a dedicated microcontroller that provides hardware-based, tamper-resistant security functions. Its core operations establish a chain of trust for the entire system.

01

Cryptographic Key Generation & Storage

The TPM's primary function is the secure generation and storage of cryptographic keys. It contains a True Random Number Generator (TRNG) to create high-entropy keys and hardware-protected storage (often volatile memory) that prevents key extraction. Keys can be designated as non-migratable, meaning they never leave the TPM's physical boundary, providing the highest assurance against software-based exfiltration. This is fundamental for operations like disk encryption (e.g., BitLocker) where the volume encryption key is sealed by the TPM.

02

Remote Attestation

Remote Attestation allows a device to cryptographically prove its software state to a remote verifier. The TPM securely records measurements (cryptographic hashes) of boot firmware, OS, and critical software into its Platform Configuration Registers (PCRs). When challenged, it can sign these PCR values with an Attestation Identity Key (AIK), providing a verifiable report. This enables a server to trust but verify that a connecting device (e.g., an IoT sensor) is running authentic, unmodified firmware before granting network access or sensitive data.

03

Sealing & Binding Data

These are two key operations that tie data security to the TPM and the system's state:

  • Sealing: Encrypts data so it can only be decrypted by the same TPM when the system is in a specific, trusted state (i.e., PCR values match). This is used to protect secrets until secure boot completes.
  • Binding: Encrypts data directly to a specific TPM's storage key. The data can only be decrypted by that TPM, but without the state-based restrictions of sealing. This is analogous to standard asymmetric encryption where the TPM's public key is used. These functions are critical for secure credential storage and digital rights management (DRM) on constrained devices.
04

Hardware-Based Cryptographic Operations

The TPM includes dedicated cryptographic engines to perform operations internally, keeping sensitive key material isolated from the main CPU and OS. Core supported operations include:

  • RSA signing/encryption and key generation.
  • Elliptic Curve Cryptography (ECC) for efficient, strong security on constrained devices.
  • SHA-1/SHA-256 hashing for measurement and integrity checks.
  • HMAC generation for message authentication.
  • Random number generation via its internal TRNG. By performing these operations in hardware, the TPM protects against software-based side-channel attacks and ensures operations are both secure and efficient, a key consideration for TinyML devices.
05

Integrity Measurement & Reporting

This function establishes the chain of trust during boot. Before executing any code, a Core Root of Trust for Measurement (CRTM), typically the initial boot code, measures itself into a TPM PCR. Each subsequent stage (bootloader, OS kernel) is measured (hashed) and the result is extended (a cryptographic operation) into a PCR before execution. The TPM securely stores these cumulative measurements. This process does not prevent execution of malicious code but creates an immutable audit log in hardware. The reporting function (via attestation) allows this log to be verified externally.

HARDWARE ROOT OF TRUST

Why TPMs are Critical for TinyML Security

In TinyML, where models and data operate on exposed, resource-constrained devices, a Trusted Platform Module (TPM) provides the immutable hardware foundation for a secure lifecycle.

A Trusted Platform Module (TPM) is an international standard (ISO/IEC 11889) for a secure cryptoprocessor that provides a hardware root of trust. For TinyML, it delivers tamper-resistant generation and storage of cryptographic keys, enabling secure boot, device identity, and remote attestation. This hardware isolation is essential as software-only security on a microcontroller is vulnerable to physical extraction and runtime attacks.

The TPM's remote attestation capability allows a TinyML device to cryptographically prove its firmware and model integrity to a cloud service before receiving sensitive data or updates. It anchors the chain of trust for Secure OTA updates, ensuring only authenticated model binaries are installed. This prevents model poisoning, intellectual property theft, and ensures the device's behavior remains verifiable and trustworthy in the field.

IMPLEMENTATION TYPES

TPM Form Factors and Implementations

A comparison of the primary hardware and firmware implementations of the Trusted Platform Module (TPM) standard, detailing their physical characteristics, integration methods, and typical use cases for embedded and TinyML systems.

Feature / CharacteristicDiscrete TPM (dTPM)Integrated TPM (iTPM)Firmware TPM (fTPM)

Physical Form Factor

Dedicated microcontroller chip (e.g., TPM 2.0 module)

Security block integrated into main SoC/CPU die

Firmware module executing in a protected environment (e.g., ARM TrustZone)

Hardware Isolation

Full physical separation from host CPU

Logical isolation on same silicon die

Logical isolation via processor security extensions

Tamper Resistance

High (dedicated tamper-resistant packaging)

Moderate (relies on SoC packaging)

Low (dependent on host CPU's security)

Root of Trust Location

Within the discrete TPM chip itself

Within the integrated security block of the SoC

Within the firmware and protected memory of the main CPU

Typical Use Case

High-security servers, industrial controllers, payment terminals

Modern laptops, premium IoT gateways, automotive ECUs

Consumer PCs, mobile devices, cost-sensitive embedded systems

Cryptographic Performance

Dedicated crypto accelerator, consistent

Shared SoC resources, variable

Relies on main CPU, subject to OS scheduling

Physical Attack Surface

Limited to TPM chip interfaces

Part of larger SoC attack surface

Tied to the main CPU's vulnerability profile

Cost & Board Space

Higher (additional component & PCB area)

Moderate (included in SoC cost)

Lowest (no additional hardware)

Standardization & Certification

Common Criteria certified modules available

Vendor-specific implementation of TPM spec

Implementation varies by CPU vendor and firmware

Suitability for TinyML

Possible but adds BOM cost and size

Ideal if available on the target MCU/SoC

Most common for Cortex-M based systems with TrustZone

TRUSTED PLATFORM MODULE (TPM)

Frequently Asked Questions

A Trusted Platform Module (TPM) is an international standard for a secure cryptoprocessor, typically a dedicated microcontroller, that provides hardware-based, tamper-resistant generation and storage of cryptographic keys, along with remote attestation capabilities. These FAQs address its role in securing TinyML and embedded systems.

A Trusted Platform Module (TPM) is a dedicated, tamper-resistant microcontroller that provides hardware-based security functions by creating and protecting cryptographic keys, generating cryptographically secure random numbers, and measuring system integrity. It works by establishing a hardware root of trust through a set of Platform Configuration Registers (PCRs) that store cryptographically hashed measurements of the system's boot process and software state. The TPM's secure internal memory stores Endorsement Keys (EKs) and Storage Root Keys (SRKs), which are never exposed outside the chip, enabling operations like remote attestation where the device can prove its software state has not been compromised.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.