VALIDATING A TRANSACTION WITH A SECURE INPUT AND A NON-SECURE OUTPUT

Abstract

In accordance with the invention, in order to validate a transaction on a mobile handset, PC, tablet or similar device, a user closes the loop between a non-secure display controlled by a host processor and a secure keypad controlled by a secure processor such as a master secure element or trusted execution environment. The user validates the transaction by entering on the secure keypad the data shown on the non-secure display. The transaction is validated because the user only enters the data that the user agrees to and only the user is able to enter the data.

Description

Related application “Secure User Authentication using a Master Secure Element”, Attorney Docket No. 81494882US01 filed on the same day and assigned to the same assignee is incorporated by reference herein in its entirety.

Related application “Validating a Transaction with a Secure Input without Requiring PIN Code Entry”, Attorney Docket No. 81526126US01 filed on the same day and assigned to the same assignee is incorporated by reference herein in its entirety.

BACKGROUND

Mobile platforms or connected devices such as smart phones, personal computers, tablet PCs are integrating a secure element to authenticate the platform, to protect user credentials or to secure transactions. The secure element is typically a highly tamper resistant device that provides a secure execution environment isolated from the host processor. The secure element may be integrated into various form factors such as, for example, SIM cards, SD cards, or small outline packages attached directly on the printed circuit board (embedded secure element) and is especially useful for payment applications such as bank cards, mobile wallets and the like.

A payment transaction often requires the authentication of the user to either activate the application or to validate the transaction. A payment transaction is usually performed on a secure terminal with trusted user interfaces (i.e. secure display and keypad) for added security. In the typical mobile handset type architecture, a user enters their PIN code or activates the confirmation button located directly on the handset keypad. The entry of the PIN code or the activation of the confirmation button is typically handled by the host processor which operates in a non-secure and open environment. Because mobile handsets are typically connected to a network, the handsets can be infected by malware that can operate to intercept the entered PIN code or cause an invalid transaction to be confirmed.

Typical transaction validation involves two factors: 1) the application needs to be assured that only the user can validate the transaction; 2) the user needs to be assured that only the transaction the user accepts is completed. Typical solutions to the validation issue in current mobile handset architecture are typically software solutions that attempt to isolate the PIN code entry device and the display drivers showing the transaction from other processes running on the host processor. The various techniques of process isolation or virtualization create a secure environment that is typically not tamper resistant and also typically increases the complexity of the required software architecture. One example of such an approach is the TEE (Trusted Execution Environment) proposed by GlobalPlatform TEE White Paper, February 2011 and incorporated herein by reference in its entirety which states in part:

• • The TEE is a separate execution environment that runs alongside the Rich OS and provides security services to that rich environment. The TEE offers an execution space that provides a higher level of security than a Rich OS; though not as secure as a Secure Element (SE), the security offered by the TEE is sufficient for most applications. In this way, the TEE delivers a balance allowing for greater security than a Rich OS environment with considerably lower cost than an SE.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an embodiment in accordance with the invention.

FIG. 2 shows an embodiment in accordance with the invention.

FIG. 3 a shows two keypad layouts.

FIG. 3 b shows a virtual keypad which supports letter input.

FIG. 3 c shows a keypad mask on a polarizer layer in accordance with the invention.

FIG. 3 d shows the layers of a virtual keypad in accordance with the invention.

FIG. 4 a shows an embodiment in accordance with the invention.

FIG. 4 b shows an embodiment in accordance with the invention.

DETAILED DESCRIPTION

Related application “Secure User Authentication using a Master Secure Element”, referenced above, describes an exemplary embodiment where master secure element 120 is used as a secure processor and controls user input into the handset keypad (or touch screen) 110 to secure the user authentication based on, for example, the entry of a PIN code (see FIG. 1). The basic idea is that transaction validation can be accomplished by a secure processor that controls the user input but not the output. Using a master secure element is one embodiment of secure processor 120. The TEE is essentially a virtual secure processor. Using the TEE as secure processor 120 as discussed above in place of a master secure element is typically a less secure embodiment but also an embodiment in accordance with the invention.

