Intrinsic ID delivers strong, device-unique data security and authentication solutions for the connected world. These authentication solutions are based on Intrinsic ID’s patented SRAM Physical Unclonable Function or SRAM PUF technology.
Using this technology, security keys and unique identifiers can be extracted from the innate characteristics of each semiconductor. Similar to biometrics measures, these identifiers cannot be cloned, guessed, stolen or shared. Keys are generated only when required and don’t remain stored on the system, hence providing the highest level of protection.
Our SRAM PUF-based security solutions are very suitable for applications such as secure key generation and storage, device authentication, flexible key provisioning and chip asset management. They can be used to secure payments, to protect highly sensitive data, for anti-counterfeiting and anti-cloning, to prevent identity theft, piracy of media content and software apps, software reverse engineering, and more.
Intrinsic ID‘s security solutions are available as hard and soft Intellectual Property (IP) and are used by companies who want a proven, easy and cost-efficient way to provide a solid trust base within their devices and applications.
IoT platforms from cloud service providers (CSPs) such as Amazon AWS, Microsoft Azure, Google Cloud, and Alibaba Cloud offer services to onboard new edge IoT devices to their cloud. But strong device-unique keys, forming a robust root-of-trust, needed for device certification/registration and the most secure end-to-end authentication and encryption are not part of the service.
And adding an external security chip, such as a secure element, for this purpose is an expensive solution.
Unprotected firmware IP can be reverse engineered and exploited in multiple ways. Companies are looking for solutions to keep their IP and design secrets safe, protect against counterfeiting/cloning and overbuilding.
Semiconductor manufacturers want to be responsive to swings in market demand. But legacy root key creation/storage methods, such as key injection and storage in OTP, require rigid, “early-in-life” personalization. This leads to problems such as complexity, longer lead time, and occasional, inventory write-offs..