brett.chadwick's account

OneSpan provide a enrolment process that provides guidance on holding the phone correctly, the lighting conditions and more to make a successful capture. This is done through the actual facial authentication as well after enrolment. A failure here would be handled as any other authentication the transaction is cancelled, however you could handle this by offering another method or presenting the user with an error advising them the method selected failed etc. This comes down to the workflow you'd like to achieve the platform is very flexible in this regard and responds based on the Risk Analytics rule configuration, or the in-app configuration.

OneSpan fully support the Multi Device License so multiple devices can be used by a single user to authenticate. They may be using a phone sometimes, and a tablet more often but want access on both platforms. However should you wish to limit device registration you can do this within the mobile application by checking Risk Analytics for a registered device/token and not allowing additional devices to be enrolled.

This is controlled via the available API, static passwords can be set, managed, updated, expired, account lockout and a full host of typical account management options. Including a baseline acceptance on password security.

OneSpan Intelligent Adaptive Authentication (IAA) employs a mechanism that will examine and calculate the risk of a users device.  The data collection process is handled through the Mobile Security Suite (MSS) leveraging a library called the Client Device Data Collector (CDDC).  This data is then passed through the MSS orchestration interface on to the IAA system.  IAA leverages the collected data to augment the risk analytics components and then provides risk scoring based on the results.  The data is collected for every transaction processed through IAA.  The device fingerprint of this data is held by IAA to help with identifying risk profiles but is not trackable.

OneSpan's Mobile Security Suite has multiple biometric modules.  For most biometric modules, the biometric templates are stored on the device only.  For the Mobile Security Suite Face Recognition, it is possible to leverage a server side computation.  If the face recognition data is stored on the server side, it can be deployed on premise and on cloud.  There is no limitation on for storage of the face recognition data based infrastructure, proprietary IaaS, AWS and Azure are all allowed.  Additionally, virtual machines or even hardware are also supported.