With reference to FIG. 1 showing secure mobile phone architecture 100, it is apparent that Secure Processor (SP) 120 does not control non-secure display 130 which remains in non-secure domain 101 where it is controlled by host processor 115. Note that it is typically much more difficult to secure the display 130. Keypad 110, on the other hand, resides in secure domain 102 where it is controlled by SP 120. This raises the issue that the user cannot trust the transaction displayed even though application 155 is running securely in SP 120. In embodiments in accordance with the invention, SP 120 may be, for example, a master secure element or a TEE.

In embodiments in accordance with the invention, transactions may be secured on mobile handsets, PCs, tablets and similar devices equipped with a secure input and a non-secure output. When application 155 running on SP 120 validates a transaction, keypad 110 is fully controlled by SP 120. This allows the user to safely enter confidential data such as a PIN code that is directly transferred to application 155.

FIG. 2 shows an embodiment in accordance with the invention where the user closes the loop between the non-secure display 130 controlled by host 115 and keypad 110 controlled by SP 120. The user validates the transaction by entering on keypad 110 the data (e.g. the price of an item to be purchased). The transaction is validated because the user only enters the data that the user consents to enter and entry of the data is limited to the user. In step 210 of FIG. 2, host 115 sends “Data” related to the transaction to master secure element 120. In step 220, SP 120 requests data validation from host 115. This causes host 115 to display “Data*” on non-secure display 130 in step 230. In step 240, the user enters the “Data*” into keypad 110. In step 250, “Data*” entered by the user in step 240 is compared with “Data” sent by host 115 to SP 120 in step 210. If “Data”=“Data*” the transaction is validated and allowed to proceed.

For mobile handsets, PCs, tablets and similar devices where keypad 110 is physical (i.e. keypad 110 is not a touch screen keypad on non-secure display 130), a typical way to validate the transaction, in an embodiment in accordance with the invention, is to use the transaction amount such as the price of an item or service as “Data*” that is read by the user from display 130 and entered into keypad 110. The user determines if the transaction amount is correct, say the advertised price of an item. If the transaction amount “Data*” and the transaction amount “Data” transferred from host 115 to SP 120 do not match, the transaction is cancelled. Hence, if there is malware running on host processor 115 that is able to manipulate the transaction amount “Data” sent to SP 120, SP 120 will detect it in step 250. If there is malware running on host processor 115 that is able to alter the transaction amount “Data*” showing on display 130, the user will cancel the transaction.

However, when a mobile handset, PC, tablet or similar device is equipped with a touch screen keypad (i.e. not a physical keypad) host processor 115 typically controls both display 130 and virtual keypad 110a which is projected onto display 130. Touch screen 135 overlays display 130 and is controlled by SP 120 when virtual keypad 110a is displayed. However, malware running on host processor 115 can control virtual keypad 110a and manipulate the layout of keypad 110a underneath touch screen 135. This can lead to the user entering an amount that is different from the one the user believes is being entered. For example, with reference to FIG. 3a, virtual keypad layout 310 is communicated to SP 120 while virtual keypad layout 320 is communicated to the user via display 130. Virtual keypad layout 310 is the layout for a typical cell phone keypad while virtual keypad layout 320 is the layout for the number pad for the typical computer keyboard. Then a transaction amount of $10 on display 130 as seen by the user communicates a transaction amount of $70 to SP 120.

In an embodiment in accordance with the invention, the integrity of keypad 110a may be verified to differentiate virtual keypad layout 310 from virtual keypad layout 320. The user enters, in addition to the transaction amount, secret data such as a PIN code having, for example at least four digits, that is shared between the user and SP 120. However, note that there is a security vulnerability if the PIN code contains only the numbers “4”, “5”, “6” and “0” as the positions of those numbers do not change in going from keypad 310 to keypad 320. For a four digit PIN code, 2.56% of the available PIN codes would have this security vulnerability. Using PIN codes with more than four digits can also be used to reduce this security vulnerability. For example, a six digit PIN code, only 0.4% of the available PIN codes have this vulnerability.

The malware may also attack the integrity of virtual keypad layout 310 by just reversing the positions of cancel and validate, tricking the user into validating a transaction when the user wished to cancel it. This may be solved, for example, by having green and red markers or other indicators (for “OK” and “CXL”, respectively) on the mobile handset case that are below the correct positions of the “OK” and “CXL” keys so that the user can detect when the positions have been switched.

FIG. 3 b shows virtual keypad 351 which supports letters and allows a PIN code to be replaced by a password to improve the security. Using secret data such as a PIN code, birth date or password, for example, strengthens the transaction validation with user authentication. Using a PIN code, birth date or password for the transaction provides an integrity check for virtual keypad 351 with the use of a PIN code typically providing the weakest solution.

FIG. 3 c shows an exemplary embodiment in accordance with the invention where keypad mask 356 has been added to polarized layer 355 underneath touch screen 135 as shown in FIG. 3d. Keypad mask layer 356 projects predefined keypad layout 310 onto touch screen 135 instead of virtual keypad layout 320 created on display 130 by host 115. Keypad mask 356 cannot be altered by host processor 115 as it is physically integrated into display 130 and provides a secure mapping to touch screen 135. This provides a secure solution to the possibility that host 115 manipulates non-secure display 130 and prevents the user from entering an amount that is different from the one the user believes is being entered.

In an embodiment in accordance with the invention, SP 120 drives two input lines of polarized layer 355 to activate keypad mask 356, one to control the background of predefined keypad layout 310. FIG. 3d shows the layers of display 130 and touch screen 135. Polarized layer 355 with keypad mask 356 is located between touch screen 135 and top glass 360. Liquid crystal layer 365 lies between top glass 360 and bottom glass 370. Below bottom glass 370 is backlight and polarizer layer 375.

FIG. 4 a shows an embodiment in accordance with the invention using both the transaction amount and the PIN code on a mobile handset, PC, tablet or similar device for transaction validation. The transaction is validated when the user enters both the agreed to transaction amount and the user's PIN code. Knowledge of the PIN code is restricted to the user and SP 120 and only the user can enter both the PIN code and the transaction amount. Hence, if the transaction amount entered by the user on keypad 110a and the transaction amount sent to SP 120 by host processor 115 are different, the transaction is cancelled by SP 120.

In step 410 of FIG. 4a, host 115 sends “Amount” related to the transaction to SP 120. In step 420, SP 120 requests amount validation with PIN code from host 115. This causes host 115 to display the amount and PIN entry fields on non-secure display 130 in step 430. In step 440, the user enters the “Amount*” and their “PIN*” into keypad 110a. Keypad 110a may be a virtual keypad generated by host 115 on display 130 or keypad layout 356 that is created by polarized mask layer 355 on touch screen 135. In step 450, “Amount*” entered by the user in step 440 is compared with “Amount” sent by host 115 to SP 120 in step 410 and “PIN*” entered by the user in step 440 is compared to “PIN” stored in the SP 120. If “Amount”=“Amount*” and “PIN”=“PIN*” the transaction is validated and allowed to proceed.

Note that for embodiments in accordance with the invention, it is not necessary for the transaction amount to originate from host processor 115. It may also come from another device directly connected to SP 120 such as a near field communications (NFC) controller 499 as shown in FIG. 4b if the mobile handset, PC, tablet or similar device is NFC enabled, for example. However, the transaction amount is still communicated to host processor 115 for validation by the user.

