In simple terms, a root of trust is the security foundation for a system-on-a-chip (SoC) or electronic system. Any functionality that needs to be secure relies in whole or in part on that root of trust. However, the term “root of trust” means different things to different people. In some cases, a root of trust is thought to be a single key that was either provisioned to a device or generated by the device itself. In other cases, a root of trust is seen as code, usually boot code, that is immutable and considered always trusted. A newer definition of a root of trust is a hardware module embedded in a chip or system that provides security functionality that keeps the entire chip or system secure.
Even when it is clear that root of trust is referring to a hardware root of trust, there is such a wide range of root of trust hardware available that the real capabilities and security of any given hardware root of trust is not readily apparent. In this session, we’ll discuss the attributes of a hardware root of trust that provides strong security and the flexibility to adapt to future threats.
This webinar will answer the following questions:
- What is meant by a “root of trust?”
- How can a root of trust be implemented?
- What are the features of a best-in-class root of trust?
- What does Rambus offer for root of trust functionality?
View more in the Secure Silicon IP Series:
Part One: Complexity vs. Security
Part Three: When One is Not Enough: Multiple Roots of Trust
About the Speaker
Senior Director, Product Management, Rambus
Ben Levine is Senior Director of Product Management for the Rambus Security Division. He is the product line manager for the Rambus family of hardware security cores, the CryptoManager Root of Trust. He has held other positions at Rambus, including Technical Director focusing on content protection, and Director of Engineering, managing hardware and software teams. His technical expertise includes ASIC design, hardware security, system security, computer architecture, and system design.