With a hardware root of trust, security protocols and applications can be run within a secure perimeter of an SoC, keeping keys and security assets protected from unauthorized access. Even biometric applications, like iris-matching, can be processed within the root of trust with strong protection of the templates and the matching algorithms stored therein. A hardware root of trust can perform a nearly unlimited number of different security applications, and run those on behalf of many different entities, such as the chip manufacturer, device OEM, service provider, and so on. This introduces a new challenge namely while many applications or entities require access to the security capabilities of the root of trust, the access levels, privileges and functions needed can vary greatly. This session will discuss how a secure co-processor with multiple roots of trust allow different entities or applications to have their own “virtual” security core in the SoC, but each with a private security domain.

This webinar will answer the following questions:

  • What are examples of apps and features that a root of trust enables?
  • Why is there a need for multiple roots of trust?
  • Why might different stakeholders require different security access levels?
  • What are the capabilities of Rambus root of trust solutions?

View more in the Secure Silicon IP Series:

Part One: Complexity vs. Security

Part Two: Will the Real Root of Trust Please Stand Up?

About the Speaker

ben-levine

Ben Levine
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.