In step 455 of FIG. 4b, NFC controller 499 sends “Amount” related to the transaction to SP 120. In step 460, SP 120 requests amount validation with PIN code from host 115 and in step 465 sends “Amount” to host 115. This causes host 115 to display the amount and PIN entry fields on non-secure display 130 in step 470. In step 480, the user enters the “Amount*” and their “PIN*” into virtual keypad 110a. In step 490, “Amount*” entered by the user in step 480 is compared with “Amount” sent by NFC controller 499 to SP 120 in step 455 and “PIN*” entered by the user in step 480 is compared to “PIN” stored in the SP 120. If “Amount”=“Amount*” and “PIN”=“PIN*” the transaction is validated and allowed to proceed.

SP 120 in accordance with the invention requires a security indicator such as, for example, an LED to inform the user that the system is operating in secure mode and prevent phishing although any data intercepted by malware running on host processor 115 typically cannot be introduced into SP 120. SP 120 is designed such that user data can only be entered through keypad 110/110a.

Note that for embodiments in accordance with the invention, it is not necessary for the transaction amount data to originate from host processor 115. It may also come from another device directly connected to SP 120 such as a Near Field Communications (NFC) controller if the mobile handset, PC, tablet or similar device is NFC enabled, for example. However, the transaction amount is still communicated to host processor 115 for validation by the user. Also the PIN code need not be verified directly by SP 120. For online transactions, for example, the PIN code entered by the user may be encrypted by SP 120 and sent to a back end server for authentication. Transaction data such as amount, card number or expiration date may be either encrypted together with the PIN code or encrypted separately when communicated to the back end server.

While the invention has been described in conjunction with specific embodiments, it is evident to those skilled in the art that many alternatives, modifications, and variations will be apparent in light of the foregoing description. Accordingly, the invention is intended to embrace all other such alternatives, modifications, and variations that fall within the spirit and scope of the appended claims.

Claims

1. A method for validating a transaction using a secure input and a non-secure output comprising: sending first data from a host processor to a secure processor;sending a request for data validation from the secure processor to the host processor in response to receipt of the first data by the secure process;sending second data from the host processor to the non-secure output for display to a user;accepting a user input of the second data into the secure input;sending the second data from the secure input to the secure processor; anddetermining if the first data and the second data are equivalent to validate the transaction.

2. The method of claim 1 where the non-secure output is a display.

3. The method of claim 1 where the secure input is a physical keyboard.

4. The method of claim 1 where the first data is a transaction amount.

5. The method of claim 1 where the secure processor is a master secure element.

6. The method of claim 1 where the secure processor is a Trusted Execution Environment.

7. A method for validating a transaction using a secure input and a non-secure output comprising: sending first data from a device to a secure processor;sending a request for transaction validation from the secure processor to the host processor in response to receipt of the first data by the secure process;sending second data from the host processor to the non-secure output for display to a user;accepting a user input of the second data and secret data into the secure input;sending the second amount and the secret data from the secure input to the secure processor; anddetermining if the first data and the second data are equivalent and authenticating the secret data to validate the transaction.

8. The method of claim 7 where the device is the host.

9. The method of claim 7 where the non-secure output is a display.

10. The method of claim 7 where the secure input is a touch screen overlying the display.

11. The method of claim 10 further comprising a keypad mask on the polarized layer interposed between the display and the touch screen.

12. The method of claim 7 where sending a request for transaction validation includes providing the first data to the host processor.

13. The method of claim 12 wherein the device is a Near Field Communications (NFC) controller.

14. The method of claim 7 where authentication of the secret data is performed by a back end server.

15. The method of claim 7 where the data is a transaction amount.

16. The method of claim 7 where the secure processor is a master secure element.

17. The method of claim 16 where sending a request for transaction validation includes providing the first data to the host processor.

18. The method of claim 17 wherein the device is a Near Field Communications (NFC) controller.

19. The method of claim 7 where the secure processor is a Trusted Execution Environment.

20. The method of claim 19 wherein the device is a Near Field Communications (NFC) controller.