Adding Voice Biometrics Security is as Easy as A-P-I

Share This

It doesn’t take a genius to know that security is critical to successful business operations. Recently we looked at different authentication methods and how to use them. Naturally, as a company that deals in voice communications, it makes sense to highlight the benefits of voice biometrics as a security option.

How It Works

There are two elements to voice biometrics: registration and authentication.

Registration entails talking to the voice biometric engine long enough so that it can create a voice print for an individual.

One method for creating a voice print is to use a random number case approach. In this use case, the voice bio engine prompts the user to recite a string of random numbers. An IVR captures this audio and sends it to the engine. If there is a successful match, the system then moves to another random string of numbers. This process is repeated until the voice biometrics engine determines that it has enough samples to create a voice print. Typically, this is in the range of 4–6 audio samples.

Authentication is even simpler. During subsequent calls to the same company, the caller’s voice is verified against the voice print already in the system. Registration only needs to be done once, making the authentication process a fast and efficient security measure once it’s set up.

A Robust API

At Plum, we’ve created our own REST API (or shim layer) specifically for voice biometrics. Our developers have done the hard work of evaluating numerous voice bio engines. Only the engines that meet our high standards and internal testing made the final cut into the API. Our developers continue to assess different voice bio vendors in order to offer the best combination of reliability and ease of use through a single API.

Normalizing multiple voice bio engines in an API allows us to offer increased flexibility without a corresponding increase in development complexity. The API brings the most common commands to the forefront, and pushes everything else to the background to make integration smoother.

At the heart of our voice biometrics API are the commands to manage user creation and validation, to initiate voice print enrollment for both new and existing users, and to authenticate users. The end result streamlines the creation and authentication of voice prints through an interactive voice response application.

Integrate Voice Biometrics into Applications

Thanks to our voice bio REST API, developers can easily boost the security of their DEV voice applications. A custom-made JavaScript helper library maintains the API endpoints and provides functions to parse XML DOM responses. It can also be used to build remote grammars for ASR matching, making voice biometrics much more usable. Developers can trigger this helper library by adding a single line of code to their VoiceXML script.

Without the assistance of the REST API and the JavaScript helper library, developers would have to connect everything directly between the voice biometrics engine and their voice application in a traditional, high level programming language. If your company wanted to change voice bio vendors or test different voice engines to see which one works best with your application, then developers would have to re-write all of the integration code to fit the new engine. A custom API makes testing different voice biometric systems or platforms a breeze. Plum Voice’s Voice Biometrics API makes voice biometrics a plug-and-chug coding option because it is designed to handle multiple engines.

Lauding the benefits of voice biometrics and multi-factor security authentication is all well and good, but if these additional features aren’t cost effective or are difficult to implement the ROI drops. Plum makes voice biometric authentication easy to implement into voice communications, reducing the number of hours that developers need to spend on it. This makes its security benefits even more attractive because it provides a strong layer of security as a standalone or as part of a multi-factor authentication process.

(Visited 418 times, 1 visits today)