KeyTrac only records the relative dwell and flight time and the keycode of each key while you’re typing in a textbox. To keep passwords secure, we use a special, obfuscated format, which keeps all of your passwords safe.
No! The KeyTrac Recorder is explicitly bound to specific input fields and is technically not able to record entries which where made “outside” of these configured textboxes. Other inputs, wherever they may occur, are entirely ignored.
Users don’t even recognize that the KeyTrac Recorder is working in the background. We’ve done a lot of performance tests, optimizations and enhancements in order to not damage the user experience of your website.
The “password hardening” operation mode is intended to be used for enhancing the security of password based authentication. By using this feature, you add an additional, biometrics-based security layer to your application.
The “any text” operation mode is perfectly suited for identifiying users based on the keystroke dynamics while typing changing, dynamic text phrases. This type of recognition is the special feature of AnyText.
KeyTrac Recorder is bound to one or more textboxes and is waiting for user inputs to record keystroke dynamics.
After submitting the form, all recorded keystroke dynamics gets passed to your backend as form encoded values.
Now it’s time to pass the recorded keystroke dynamics and user ID to the KeyTrac API.
This is the time where the KeyTrac algorithm matches the submitted keystroke dynamics against the users’ profile.
The computed match-score is now passed back to your backend where you’re able to utilize these results.
Before getting started, you need to extend your codebase to be able to transfer and receive data from the KeyTrac API. You need to, at least, incorporate an enrollment and an authentication section for using KeyTrac.
After implementing the required changes in your code, you’re now able to send the recorded keystroke dynamics to the KeyTrac API. This is required for enrollment and authentication of a user.
Now, your’re almost done. In the authentication case, the API responds with a true/false value and a percentage match-score. Use this boolean value to decide whether to permit or to reject this authentication request.