Middleware getting between biometric readers and template transfer storage
This presentation is the property of its rightful owner.
Sponsored Links
1 / 16

Middleware: Getting Between Biometric Readers and Template Transfer/Storage PowerPoint PPT Presentation


  • 83 Views
  • Uploaded on
  • Presentation posted in: General

Middleware: Getting Between Biometric Readers and Template Transfer/Storage. Mira LaCous CTO, VP Technology and Development BIO-key International, Inc. 651-687-0414 [email protected] Abstract.

Download Presentation

Middleware: Getting Between Biometric Readers and Template Transfer/Storage

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Middleware getting between biometric readers and template transfer storage

Middleware: Getting Between Biometric Readers and Template Transfer/Storage

Mira LaCousCTO, VP Technology and Development

BIO-key International, Inc.

[email protected]


Abstract

Abstract

  • A crucial factor in the acceptance of biometrics is getting information and templates from biometric readers into a usable format for storage and comparison against a database. "Middleware" solutions play a major role in streamlining this information for use with other biometric templates and solutions.


Agenda

Agenda

  • Purpose of Middleware with Biometrics.

  • What does Middleware Really Do?

    • User Interface

    • Application Interfaces

    • Security

    • Logic Control

    • Communications

    • Storage / Retrieval

  • Biometrics

  • Thoughts on Standards.


Purpose of middleware

Purpose of Middleware

  • Users interacting with complex systems.

  • Managing the overall process.

  • A case example…


What does middleware do

What does Middleware Do?

  • Provide essential functions:

    • User Interface

    • Application Interfaces

    • Security

    • Logic Control

    • Communications

    • Storage / Retrieval

  • We’ll focus on Biometric Authentications.


The architecture

The Architecture


User interface requirements

User Interface Requirements

  • User interaction and prompting.

  • User training and guidance.

  • Error and Exception handling.

  • Cool look and feel… it is a ‘new’ technology.


Api requirements

API Requirements

  • Must be flexible for various systems.

  • Provide the key functionality of:

    • Administration

    • Enrollment

    • Authentication

    • Reports and Logs

  • May conform to standards, like BioAPI.


Security requirements

Security Requirements

  • Examine all forms of spoofing/hacking.

  • Protect templates and models.

  • Prohibit replay and other attacks.

  • Preserve privacy.

  • Stop identity theft or use.


Logic control requirements

Logic Control Requirements

  • Must make decisions at various levels.

  • Determine flow and control of authentication.

    • User Interaction

    • Security handling

    • Retry / Fail

  • Ultimately the decision for access / denial.


Communications requirements

Communications Requirements

  • Handles the transport of data and control.

  • Issues of Firewalls must be considered.

  • Consider standards:

    • TCP/IP & HTTP

    • 802.11b & Blue Tooth

    • USB & USB2 & Firewire

    • and many, many more

  • Again, must fit various needs.


Storage requirements

Storage Requirements

  • Centralized or Distributed.

  • Manages significant data for Biometrics.

  • Support Verification or Identification.

  • Suitable for various applications.

  • Meets standards and open… yet secure.

  • Cost effective…


Now the biometric

Now, the Biometric

  • Accuracy is required

    • Low False Accepts (major security issue)

    • Low False Rejects (piss off factor)

    • Low Failure to Enroll (missing populations)

  • Accessibility

    • Must be easy to use

    • Non-intrusive

    • Intuitive operation, when possible

  • Cost effective


Standards

Standards

  • Each are can have a standard…

    • Templates (CBEFF, NIST, etc)

    • APIs (BioAPI, BAPI, HAAPI, etc)

    • Security (FIPS, X.509, CDSA, IPSEC, etc)

    • Storage (M1, Relational, ODBC, etc)

    • Industry (AAMVA, HIPAA, LDAP, Novell, etc)

  • Can fall to lowest common denominator.

  • Costs, advantages, requirements must all be weighed and examined.


Is it magic

Is it Magic?

  • With the right components and structure, anything is possible.

  • There are many ways to the solution…


Questions

Questions?

Mira LaCous

CTO, VP Technology and Development

BIO-key International, Inc.

[email protected]

651-687-0414


  • Login