Authentication is the act of confirming the truth of a datum or entity. This might involve confirming the identity of a person or assuring that a computer (program) is a trusted one. You can authenticate in three different ways: based on something you know, something you have or something you are. Each authentication factor covers a range of elements used to authenticate or verify a person’s identity prior to: being granted access; approving a transaction; signing a document; granting authority to others and establishing a chain of authority.

To be more specific, the three factors (classes) of authentication are:

+ Ownership: a devise the user has to verify that he is to be trusted. For example a wrist band, ID card, security token, software token or cell phone.

+ Knowledge: something the user knows to verify that he is to be trusted. For example a password, a personal identification number (PIN) or a unique challenge response.

+ Inherence: something the user is or does to verify that he is to be trusted. For example fingerprint, retinal pattern, DNA sequence, signature, face, voice or some biometric identifier.

Our answer…

TrustBuilder is our answer to your obligation to be sure. TrustBuilder is a versatile authentication server, that we built based on our experience and knowledge obtained in many projects at large organizations. This safe guard provides User Authentication, Adaptive Access Control and Transaction Validation services to Web or Network Access Management platforms, to portals and to applications. Multiple authentication mechanisms, 2-factor authentication and several authentication data sources can co-exist and can be combined to suite the most complex needs. TrustBuilder offers open and flexible integration capabilities and can also seamlessly be integrated with IBM Security Access Manager for Web (ISAM) and IBM Security Access Manager for Mobile.