Haventec Authenticate decentralises your authentication across 3 different locations. If a hacker wanted to try to access your account, they would need to have all 3 parts of the key: the secret key on your device, the one-time server key and your PIN which only you know as it is never saved anywhere. If an attacker manages to get all 3 parts, they will need to use them before you re-authenticate because Haventec Authenticate will roll your device secret key and the sever key after every successful authentication.
Because we have rebuilt authentication from the ground up we have also included 2FA built into our Authentication process. Two Factor authenticate is a combination of something you know, something you have, and something you are. With Haventec Authenticate we use something you know and something you have.
No. Your application can use any number of digits for the PIN. Because Haventec Authenticate does not know or save the PIN we do not restrict the length of the PIN. The length of the PIN you use is down to your organisation risk posture. We recommend a 4 digit PIN for a balance between security and usability.
A device is any hardware or software that runs your application. Including but not limited to:
You can choose to automatically register a customers device or you can have your customer enter a registration code into their device to register it.
Have a look at our Sign up user flow for more details.
Your customer can register as many devices as they like.
Yes, Haventec Authenticate can be deployed on-premise or you can use our demo cloud solution.
Haventec Authenticate uses industry standard integration patterns and protocols including but not limited to: