TECHNICAL FIELD OF THE INVENTION [0002] The invention relates to the field of secure information transfer, in particular secure information transfer for open-network transactions.

BACKGROUND OF THE INVENTION [0003] The need for secure communication is ancient and has grown to paramount importance.

Any system implementing an electronic transfer of funds, for example, requires multi-level security measures. The simple acts of assigning and using a Personal Identification Number (PIN) to access the ATM debit network requires the use of highly controlled protocols and/or hardware.

[0004] Any transaction is susceptible to fraud and deceptions. Even a face-to-face encounter between a customer and banker could be subject to frauds of impersonation or false identity.

Transactions between strangers and more particularly, transactions conducted on an open- network like the Internet cannot be conducted within reasonable risk limitations without some kind of identity verification.

[0005] The use of a PIN provides a certain level of verification, as we assume that the only person with knowledge of the PIN should be the authorized cardholder. Of course, any communication of the PIN is subject to eavesdropping, interception or man-in-the-middle attacks.

When connecting to the ATM network, the PIN may not be transmitted, even in encrypted form, over open networks.

[0006] Information does not have to be transmitted to be communicated, however. For example, zero-knowledge techniques can be used to communicate information without transmitting the information. Zero-knowledge protocols take advantage of the fact that possession of data can be proved without revealing the data.

[0007] Another method of communicating information without transmitting the information can be seen in a PIN mailer process. The PIN mailer process allows a cardholder to select a PIN using a form and the paper mail. The PIN mailer process is compliant with current ANSI standards and accepted in the banking industry.

[0008] The card issuer associates a form with a card that has been issued to a cardholder. The association is typically to a specific form using a serial number and may be an association to a form type using a form ID. The card issuer sends the associated form to the cardholder. The cardholder is instructed to select a PIN for a given account by completing a paper-based form and delivering it to the card issuer or the issuer's producer via normal mail. The paper form that the cardholder completes is designed specifically for the purpose. First, it is typically a multi-layer carbon-copy form. The form includes a top page for entering the PIN in a manner that is clearly understandable to the user. The top page allows the insecure entry of the information.

According to protocol, the top page is destroyed by the cardholder as soon as the PIN is entered, so that there is no insecure copy of the information. The bottom page, or pages, are specifically designed to protect the data that has been entered. Parts of the page may be generated through cryptographic processes to further obscure the data. The cardholder completes the form by selecting their PIN on the top page by circling one or more values or filling in bubbles representing their desired PIN. Position information is transferred through to the bottom page. The position information does not include, in any form, the numerals that make up the PIN. The encoded information represents the position of the PIN on the now-destroyed top sheet.

[0009] Once the cardholder destroys the top page of the form, there is no cleartext or encrypted version of the PIN. This bottom page containing position information is then sent via normal mail to the card issuer. The page is safe from an interception attack because the form has no information identifying the cardholder and no information to assist in identifying the numerals associated with the position data. The card issuer is able to retrieve the value representing the PIN from the returned'bottom'page and information related to the request form, such as a form number or serial number.

[0010] What is needed, therefore, is a system and method for transferring information over an open network in a secure manner.

SUMMARY OF THE INVENTION [0011] Information may be securely transferred from a first device to a second device over an open network by transferring software to the first device and executing the software. Data representing the information is entered at the first device and transferred to the second device.

The second device uses the data to determine the information.

BRIEF DESCRIPTION OF THE DRAWINGS [0012] For a more complete understanding of the present invention and the advantages thereof, reference is now made to the following description taken in conjunction with the accompanying Drawings in which: Figure 1 is a diagram of a system for secure information transfer; Figure 2 is an architectural diagram of the acquisition process; and Figure 3 is an architectural diagram of the authorization process.

DETAILED DESCRIPTION OF THE INVENTION [0013] Referring now to the drawings, wherein like reference numbers are used to designate like elements throughout the various views, several embodiments of the present invention are further described. The figures are not necessarily drawn to scale, and in some instances the drawings have been exaggerated or simplified for illustrative purposes only. One of ordinary skill in the art will appreciate the many possible applications and variations of the present invention based on the following examples of possible embodiments of the present invention..

[0014] With reference to Figure 1, a system 100 for the secure transfer of information is shown. A computer 102 including a pixelated display 104 and a pointing device 106 such as a mouse may be used to send information, such as a PIN, to an authority. The computer 102 is communicably connected to the authority server 110 by network 108. Server 110 may be connected to a storage device 112 and a secure processor 114.

[0015] Typically, an initialization process authenticates the computer 102 to the server 110.

A selected and perhaps tailored version of PIN entry software is associated with the computer 102 and is loaded onto the computer 102 from the server 110. The software may be cryptographically linked to an Authorization process. The cardholder utilizes the software to enter data representing the PIN, such as position data indicating the position of a PIN numeral on a pixelated display. The data may be sent from the computer 102 to the server 110 through a strongly encrypted communications channel.

[0016] When the data is received by the server 110, the data is processed at secure processor 116 using association data stored in storage device 112. The secure processor provides the PIN for authentication, verification, identification or any other suitable purpose. It will be recognized by those skilled in the art that other forms of data could be communicated in the same manner.

