desktop-virtualization-community-VDI-UDS-EnterpriseJOIN OUR


Google open sources tools to create security keys

Posted by UDS Enterprise TeamGoogle open sources tools to create security keys 2020-02-03 UDS Enterprise TeamGoogle open sources tools to create security keys

Companies and users are increasingly aware of the need to be extremely cautious when surfing the Internet and to properly protect their connected devices. The FIDO security keys are a way to provide extra protection against practices such as phishing. These are physical devices with an appearance similar to USB that users can connect to their terminals and are responsible for carrying out the double factor authentication (2FA).

With the aim of improving this technology and accelerating its adoption, Google has launched OpenSK, an Open Source project so that any organization or developer can create their own security keys compatible with FIDO U2F and FIDO2.


At the moment, OpenSK firmware can only be used in the Nordic chip. As Google explains in its security blog, Nordic has been chosen as initial reference hardware because “it is compatible with all major transport protocols mentioned by FIDO2: NFC, Bluetooth Low Energy, USB and a core of dedicated hardware encryption.”

In addition to the technology itself, Google also facilitates the model of a fully customizable 3D printable case to easily protect and transport the security key.

OpenSK is developed in Rust language and runs in TockOS which, according to Google, “makes the code less vulnerable to logical attacks, as it provides better isolation and cleaner OS abstractions in support of security.” The company says in its blog that they hope that over time this project "will provide innovative features, stronger embedded crypto, and encourage widespread adoption of trusted phishing-resistant tokens and a passwordless web."

For now, this initial version of OpenSK is considered an experimental research project. For more information you can check Google security blog and this video about OpenSK. The source code is available in this GitHub repository.



You must authenticate to review this post