OpenTitan’s Peppermint and Darjeeling Bring Auditable Roots of Trust into the SoC Flow

OpenTitan’s Peppermint and Darjeeling push auditable roots of trust into mainstream SoC design, turning security into a verifiable architecture choice.

Updated

What is this trend?

OpenTitan’s Peppermint and Darjeeling package auditable roots of trust into SoC designs, making secure boot, identity, attestation, and lifecycle controls part of the core hardware flow.

  • Peppermint targets constrained IoT and MCU-class designs with an integrated root of trust and secure enclave.
  • Darjeeling extends the same open trust-anchor model to larger SoCs and embedded RISC-V platforms.
  • Security controls are shifting from add-on features to verifiable architecture decisions.
  • Teams now need threat models, verification evidence, and compliance-ready artifacts built into design flow.
  • Open, auditable RoT blocks help hardware teams design security earlier and prove it later.

What’s the latest?

OpenTitan’s IoT-focused Peppermint top-level wraps an integrated root of trust and secure enclave around the Ibex RISC-V core for wearables, IoT end nodes, and microcontrollers, giving constrained-dev

Autonomous Verification Agents, Packaging as Product Strategy, and Auditable Roots of Trust Move Upstream

How it developed

  1. Continuous risk scoring, hardware roots of trust, and agent-supervised EDA

  2. Package-Aware Co-Design Moves Upstream, EU Age Checks Put Hardware Attestation on the Hook

  3. Security certification becomes a release gate, AI verification moves upstream into environment buildout

  4. Security Moves Upstream, and Memory and Interconnect Become Core AI Design Constraints

Go deeper

Curated long-form picks on this trend — podcasts, videos, and analysis, by seniority.

Stay ahead in Hardware Engineering

Get the weekly Hardware Engineering brief in your inbox — the developments, what they mean by seniority, and what to do next.