Glossary

Device Identifier Composition Engine (DICE)

A hardware security standard that layers boot state measurements into a compound device identifier, enabling secure key derivation and attestation without requiring a full TPM.

Get in touch Learn more

Modern WeWork hardware lab area with product team collaborating around AI device prototypes, 3D printer in background, dramatic industrial lighting with product sketches on glass walls.

HARDWARE ROOT OF TRUST

What is Device Identifier Composition Engine (DICE)?

A hardware security standard that layers boot state measurements into a compound device identifier, enabling secure key derivation and attestation without requiring a full TPM.

The Device Identifier Composition Engine (DICE) is a hardware security standard that cryptographically combines a device's unique immutable secret with measurements of each successive layer of boot firmware and software. This layered hashing process generates a Compound Device Identifier (CDI), which uniquely represents the device's identity and its precise software state at any given moment.

Unlike a traditional Trusted Platform Module (TPM), DICE operates without dedicated security silicon, instead embedding the root of trust directly into the boot sequence. This enables lightweight remote attestation and secure key derivation for constrained IoT devices, ensuring that any unauthorized modification to the boot chain automatically produces a different cryptographic identity, thereby preventing access to sealed secrets.

HARDWARE-ROOTED IDENTITY

Key Features of DICE

The Device Identifier Composition Engine (DICE) establishes a cryptographically verifiable identity rooted in immutable hardware, enabling layered attestation without the cost or complexity of a discrete TPM.

Layered Boot Attestation

DICE creates a compound device identifier (CDI) by chaining measurements from each stage of the boot sequence. If any firmware or software component is modified, the derived CDI changes cryptographically.

First mutable code measures the next layer before execution
Each layer receives a unique identity secret based on the previous layer's measurement
A compromised bootloader automatically results in a different cryptographic identity
Enables remote verifiers to detect tampering by validating the CDI against a known-good value

Unique Device Secret (UDS)

The UDS is a statistically unique, non-extractable entropy value fused into the silicon during manufacturing. It serves as the root of trust for all subsequent key derivation.

Injected via physical unclonable function (PUF) or factory provisioning
Never directly accessible to firmware or software
Combined with the first mutable code measurement to derive the CDI
Provides hardware-bound identity without requiring stored keys in non-volatile memory

Symmetric Key Derivation Architecture

DICE uses HMAC-based key derivation functions (HKDF) to generate cryptographic keys deterministically from the CDI. This eliminates the need for key storage and enables on-demand key generation.

Keys are derived, not stored — they exist only when needed
Different keys for different purposes: attestation, sealing, identification
Forward secrecy is inherent: a compromised layer cannot derive keys for previous layers
Compatible with NIST SP 800-108 key derivation standards

TPM-Free Attestation

DICE provides hardware-rooted attestation without requiring a discrete Trusted Platform Module. This makes it ideal for cost-constrained, power-sensitive, and space-limited embedded devices.

Implements attestation in firmware using existing hardware capabilities
Reduces bill of materials (BOM) cost by eliminating dedicated security chips
Suitable for microcontrollers and IoT devices with minimal silicon area
Adopted by the Trusted Computing Group (TCG) as the DICE Architecture specification

Certificate-Based Identity

DICE enables the creation of device identity certificates anchored to the hardware root of trust. Each device can generate a self-signed certificate or a certificate signing request (CSR) tied to its unique CDI.

Supports X.509 certificate enrollment for enterprise PKI integration
Enables mutual TLS (mTLS) with hardware-bound client certificates
Device identity persists across reboots but changes if firmware is tampered with
Aligns with IEEE 802.1AR secure device identity standards

Recovery and Resilience

DICE defines a recovery policy that allows a device to restore a known-good state after a failed update or detected compromise. The architecture supports measured, verifiable rollback.

Recovery image is measured and attested before execution
Failed updates produce a different CDI, alerting verifiers to the change
Supports A/B boot partitions with cryptographically verified fallback
Prevents rollback attacks by binding version information into the measurement chain

HARDWARE IDENTITY COMPARISON

DICE vs. TPM: Key Differences

Comparing the Device Identifier Composition Engine (DICE) standard with a discrete Trusted Platform Module (TPM) across critical dimensions for IoT and embedded attestation.

