Shortcuts Call 203 834 2288 Contact Us

Authentication + Unique Communication Channel = True Protection

Man in the Middle (MITM), Man in the Browser (MITB), Phishing, and Pharming attacks can take your costly layers of protection and make them useless. KeyID has the solution—patent pending technology in a simple, easy-to-deploy solution that eliminates the threat of MITM, MITB, Phishing, and Pharming.

Validate the End Points of the Channel
At the core of KeyID products is a simple premise—validate the end points of the unique communication channel. If you can be sure the data started in a valid location and ended in a valid location without interference, you eliminate MITM, MITB, Phishing, and Pharming.

Unique Design
All KeyID solutions integrate user authentication information with elements of the underlying SSL communication channel that are unique to the session, such as Client IP address, Server IP Address, the Public or Private Key, and a random session number.

Elevate OTP Protection
KeyID SecureOTP is a lightweight plug-in that installs on the client.

SecureOTP





True Protection
The client plug-in encrypts a packet with authentication information and elements of the unique SSL channel, such as Client IP Address, Public Key, and Random Session Number.

The server decrypts the packet, validating the elements of the unique communication channel and verifying that the valid client—and only the client—are in the channel. The original OTP is never transferred, so the elements of the channel can never be recreated.



Full ID Verification and Transaction Authorization
KeyID SecureCard goes beyond authentication to deliver complete data encryption, identity verification, and transaction authorization through an innovative, easy-to-deploy device.

SecureOTP







True Protection
The card reader encrypts and sends the private key, user information, and unique channel elements to the server.

The server calls on a KeyID device to verify the keys and the unique endpoints of the channel. Only the authorized client and server can be in the channel, or the KeyID device will reject the packet.