Frequently Asked Questions
What data does the Twosense agent collect?
Twosense measures behavioral data such as typing cadence and mouse movements continuously throughout the day.
Are my keystrokes being logged somewhere?
Keystrokes and the resulting characters entered are not collected, with no mechanism for a User, Administrator, or Twosense employee to see what has been typed. Our system collects on the "how" of typing, not the "what" that was typed.
Does Twosense use my webcam or microphone?
No, Twosense does not use a webcam or a microphone, does not collect audio or visual data, nor require the hardware to be present.
Does Twosense keep track of when I’m at my computer, or any other performance tracking?
Twosense is not productivity software. We only report a list of authentication events and whether or not the MFA challenge was successfully automated.
How long does it take to start working?
Like any machine-learning system, it takes time before your unique behavior can be effectively modeled. For most users, some behavioral signals will have been learned within a day or two, with all users complete in under two weeks under normal usage.
Can users be locked out of applications if Twosense goes down?
If Twosense’s cloud service is unavailable, all users will be directed to traditional MFA workflows (the same ones they are using today.)
Does Twosense need sensitive access to the IdP or SSO?
No administrative access or keys are required. Twosense functions as a multifactor provider, which an Administrator will need to initially configure. From that point onwards, no further access is needed.
Can Twosense be rolled out to a specific group of users?
Yes. Twosense is configured as an MFA factor that gets added to a policy. That policy can then be applied to any group of users.
Can Twosense be used for remote employees?
Yes. Twosense is designed to be used for both secure facilities and remote agents.