[0017] The computer display may present a graphic representation of a traditional PIN Pad to the cardholder. The graphic representation of a PIN pad is a form provided to the cardholder providing a familiar interface to enhance usability and acceptance. However, clicking a mouse button as the cursor is on a graphic representation of a numeral provides the computer with the display address point and not the numeral. Only the server has the association that will generate the numeral from the display address point.

[0018] An Acquisition process securely obtains the information from which a card holder's PIN can be distilled. An Authorization process allows an Internet-based merchant to request a debit transaction be authorized and obtain payment.

[0019] With reference to Figure 2, a diagram of an information transfer system is shown. A computer 102 is communicably connected to a Web server 120. The Web server 120 provides an interface with an application server 122. The application server 122 is connected to a host cryptographic module 124.

[0020] Each of these components form a cryptographic zone. The cryptographic zones may be identified by the cryptographic controls in place within the zone and delineated where cryptographic controls change. The first zone provides the security for communication between computer 102 and web server 120. SSL is the standard encryption used for Internet communication.

[0021] The data sent from the computer 102 to the application server may be encrypted.

For example, the Advanced Encryption Standard (AES) may provide 256 Bit encryption of all information communicated between the computer 102 and the application server 122. The data sent from computer 102 to the PIN Distillation TRSM 124 may be encrypted. For example, the AES may provide 256 encryption between the computer 102 and the TRSM 124.

