

Current information about the planned delivery date can be found here in the Status Updates (scroll down). With strong hardware encryption, trustworthy thanks to open source, quality made in Germany. This reliably protects your accounts against phishing and password theft, and encrypts your communications and data. The Nitrokey 3 combines the features of previous Nitrokey models: FIDO2, one-time passwords, OpenPGP smart card, Curve25519, password manager, Common Criteria EAL 6+ certified secure element, firmware updates. The new Nitrokey 3 is the best Nitrokey we have ever developed. We are looking forward to seeing new form factors and possibly applications on your phone that comply with the FIDO2 specification.The New Nitrokey 3 With NFC, USB-C, Rust, Common Criteria EAL 6+ Some examples include USB security keys and NFC enabled smartcards, just to name a few. Our partners are working on a variety of security key form factors. The security key holds your credential and can be protected with an additional second factor like fingerprint (integrated into the security key) or a PIN to be entered at the Windows sign-in. These keys have all the benefits of a Trusted Platform Module (TPM) while also being portable enabling the increasing number of mobile workers.įIDO2 compliant security keys provide secure authentication, independent of the form factor. Unlike traditional passwords, these keys rely on high-security, public-key cryptography to provide strong authentication. A user can walk up to any device belonging to the organization and authenticate in a secure way – no need to enter a username and password or set-up Windows Hello beforehand.


Security keys allow you to carry your credential with you and safely authenticate to an Azure AD joined Windows 10 PC that’s part of your organization. Microsoft and its partners have been working together on FIDO2 security keys for Windows Hello to enable easy and secure authentication on shared devices. Or a public-sector organization that wants secure authentication on devices while adhering to security policies and directives where the users credential needs to be physically separate from the device itself. Another scenario is hospital medical staff that need access a patient records on a device no matter where the patient is located. Imagine a helpdesk scenario where an employee can walk up to any device and simply log in using Windows Hello and not username and password.
