Secondary authentication is an important process as it increases security and allows a better overall authentication user experience. However, the usability aspects of some secondary authenticators such as knowledge-based questions together with a high rate of secondary authentication requests could achieve the opposite result. By utilizing the mobile device and easy to use biometrics such as finger, voice, and face you can easily improve the secondary authentication experience. Moreover, by using some of the built-in sensors of the mobile device you can also minimize the number of secondary authentication events. Transmit includes all the components you need to fix the secondary authentication user experience.
Connect your Applications
Instead of embedding authenticators into each one of your applications, use a simple interface to offload all authentication and provisioning tasks to Transmit. Your applications don’t need to manage authentication anymore and have a clear and static interface for requesting authentication and provisioning services.
Connect Existing Authenticators
Have some secondary authenticators you’d like to keep? We provide a simple middle-tier that allows you to plug them into the platform. Once connected you can manage these authenticators using the unique capabilities of the platform and deploy the same authenticators across different applications and channels.
As part of the Transmit platform you will find ready-to-go secondary authenticators including:
- Fingerprint scanning: TouchID for iPhone as well as fingerprint authentication for various fingerprint-enabled Android devices.
- Face recognition: Advanced face recognition algorithms for instant authentication. Unique anti-spoofing mechanisms prevent an attacker from bypassing the system using a picture or a video of the user.
- Voice recognition: Have the user authenticate using a simple paraphrase. Unique anti-spoofing mechanisms prevent an attacker from bypassing the system using recorded voice.
- OTP over SMS: a one-time code sent to the user’s mobile device. The user needs to re-enter that code back into the application.
- Mobile notifications and swipe: a notification is generated on the mobile app with the details of the secondary authentication request. All the user needs to do is swipe to approve.
- Landline callback: a call is generated to the user’s phone and the user needs to approve the secondary authentication request.
You can enrich the Transmit platform with context from various sources using a set of simple APIs. This context could be used to reach better secondary authentication decisions. For example, you can add context collected from the user’s device such type of hardware, location, and security status. You can add business related context as as account type and customer age. And you can add risk-related context from any risk-detection system or feed.
Embrace the future
The biometric race is just beginning. Additional biometric techniques are expected to hit the market and existing biometric techniques are expected to improve and expand to more devices. Cost of integration, time to market, and on-going maintenance work are increasing concerns. Transmit helps you manage all that with using a unified management platform and the separation of authenticators from your application. Whenever you need to update an existing authenticator, expand to additional devices, or add newly-released authenticators, you will do that centrally through the platform without the need to hardcode it into your applications.
Deploying new authenticators or even new versions of existing authenticators could be challenging. Authentication is right in the face of your users and if it doesn’t work properly the impact on the user-experience, brand, and business could be significant. No matter how much testing you do, you can never simulate all the different device configurations, environmental and human factors. The final test will always be in the field. Transmit provides mechanisms to do gradual deployment of any change you make. You can deploy to specific users, specific number of users, specific geo-locations, etc. You can then gradually increase the deployment phase and more importantly you can rollback immediately in less than 5 seconds if something is not working properly.
Biometric authentication introduces challenges that are very specific to the nature of biometrics. False Rejection Rate (FRR), False Acceptance Rate (FAR), enrollment failures, the time it takes to complete an authentication process are just a few. No matter which numbers the vendor comes up with and the results of your lab testing, the ultimate test is in the field and is ongoing. Transmit collects detailed information on all the different aspects of biometric authentication. Using our analytics capabilities, you can understand what works and what doesn’t, where the problems are, what’s the impact of changes you’ve made on your customer-base, and much more.
In a dynamic environment with different biometric authenticators, different endpoint devices, and different environmental conditions, many things could go wrong. Users may be unable to enroll, unable to authenticate, slow to authenticate or just confused. Your first priority from efficiency, user experience and cost perspective is to avoid that call to the customer care center. Transmit Security’s extensive conditional workflows allow you to do just that. However, if the customer calls for support, every second matters and you want to have accurate information on what went wrong and how to rectify it immediately. Transmit provides APIs and an interface for customer support personnel to quickly and efficiently address authentication and provisioning issues.