What we want to solve with UNiD

by masa256k1 in September 22nd, 2021

In order to develop secure IoT services, developers have to consider device, network, and cloud security from the development stage, which requires a high level of expertise. For example, it is necessary to consider the selection of hardware and chip in the development stage, how to embed the device key and certificate in the manufacturing stage, how to update the firmware in the operation stage, and how to invalidate the certificate in the destruction phase.

In many cases, the each development is outsourced to the respective vendors, which is a huge burden and cost for the project team. In addition, the manual security provisioning such as embedding individual key and certificate is difficult to manage the vulnerabilities.

Unlike the manual security provisioning, UNiD enables IoT devices to autonomously manage their identifiers, keys, and certificates to build digital trust with other devices and the cloud by leveraging decentralized identity and hardware Root of Trust. You can see the reference code of DID written by NodeJS from here.

Currently, we focus on developing open-source libraries written by Rust and compatible with Renesas Electronics RA6M3 (Cortex-M4) to automate security provisioning.

We believe the way of compiling Rust as a static library (.a) and referring it from C is the better choice due to its "simplicity" and "fewer dependencies."

You can easily integrate our Rust libraries into devices to build E2E secure channel and send messages securely and privately regardless of the network topology or routing hops.

We believe that most IoT devices will be configured on the basis of Root of Trust and encrypted communication, just as most web services are now using TLS communication. And we also believe the new security stack should be developed openly and widely available for all developers to use.

If you'd like to be a part of the UNiD community, visit our GitHub. Click Star🌟 if you like.

Your cart