Feature	DICE	Discrete TPM	Software TPM (fTPM)
Hardware Cost	$0 (uses existing flash)	$2-5 per unit	$0 (uses CPU trusted zone)
Boot Time Impact	< 1 ms	50-200 ms	10-50 ms
Physical Attack Resistance
Remote Attestation Support
Sealed Storage for Keys
Layered Boot Measurement
Silicon Footprint	< 1 KB ROM	~1-2 mm² die area	~100 KB SRAM
Standardized API	DICE Layering Architecture (TCG)	TPM 2.0 (ISO/IEC 11889)	TPM 2.0 (ISO/IEC 11889)

DICE ARCHITECTURE

Frequently Asked Questions

Explore the foundational concepts of the Device Identifier Composition Engine (DICE), a hardware security standard that layers boot state measurements into a compound device identifier for secure key derivation and attestation.

The Device Identifier Composition Engine (DICE) is a hardware security standard defined by the Trusted Computing Group (TCG) that creates a cryptographically strong, layered device identity without requiring a full Trusted Platform Module (TPM). It works by breaking the boot process into discrete layers, where each layer receives a Unique Device Secret (UDS) fused into the silicon during manufacturing. The first boot layer combines the UDS with a hash of the next layer's code to derive a Compound Device Identifier (CDI). This CDI is then passed to the next layer, which repeats the process, mixing in its own code measurement. This chaining mechanism ensures that if any firmware or software component is modified, the final device identity changes, making it impossible to access sealed secrets. DICE is lightweight, requiring only a small amount of ROM and cryptographic logic, making it ideal for resource-constrained microcontrollers and IoT devices where a full TPM is cost-prohibitive.

Enabling Efficiency, Speed & Accuracy

Intelligent Analysis, Decision & Execution

We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.

Talk to Us

Search across company data

Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.

Useful when people spend too long searching or get different answers from different systems.

Enterprise searchRAGPermissions

Automate internal workflows

Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.

Useful when repetitive work moves across multiple tools and teams.

AI agentsWorkflow automationGovernance

Add AI to products and internal tools

Build assistants, guided actions, or decision support into the software your team or customers already use.

Useful when AI needs to be part of the product, not a separate tool.

AI integrationDecision supportModel routing

DICE ECOSYSTEM

Related Terms

Explore the foundational hardware security primitives and identity standards that interact with or extend the Device Identifier Composition Engine (DICE) architecture.

Trusted Platform Module (TPM)

A discrete or firmware-based secure cryptoprocessor that provides hardware root of trust capabilities. Unlike DICE, which layers identity in firmware, a TPM is a dedicated microcontroller that securely stores platform measurements in Platform Configuration Registers (PCRs) and performs sealed-key operations. DICE is often viewed as a lightweight alternative to a full TPM for constrained IoT devices.

Hardware Security Module (HSM)

A dedicated physical computing device that safeguards and manages digital keys for strong authentication and provides cryptoprocessing. HSMs are used to protect the Device Identity Key lifecycle at scale in manufacturing environments. While DICE derives keys from firmware state, an HSM provides tamper-resistant storage for the root keys that might certify a DICE attestation chain.

Remote Attestation

A mechanism by which a host authenticates its hardware and software configuration to a remote verifier. DICE enables this by generating a compound device identifier that cryptographically captures the boot state. A verifier can compare the signed DICE measurements against known-good values to ensure the agent is running in a trusted execution environment before granting network access.

SPIFFE (Secure Production Identity Framework for Everyone)

An open-source standard for securely identifying software systems in dynamic environments. SPIFFE issues SPIFFE Verifiable Identity Documents (SVIDs) to workloads. DICE provides the hardware-rooted proof of trust that a SPIFFE agent can use to assert its identity without shared secrets, binding the workload identity to the physical device's boot integrity.

Confidential Computing

A hardware-based security paradigm that protects data in use by performing computation in a Trusted Execution Environment (TEE) . DICE can be used to attest to the integrity of the TEE itself. By measuring the firmware and hypervisor layers, DICE ensures that the confidential computing enclave has not been tampered with before secrets are provisioned into it.

Zero Trust Architecture (ZTA)

A security model that eliminates implicit trust and requires continuous verification of every access request. DICE serves as the hardware root of trust for the device identity pillar in a ZTA. It provides the immutable, cryptographically verifiable device posture assessment required to grant an agent just-in-time access to enterprise resources.

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.

Limited slotsGet a Free AI Consultation

How We Work

Custom AI workflows for your Business

One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.