The present disclosure relates to a data processing device for executing an application. Furthermore, the present disclosure relates to a method for executing an application in a data processing device. Furthermore, the present disclosure relates to a corresponding computer program product.
Today, security plays an important role in many electronic devices and computing environments. For example, conventional mobile electronic devices may be used for payment transactions which require that sensitive payment-related data, such as user credentials, are input and/or stored on said devices. Such mobile electronic devices may for instance be equipped with a near field communication (NFC) interface based on radio frequency (RF) technology, in order to exchange payment-related data with a terminal device at a point-of-sale (POS).
Traditionally, sensitive payment-related data have been incorporated into dedicated security tokens such as smart cards, in which the data are inherently confined to a relatively trusted environment. However, with the advent of integrated solutions, in particular the integration of so-called secure elements (SE's) in mobile devices, payment-related data are often exposed to a potentially hostile environment, and therefore the confidentiality of these data may be at stake.
A secure element is often implemented as an embedded chip, more specifically as a tamper-resistant integrated circuit with stalled smart-card-grade applications, for instance payment applications, which have a prescribed functionality and a prescribed level of security. Examples of such secure elements are the integrated circuits of the so-called SmartMX™ or SmartMX2™ series of IC's produced by NXP Semiconductors. Alternatively, so-called Subscriber Identity Modules (SIM's) or Universal Subscriber Identity Modules (USIM's) may be used as secure elements. Furthermore, secure digital (SD) cards, such as traditional SD cards or micro-SD cards, may be used as secure elements. A secure element may be embedded in a mobile device or another host device, for example as a small outline package soldered directly on a printed circuit board. Alternatively, a secure element may be comprised in said mobile device as a removable component (e.g. a SIM or an SD card).
Although a secure element offers a relatively secure environment for executing applications, the execution of these applications typically requires that user input data, e.g. a personal identification number (PIN) or transaction confirmation data, are fed to the secure element via a user interface of a host device, e.g. via a physical or virtual keypad of a mobile phone in which the secure element is embedded. Furthermore, the execution of these applications may require that output data are presented to a user via a user interface of said host device, e.g. a display. It is evident that both the input data and the output data must remain secret, because these data may be sensitive in nature. However, since the user interface is typically driven by a central processing unit of the host device, these input data and output data may be acquired and manipulated relatively easily by an attacker.
Nowadays high-end mobile device architectures are advanced, compact computer systems which normally contain an application processor and a baseband processor. The baseband processor (or modem processor) controls radio interfaces such GSM, GPS, Bluetooth and Wi-Fi interfaces. The application processor is the main or central processing unit of the mobile device, which executes many different applications. This implies that the input data for the secure element and output data from the secure element may be exposed to many different components and processes of the mobile device.
In order to adequately protect payment transactions, dedicated standards have been developed by service providers (e.g. EuroCard, MasterCard and Visa) for both credit cards and debit cards. These cards, and thus the transactions executed with them, are typically protected by user credentials authorized or unlocked by a 4-digit secret PIN. The secret PIN must be protected against any attack; otherwise an attacker, who is able to acquire said PIN and other user data, may be able to execute transactions in the name of the user. Nowadays, transactions are normally carried out via so-called trusted terminals, so that the user may rely on the correct functioning of the display and the keyboard without fearing that, for example, a Trojan-horse attack reveals the user's input on the keyboard and/or manipulates the display during a transaction.
In mobile phone architectures several attempts have been made to provide a reasonably good security level for transactions of the kind set forth. For example, the so-called ARM TrustZone offers a mechanism for isolating a so-called secure world within a computing architecture, i.e. a secure sub-environment supported by hardware features. The ARM TrustZone mechanism has been described in “ARM Security Technology: Building a Secure System using TrustZone® Technology”, published by ARM Limited, ©2005-2009, document number PRD29-GENC-009492C. However, the ARM TrustZone mechanism requires context switching between the secure world and the non-secure world, and since the switch mechanism itself is at least partly controlled by elements of the non-secure world, attack points are offered to the whole system. Furthermore, mobile phones are vulnerable to so-called jail-break attacks which allow updating the complete Flash memory of the mobile phones by the attacker. Therefore, today's mobile phone platforms must still be regarded as relatively insecure.
As mentioned above, secure elements which are introduced into the mobile phone architecture, for example in combination with NFC technology, provide a relatively high level of security for storing and processing user credentials and keys, and thus they may be regarded as a trust anchor or root-of-trust in any such architecture. However, the trust-anchor feature of a secure element in current implementations cannot be fully exploited, because the secure element is to a certain extent still used as a slave device from an application perspective. Another strong feature of a secure element is its capability to establish an end-to-end secure channel for any application for which the required keys have been pre-installed on the secure element in a secure environment.
In view of the above, it is desirable to further increase the security of electronic devices and computing environments in which secure elements are used to facilitate the secure execution of applications. More specifically, it is desirable to better exploit the capabilities of secure elements in these electronic devices and computing environments.
There is disclosed a data processing device for executing an application, the data processing device comprising a processing unit for controlling access to at least one user interface comprised in the data processing device, and a secure element for facilitating secure execution of the application, wherein executing the application comprises receiving input data from and/or sending output data to the user interface, and wherein the secure element is arranged to cause the processing unit to restrict the access to the user interface during execution of the application.
According to an illustrative embodiment of the data processing device, restricting the access to the user interface comprises restricting the access to the user interface to instructions comprised in said application.
According to a further illustrative embodiment of the data processing device, the access to the user interface is restricted to the instructions comprised in said application by setting at least one control register in the processing unit to a value indicative of a secure access mode.
According to a further illustrative embodiment of the data processing device, the control register is comprised in an application controller of the processing unit.
According to a further illustrative embodiment of the data processing device, the secure element comprises an integrated circuit in which the application has been installed.
According to a further illustrative embodiment of the data processing device, the secure element is further arranged to cause the processing unit to revoke the restriction of the access after the application has been executed.
According to a further illustrative embodiment of the data processing device, the processing unit provides user interface access control by means of at least one of hardware and a control program installed in the processing unit, and wherein the secure element is further arranged to verify the integrity of the user interface access control.
According to a further illustrative embodiment of the data processing device, the secure element is further arranged to load a user interface access control program into the processing unit.
According to a further illustrative embodiment of the data processing device, the secure element is integrated into the processing unit.
Furthermore, there is disclosed a method for executing an application in a data processing device, the data processing device comprising a processing unit for controlling access to at least one user interface comprised in the data processing device, and a secure element for facilitating secure execution of the application, the method comprising the secure element causing the processing unit to restrict the access to the user interface during execution of the application, and receiving input data from and/or sending output data to the user interface.
According to an illustrative embodiment of the method, restricting the access to the user interface comprises restricting the access to the user interface to instructions comprised in said application.
According to a further illustrative embodiment of the method, the access to the user interface is restricted to the instructions comprised in said application by setting at least one control register in the processing unit to a value indicative of a secure access mode.
According to a further illustrative embodiment of the method, the secure element further causes the processing unit to revoke the restriction of the access after the application has been executed.
According to a further illustrative embodiment of the method, the processing unit provides user interface access control by means of at least one of hardware and a control program installed in the processing unit, and wherein the secure element further verifies the integrity of the user interface access control.
Furthermore, there is disclosed a computer program product comprising program elements executable by a processing unit or a secure element, wherein each program element comprises program instructions which, when being executed by the processing unit or the secure element, cause said processing unit and secure element to carry out or control respective steps of a method of the kind set forth.
Embodiments will be described in more detail with reference to the appended drawings, in which:
In accordance with the present disclosure, a data processing device, e.g. a mobile phone, for executing an application is provided. This data processing device comprises a processing unit for controlling access to at least one user interface comprised in the data processing device, and a secure element for facilitating secure execution of the application. The application may, for example, be executed by the secure element, but the secure element may have to rely on the processing unit to handle the input to and the output of the application. Alternatively, the processing unit may execute the application, but the processing unit may have to rely on the secure element for certain functions, for example for comparing input data with user credentials stored in the secure element or for cryptographic functions based on keys stored in the secure clement. In either case, executing the application comprises receiving input data from and/or sending output data to the user interface. Furthermore, the secure element is arranged to cause the processing unit to restrict the access to the user interface during execution of the application. In this way, the secure element's intrinsic capability to establish an end-to-end secure channel may be better exploited, and consequently it may be that the application may be executed more securely.
In accordance with the present disclosure, the secure element 104 may control the user interface access controller 204 in such a way that the latter activates a secure access mode in which said restricted access is enabled. For example, the user interface access controller 204 may contain a control register whose value may be set, by the secure element 104, to a value indicative of the secure access mode. The user interface access controller 204 then enables the restricted access to the user interfaces by means of techniques which are known as such, for example by means of the above-mentioned TrustZone mechanism. It is noted that the user interface access controller 204 does not need to be implemented as a separate entity within the processing unit; it may also consist of a designated set of software and/or hardware resources, e.g. a part of an ARM Trustzone allocated to the processing of user input and/or output. Furthermore, it is noted that, although the secure element 104 has been shown in
In prior art systems, the TrustZone control is typically performed by a TrustZone driver residing in a part of the application controller that belongs to the non-secure world. In accordance with the present disclosure, the TrustZone control unit 304 effectively performs the function of the TrustZone driver, i.e. it effectively controls the TrustZone by setting the TrustZone control register 302 to an appropriate value, i.e. a value indicative of the secure access mode. If the TrustZone control register 302 is set to such a value, then the application controller is effectively switched from the non-secure world into the secure world. That is to say, the application controller is effectively switched from the non-secure world into the secure world under the control of the secure element. Since the TrustZone driver function, or at least all security-critical parts thereof, reside in the secure element, they are adequately protected, and consequently it may be prevented that said TrustZone driver function or its security-critical parts are manipulated in order to open doors for attacks. The TrustZone driver function may for example be embodied as a computer program that resides in a non-volatile memory unit of the secure element. In the secure access mode, I/O transactions over the so-called Advanced Peripheral Bus 326 (APB) may for instance be rejected by the application controller if they are initiated by instructions that are not comprised in an application which is being executed or supported by the secure element.
It is noted that the application controller may contain more than one TrustZone control register, which allows for a more detailed control of specific TrustZone functions, for example. Furthermore, the secure element may set the value of the TrustZone control register of the application controller directly via dedicated hardware-based control signals which cannot be interrupted or changed by the application processor. This establishes that the secure element may effectively behave as a master device during the execution of the application. In particular, if the application has been installed in the secure element and the secure element executes said application and controls its input and/or output in accordance with the present disclosure, a relatively large security improvement may be achieved.
As soon as the application has been executed, e.g. as soon as a payment transaction has been carried out, the secure element may release the Trustzone control register and give back control to the application controller. In this way, a negative impact of the presently disclosed access control function on the processing speed of the whole system may be minimized.
Furthermore, any software used in the secure access mode, in particular the user interface control program, may be checked by the secure element in advance of a switch-over to said mode, in order to prevent execution of compromised code. Alternatively or in addition, the secure element may upload software, in particular the user interface control program, to the application controller before switching the application controller to the secure access mode. Both measures may further improve the security of the system. Furthermore, the secure element may verify the integrity of the user interface access control hardware comprised in the processing unit.
The skilled person will appreciate that, although the above-described embodiments have been illustrated with reference to the ARM TrustZone technology, similar technologies may equally well be used to implement the embodiments. For example, the principles underlying the above-described embodiments may equally be applied to data processing devices based on an Intel® architecture comprising so-called Software Guard Extensions (SGX), which allow an application to instantiate a protected container, referred to as an enclave. It is therefore envisaged that, in accordance with the present disclosure, the restricted access to the user interface may also be realized by activating a secure access mode based on an Intel® SGX mechanism, which mechanism subsequently assures said restricted access.
It is noted that the drawings are schematic. In different drawings, similar or identical elements are provided with the same reference signs. Furthermore, it is noted that in an effort to provide a concise description of the illustrative embodiments, implementation details which fall into the customary practice of the skilled person may not have been described. It should be appreciated that in the development of any such implementation, as in any engineering or design project, numerous implementation-specific decisions must be made in order to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill.
Finally, it is noted that the skilled person will be able to design many alternative embodiments without departing from the scope of the appended claims. In the claims, any reference sign placed between parentheses shall not be construed as limiting the claim. The word “comprise(s)” or “comprising” does not exclude the presence of elements or steps other than those listed in a claim. The word “a” or “an” preceding an element does not exclude the presence of a plurality of such elements. Measures recited in the claims may be implemented by means of hardware comprising several distinct elements and/or by means of a suitably programmed processor. In a device claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
Number | Date | Country | Kind |
---|---|---|---|
14150876.2 | Jan 2014 | EP | regional |