Biometrics are enrolled and bound to identity information centrally. Biometric authentication takes place on a central server against data stored securely on a server. A biometric match is required on the server to enable authentication. The solution grants access to information and assets to customers or employees, by means of an architecture analogous to using usernames and passwords to enable secure access to networks and data.
Aware’s Mobile SDKs can be used to capture biometrics on a device. Alternatively, BioComponents can be used within WebEnroll or URC to enroll biometric images (fingerprint, face, and/or iris) from the applicant. Biometrics are submitted securely to BioSP running on a central server. Identities are stored securely in BioSP Subject Manager. A biometric match is performed by Nexa fingerprint, face, or iris matching algorithms.
Biometric capture is performed on the device using Aware’s Mobile SDKs. Biometric authentication takes place within a module running on the device. A biometric match on the device is required to satisfy a PKI challenge/response exchange with the server. The biometric reference is stored on the device and only PKI data is exchanged. Authentication can serve to secure access to financial information or transactions conducted from a device. This architecture is analogous to use of a PIN on a smart phone. Open technical standards such as FIDO can be employed to conform to standards-based interfaces and protocols.Format Manager and Transaction Manager can be used to submit standards-compliant biometric records to the FBI or other external government systems for search.
Aware software can be used to enable payment systems with biometric authentication. Biometric modules operating on a mobile device or PC perform fingerprint, face, or iris capture, spoof detection, and/or authentication. Biometric matching can also be administrated centrally using BioSP.