[0022] Acquisition data is acquired by system software installed on computer 102. The acquisition data may be encypted using an AES (DATABIkey.

[0023] The first zone includes the computer 102 and is basically uncontrolled: The client PC 102 is an end-point for almost all cryptographic security in the Acquisition process and is not directly controllable by the system. It is advantageous to establish a trusted presence at this uncontrolled point. One way to establish a trusted presence is to use cryptographic methods provided as part of system software that is securely downloaded, under 128-bit SSL, at the start of each session. Trust is further enhanced through the use of nationally recognized, federal standard message integrity verification technology: FIPS 180-2 Secure Hash Standard (SHS) Secure Hash Algorithm (SHA) SHA-512.

[0024] The second zone includes the web server and is a controlled area that is accessible via the Internet. It provides an accessible interface to the clients, but does not perform any meaningful function except transmitting information back to the Application Processing Zone.

The web server establishes the initial secure session to enable the download of the system software and the upload of the client Public cryptographic key (RSA 1024-Bit) to the Host Cryptographic Device in Zone 4. The web server is located within a physically secure area.

[0025] The third zone includes application processing: This zone performs much of the meaningful work of the Acquisition phase. The Application server 122 establishes itself as the end-point for the AES (256 Bit) encrypted communications channel to the client 102. The application server 122 may be located within a physically secure area.

[0026] The forth zone includes a secure area housing two components, the Host Cryptographic Module (HCM) and the Acquisition Data Store. Both components are within a physically secure area.

[0027] The HCM is a FIPS 140-2 Level 3 device and is the workhorse of the encryption process in the Acquisition process. It generates and uses the AES Keys created (Communications and Data) to support and protect information during the Transmission process. It also performs RSA and TDES encryption processes.

[0028] This is a cryptographically secured (128 Bit TDES) holding area for acquisition data while waiting for the Authorization process to begin.

[0029] With reference to Figure 3, a flowchart 300 of a commercial process is shown. At function block 302, a user accesses a merchant site that utilizes the present system's payment system and selects Debit as the form of payment for services and/or merchandise offered by the merchant. A 128 Bit SSL secured session is established between the Web server and the client PC at function block 304.

[0030] Under this secured communications path, the system's software is downloaded and installed on the client at function block 306. A digital certificate for establishing SSL sessions may be loaded on the Web Server. The The Host Cryptographic Module may manually load randomly generated TDES keys [KPS] under dual control and split-knowledge for use in encrypting the Acquisition data for storage.

[0031] The process ontinues with Communications Key Establishment at function block 308. An RSA Public/Private Key pair (1024 bit) is generated. The Public Key is sent via SSL to the Web Server and then as clear text to the Application server and finally to the Host Cryptographic Module. The Host Cryptographic Module generates a 256 Bit AES key AES to be used in protecting communications between the client and the Applications Server. The Host Cryptographic Module also generates a 256 Bit AES key (AES (Data)), this one is used to encrypt the Acquisition Data between the Client and the Host Cryptographic Module. The Host Cryptographic Module salts the AES (cOmm) keyS then generates a cryptographic hash (SHA-512) of the salted AES (comm) key, and then wraps the salted AES (comm) key, along with the cryptographic hash with the Client's RSA Public Key. This cryptogram is then presented to the Application Server. The Host Cryptographic Module salts the AES (Data) key, then generates a cryptographic hash (SHA-512) of the salted AES (Data) key, and then wraps the salted AES (Data) key, along with the cryptographic hash with the Client's RSA Public Key. This cryptogram is further encrypted with the AES (comm) key.

[0032] This cryptogram is then presented to the Application Server. The Host Cryptographic Module combines the two elements, salts the combination, then generates a cryptographic hash (SHA-512) for the salted combination, then encrypts the salted combination, along with the cryptographic hash of the salted combination with the Client's Public Key. This cryptogram is then presented to the Application Server, and is ultimately transmitted back to the Client further wrapped within SSL.

[0033] The Client decrypts the key package with its Private key, and then generates a cryptographic hash (SHA-512) of the result, comparing the calculated cryptographic hash with the one provided in the key exchange message. The Client decrypts the received cryptogram, first with the AES (Comm) and then with the Client's Private key making the AES (Data) key available for communications between the client and the Host Cryptographic Module. The Client then decrypts the cryptogram containing the AES (comm) key using its Private key, generates a cryptographic hash (SHA-512) of the resulting key, comparing the calculated cryptographic hash with the one provided in the key exchange message. The Client then decrypts the cryptogram containing the AES (Data) key using the AES key, further decrypting the result with its Private key, then generates of cryptographic hash of the resulting key, comparing the calculated cryptographic hash with the one provided in the key exchange message. The Client now has both the AES (comm) key, and the AES (Data) key for further communication with the Application Server.

[0034] Once the communications paths have been established, the acquisition data may be delivered at function block 310. Acquisition data is first'salted'then encrypted under the AES (Data) Key. Additional information to be transmitted with the Acquisition data is concatenated, and the result is again'salted'. The client performs a cryptographic hash of the resulting cryptogram using SHA-512. The resulting cryptographic hash is concatenated to the block if data to be transmitted and the resulting value is encrypted under the AES (comm) key. The result of the encryption is then processed with CRC-64. CRC is appended to the cryptogram.

This cryptogram is finally sent under SSL to the Web Server. The Web server removes the SSL encryption and forwards the message to the Application Server.

[0035] Once received by the Application Server, the message's integrity is verified at function block 312. The Application Server parses the message and a CRC is performed on the concatenation of cryptogram and Hash. The newly calculated CRC is compared to the CRC sent with the message. If they match, integrity is verified and the process continues. If not, the process ends and an error is generated.

[0036] The Application Server calls to the HCM to decrypt the message with the AES (comm) Key. The Application Server parses the concatenation again and a SHA-512 is performed against the cryptogram. The newly calculated Hash is compared to the Hash sent with the message. If they match, integrity is verified and the process continues. If not, the process ends and an error is generated. The cryptogram is sent to the Host Cryptographic Module. The Acquisition Data is securely stored awaiting the start of the Authorization Process. The Host Cryptographic Module decrypts the Acquisition Data from the AES (Data) key and re-encrypts with the TDES (Storage) Key [KPS] and send the resulting cryptogram to the Acquisition Storage area.

[0037] The following actions or activities may be accomplished before the first transaction can be authorized. The PIN Distillation TRSM manually loads randomly generated TDES keys under dual control and split-knowledge for use as PIN encrypting keys (PEK) [KPT or KPS] to protect PIN Blocks when transmitted to the EFT Interface. The Host Cryptographic Module manually loads randomly generated TDES keys under dual control and split-knowledge for use as Master Keys [*KKS] to protect all other keys while in storage. The Host Cryptographic Module manually loads randomly generated TDES keys under dual control and split-knowledge for use as Key encrypting keys (KEK) [KKT] to protect the exchange of key used to protect PIN Blocks (PEK) [KPT] when transmitted to the EFT Networks.

[0038] The authorization process begins when a merchant accesses the system's Transaction Manager and requests payment for services and/or merchandise offered by the merchant. Once initiated, the Gateway Server uses transaction information provided by the merchant via the Transaction Manager to identify the proper acquisition data cryptogram in storage. The Gateway Server requests the acquisition data cryptogram from storage and provides it to the PIN Distillation TRSM.

[0039] The PIN Distillation TRSM decrypts the acquisition data cryptogram using the TDES (storage) Key [KPS]. The PIN Distillation TRSM distills the cardholder's PIN from the Acquisition Data. The PIN Distillation TRSM creates the required PIN Block (ANSI Format 0) and encrypts with the PEK (ATMD) [KPS]. The PIN Distillation TRSM provides the cryptogram to the Gateway. The Gateway sends the cryptogram to the EFT Interface. The EFT Interface sends the cryptogram to the Host Cryptographic Module. The Host Cryptographic Module translates the PIN Block from encryption under PEK (ATMD) [KPS] to encryption under PEK (EFT) [KPT]. The resulting cryptogram is sent back to the EFT Interface. The EFT Interface sends the cryptogram to the EFT Network.

[0040] It will be appreciated by those skilled in the art having the benefit of this disclosure that this invention provides a system for PIN exchange. It should be understood that the drawings and detailed description herein are to be regarded in an illustrative rather than a restrictive manner, and are not intended to limit the invention to the particular forms and examples disclosed. On the contrary, the invention includes any further modifications, changes, rearrangements, substitutions, alternatives, design choices, and embodiments apparent to those of ordinary skill in the art, without departing from the spirit and scope of this invention, as defined by the following claims. Thus, it is intended that the following claims be interpreted to embrace all such further modifications, changes, rearrangements, substitutions, alternatives, design choices, and embodiments.