Trusted terminal platform

Abstract

A point-of-sale (POS) terminal is provided for entering a PIN to enable a financial transaction. The point-of-sale terminal has a card reader for reading information from a credit card, a processor for running an operating system, with applications, a touch screen for displaying information and receiving user inputs, and a Security-Box connected between the touch screen and the processor to control the user input on the touch screen to the processor. The Security Box is configured to run in a “PIN Entry Mode” and a “Clear Text Mode.” When running in “PIN Entry Mode” the user input is not forwarded as touch coordinates to the processor and when running in “Clear Text Mode” the touch coordinates are transmitted to the processors.

Claims

1. A User-terminal for entering secure user information, comprising: a processor configured for running an operating system with applications; a touch screen configured for displaying information and receiving user inputs as touch coordinates from a user; a Security-Box being connected between the touch screen and the processor and configured to control a transfer of the user inputs to the processor, the Security-Box being configured to run in a “Secure Mode” and a “Clear Text Mode,” wherein when running in “Secure Mode” the user inputs are forwarded as replacement coordinates of the touch coordinates entered by the user, forwarded to the processor, and when running in “Clear Text Mode” the touch coordinates are transmitted to the processor; wherein the user-terminal is configured to run at least first and second applications displaying information on the touch screen and allowing an interaction with the user, the first application interacting with the Security-Box to perform security relevant financial transactions; wherein the second application interacting in “Clear Text Mode” with the touch screen; wherein the first application interacting with the Security-Box is configured for switching the Security-Box into “Secure Mode” and needs to be authenticated with the Security-Box using a cryptographic method with one or more security keys; and wherein the touch screen is connected to the Security-Box and the Security-Box is connected to the processor via a USB Composite Device having two logical USB-Channels, and wherein the two logical USB-Channels are setup to transmit the touch coordinates and the replacement coordinates respectively.

2. The User-Terminal of claim 1 wherein the security keys are stored in the Security-Box.

3. The User-Terminal of claim 1 wherein the first application interacting with the Security-Box uses a signature or cryptogram to authenticate with the Security-Box.

4. The User-Terminal of claim 3 wherein the Security-Box is configured to verify the signature or cryptogram of the first application interacting with the Security-Box before allowing switching into “Secure Mode”.

5. The User-Terminal of claim 1, wherein the User-Terminal is a mobile device without any physical keyboard and allowing interaction via the touch screen.

6. The User-Terminal of claim 1, wherein the User-Terminal is a Point-of-sale (POS) terminal for entering a personal identification number (PIN) to enable a financial transaction, and further comprising: a card reader for reading information from a credit card.

7. The User-Terminal of claim 6, wherein the card reader is a chip card reader that is integrated into the Security-Box, and wherein the Security-Box is configured to process a financial transaction based on the PIN and information of the credit card, without using the processor or applications running on the processor.

8. The User-Terminal of claim 6, wherein when a virtual pin-pad is displayed on the touch screen, the Security-Box switches to a “PIN-Entry-Mode” and is configured to interpret a user touch as the PIN, and to encrypt the PIN to forward the information together with credit card information to an associate service center/bank over a network controller.

9. The User-Terminal of claim 1, wherein the first application is further defined as a payment application running on the operating system and switching the Security-Box into “Secure Mode” and directing the touch screen to display a virtual PIN-pad on the display, wherein the payment application forwards card information from a card reader to the Security-Box, wherein the payment application forwards an encrypted personal identification number (PIN) received, from the Security-Box, to a service center/bank.

10. The User-Terminal of claim 9, wherein the payment application is configured to shift the virtual pin-pad randomly on the touch screen for every transaction and wherein the Security-Box is informed about the coordinates of the PIN Pad, to be able to interpret the user inputs.

11. The User-Terminal of claim 1, wherein the Security-Box and the display are connected with each other, and sensors indicate when a disconnection is performed, which leads to a deletion of keys in the Security-Box.

12. The User-Terminal of claim 1 wherein the touch coordinates and other touch events are transmitted with a first of the two logical USB-Channels and the replacement coordinates are transmitted with a second of the two logical USB-Channels, and wherein Key Management commands are also transmitted only over the second of the two logical USB-Channels.

13. The User-Terminal of claim 10 wherein a size of the virtual pin-pad is changed with every PIN entry.

Description

BRIEF DESCRIPTION OF DRAWINGS

(1) The figures show a possible embodiments of the invention, which are referenced by the following description. Both do not intend to limit the scope of the invention.

(2) FIG. 1 shows the secure components of the invention.

(3) FIG. 2 shows the functional Block diagram of the Security Box (SB).

(4) FIG. 3 shows the relevant software components.

(5) FIG. 4 shows the software stack of the operating system.

(6) FIG. 5 shows the high level boot process.

(7) FIG. 6 shows the application flow of the integrity checks.

(8) FIG. 7 shows the mode transitions of the invention.

(9) FIG. 8 shows the virtual PIN Entry with moving entry fields.

DETAILED DESCRIPTION

(10) Although the invention is described with respect to a special embodiment the invention is not restricted to this embodiment. The invention is directed to a universal user terminal with a touch screen on which security relevant and non security relevant applications are running.

(11) FIG. 1 shows the secure components of the invention. PIN entry function is provided by the touch screen of the terminal. In a preferred embodiment no audible tones are generated by the nature of this solution. Despite this the terminal implements an audio jack which allows people with disabilities to control the entry function. Audible tones are generated by the audio unit of the main controller board. For PIN entry this is always the same frequency and the same volume when any key of the virtual PIN Pad is hit.

(12) Additionally the context of the screen is switched off when the headphone is connected.

(13) The Terminal provides a switchable light control filter which limits observation in a fixed solid angle when a PIN is entered via the virtual PIN Pad. Additionally the entire virtual PIN Pad is shifted randomly (FIG. 8) for every transaction. As additional secure measure the size of the key pad is changed per PIN entry.

(14) The Terminal can use the MAGTEC MagneSafe IntelliHead Reader [3]. The magnetic-stripe reader is in a possible embodiment connected to the main controller using a standard communication interface (USB (Universal Serial Bus) 1.1, HID). The reader itself is equipped with build-in security, encryption head and cryptographic functions for device authentication and key management. The encrypted track data is read by the payment app running on the main controller board and transferred to the security box for translation. The design of the Terminal prevents modifications like adding an additional head and microcontroller from inside and outside.

(15) Each encrypting head contains a unique key which is shared with the Security Box and derived from a master key and the key serial number.

(16) Key injection is operated in a Key Loading and Initialization Facility (KLIF) using a Key Loading Device which is provided by the manufacture.

(17) The interaction of the reader is controlled by the payment application running on the main controller. In addition to the Security Box (FIG. 2), the device itself performs a self-test (FIG. 5, 6, 7) which includes integrity and authenticity checks upon boot and at least once a day.

(18) All Application modules (FIGS. 3 and 4) are under control of the Acquirer and signed by cryptographic procedure. The Terminal verifies the signature before execution.

(19) The PCI Terminal Firmware is provided by the Terminal Vendor, any changes are reviewed in a QA process and documented.

(20) The firmware image is signed by the Terminal Vendor as part of the Firmware Lifecycle process and verified by the Terminal before installation and execution (FIG. 7).

(21) As part of the security system, the Security Box controls the PIN entry and the touch events. If the Security Box is in “PIN Entry Mode”, only replacement characters will be submitted via the USB COM channel, touch events are suppressed.

(22) The Android OS and Kernel Modules (FIG. 4) are basis for a possible implementation. The System Package will contain only such modules which are necessary for operation. All Software executed on the Terminal run with least privilege; the System Package will be hardened accordingly.

(23) The modification of the Touch Screen, e.g. connecting a non secure touch via USB will lead the Terminal into an inoperable state. The replacement of the touch driver will lead the Terminal into an inoperable state. During PIN entry no X/Y coordinates are submitted from the Security Box except replacement codes for the touched field (virtual key), hence the observation of touch events by analyzing the USB communication in PIN entry mode is not relevant. If the Security Box is in Clear Text Mode and submits X/Y coordinates to an authenticated application, the coordinates are preferably encrypted using a TDES key (128 bit). On the main controller the key is secured by the NV SRAM of the Security Controller.

(24) The data link between these components is secured by design and/or cryptographic protocols. Key management is performed in compliance to ISO 11568 or ANSI X9.24. The Payment Card is always under control of the card holder.

(25) If the Terminal device is connected via a ECR-Interface all text messages will be signed by the ECR and verified by the Terminal Software (Driver).

(26) The Terminal provides the required cryptographic functionality SC embedded NV SRAM as keystore.

(27) The Firmware is protected by cryptographic mechanisms. PCI Terminal Firmware is managed by a Software Lifecycle Management System. The System Package in rest is protected by Software called MKS Integrity Manager which precludes unauthorized modification.

(28) The PCI Terminal Firmware itself is protected by cryptographic mechanism. The Terminal is equipped with a unique Device Number and a unique key pair. The information is loaded during manufacture in a controlled environment using principles of dual control and split knowledge.

(29) PCI Terminal Firmware is executed under control of the Main Controller (preferably a OMAP4460); it needs to be cryptographically verified by the SB (FIG. 5,6,7) and is part of the PCI approval. PCI SB Firmware is executed under control of the SB microcontroller. The responsibility in terms of PCI approval is in hand of the Security Box vendor.

(30) Add-On Applications (FIG. 4) are provided mainly by the Acquirer and these Apps are not part of the PCI approval.

(31) The SB is connected via a USB (FIG. 1, FIG. 3) connection which implements a USB Composite Device Class as HID and COM Device Class. On top of the Android OS, the terminal hosts multiple applications (FIG. 4) which have access to the terminal WXGA screen and access to touch events generated by the PCI SB Firmware. These applications are

(32) Payment Applications

(33) Other Applications

(34) All applications have to be under strict control of the Acquirer or the Terminal Vendor. It should not possible to download unsigned software in order to process applications which are out of control of these two entities. System hardening and least privilege confinement of applications deliver sufficient control in order to protect those applications. If an application gains access to a WEB site and downloads content which will be processed on the terminal, the WEB Server and the content is under control of the Acquirer (PCI DSS requirements will be fulfilled).

(35) The Terminal including its Security Box shall be evaluated according the PCI PTS 3.1. Modular Security Requirements following a modular evaluation approach.

(36) The following describes the physical security segregation and boundary of the Terminal; the dark gray SE elements (FIG. 1) are “Secure Elements” which communicate cryptographically to each other.

(37) The Security Box (SB) controls the PIN entry, cryptographic keys, EMV (Europay, MasterCard and Visa) PIN-offline verification and protects magnetic stripe data. It is connected via USB interface with the main controller and implements a USB Composite Device. In default mode the SB doesn't send any touch events to the Main PCB, see Security Mode Transition. The SB includes measures in order to protect the removal of the device from the terminal. It additionally controls some external tamper sensors which are used for disassembly protection and mesh sensing. A tamper alarm will raise an immediate erasure of the SB internal Master Key.

(38) The Main PCB (MPCB) controls the NFC, forwards Account Data to the SB and operates the software which controls the Payment and the Network. The MPCB embeds a Security Controller which is responsible for Secure Boot and provides a secure key store and cryptographic functions. The Terminal embeds disassembly switches which protect against disassembly. For example One switch is embedded with the SB and protects the Chip Card Reader; two switches are embedded on the MPCB. The switches are independent from each other and controlled by tamper ports of the SB.

(39) The Main PCB microprocessor is preferably an OMAP4460™ high-performance microprocessor based on the enhanced Cortex™-A9 MPCore with symmetric multiprocessing.

(40) The Secure Controller (SC) of the MPCB is provided preferably by a Maxim chip, the Secure Microcontroller MAXQ1850 (FIG. 2). One functionality of the SC is a first level boot operation and the secure storage of cryptographic keys (NV SRAM).

(41) The security features used by the Secure Controller are

(42) Implementation of Secure Boot

(43) Secure Key Storage (NV SRAM)

(44) Hardware AES and RSA engine

(45) SHA-256 engine

(46) Real time Clock

(47) In order to implement a Secure Boot sequence, the SC has to verify the integrity of the xloader and the u-boot of the MC, which is located in the NAND 2. The NAND 2 flash memory is accessed via an I2C IO-Expander. After verification of these boot components, the SC will start the MC by sending PWR_ON signal to the Power Management Unit.

(48) In the following different Security Measures which shall prevent multiple attacks from different directions like from the Top, Bottom or Side of the terminal are discussed.

(49) The attacker tries to get access to different locations of interest of the MPCB. At least he will get access to the secret authentication key and certificate in order to manipulate parts of the terminal software or he will steel PAN-data.

(50) The terminal housing incorporates three main blocks, Top-Shell (A), Middle-Shell (B) and Bottom-Shell (C) with an optional Printer-Shell. The construction of the terminal bonds A and B in a way that it is impossible to remove part B from part A without interfering with essential functions of the device or without leaving a trace on the top and middle shell of the device. Both parts build in conjunction with active tamper switches the secure zone of the device.

(51) LCD controller and Touch Sensor are in a possible embodiment glued. All secure relevant components of the MPCB (microprocessor, flash memory, USB controller, etc.) are mounted on top between the display and the PCB itself. The components orientation is relatively to the middle of the MPCB in order to prevent a side attack. The disassembly is protected by disassembly switches which are electrically separated from the main PCB. They are connected directly to the security box by a cable. The disassembly switch is an active component which communicates cryptographically with the security box.

(52) The backside of the MPCB offers no attack potential because security relevant conductive path is layout to the inner layers of the MPCB; Interlayer connections to the backside are avoided. Side attacks need special tooling and expert know how of the processor board.

(53) The area of the Magnetic Head is protected by a card reader rail made of spring steel which gives additional EMI/EMC protection. The Magnetic Head itself is an encryption head from MagTek.

(54) The Disassembly switches are used in order to prevent the disassembly of the construction. The switches are components which build the secure zone of the device. Two switches will be directly soldered on the MPCB, one soldered on the SB. The switch has an active component which communicates with the SB over a single wire connection which implements a cryptographic protocol. It uses a SHA-256 hash algorithm to provide a very high level of security. The large key length of 256-bits prevents exhaustive attacks while multiple physical security features prevent unauthorized disclosure of the secret key stored within the device. The key is automatically erased when the power is removed from the encrypted tamper sensor. The device contains a unique 48-bit serial number that is used in combination with an input challenge and the stored secret key to generate a response that is unique for every individual encrypted tamper sensor.

(55) All three switches are independent from each other. The switch is designed to be mounted on the main board and soldered manually.

(56) The multilayered design of the MPCB together with the packaging of critical parts like memory and μC gives protection against drilling attacks from the backside.

(57) The Touch Sensor cable is connected with the SB by a ZIF connector. In order to avoid removal attacks to the connector, the ZIF connector is located inside the Secure Zone and fastened by a squeezed PCB-Frame (D). The round part is a Disassembly Switch.

(58) The Touch Sensor is based on protected capacitive touch (PCAP) which is sensitive to finger touches. The PCAP is also highly sensitive to conductive materials on the surface.

(59) To make an overlay of either another PCAP or resistive touch it will at least contain something like an Indium Tin Oxide (ITO) layer which is conductive. This second conductive layer will interfere significantly with the normal operation of the touch screen.

(60) Besides this the Terminal Touch area is a smooth glass surface that will make any overlay easy to detect and there is no space to hide a pin disclosing bug without it being visible.

(61) The PCI SB Firmware (FIG. 3) consists of the Operating System, Tamper Control, Device Drivers for the Touch Screen, Chip Card Reader Interface and USB Host Controller Interface. It implements functions for Key Management, PIN Encryption, PAN Encryption, Chip Card Handling and Mutual Authentication between SB/MPCB. The PCI SB Firmware is downloadable using encryption and integrity checks and will be approved according PCI PTS 3.1, responsible is the SB Vendor. The USB Composite Device implements a HID device interface for touch events and a COM USB interface for functional level (Key Management, Crypto, PIN, etc.).

(62) The Magnetic Stripe Reader (MSR) firmware consists of functions for Key Management and Data Encryption. The encryption is cryptographically bound between the SB and the MSR.

(63) The software includes a secure boot, Kernel Modules and the Android OS. Application packages are provided by the Acquirer; they include e.g. Payment Apps. The FIG. 4 outlines the software components of the Android stack.

(64) The Android platform is a customized and hardened Android or other Operating System.

(65) Security relevant software components operated on the MPCB are considered as Firmware in PCI terms.

(66) The PCI Terminal Firmware consists of Kernel components, Libraries and Android Runtime. These components will be checked during boot and at least once a day.

(67) It is possible to update Add-On Applications and PCI Firmware. This includes the possibility to update a single file as part of an Application Package or a Device Driver as part of the System Package. It is also possible to update firmware files for the Security Box and NFC Reader. Download and verification of files is controlled by the Terminal Management Agent which is part of the System Package. Files belonging to the Application Package are signed under the responsibility of the Acquirer; files belonging to the System Package are signed under the responsibility of the Terminal Vendor.

(68) During boot sequence (FIG. 5-7) the System Package will be checked for integrity.

(69) The Device Manager distributes all relevant information about the Terminal configuration including parameters, configuration files for payment (BIN tables, AID tables) and binary files. Binary files means APK files with signed application files and updates of system (it means new images of system partition). Terminal management protocol will be based on secured SSL communication with Client and Server based certificates.

(70) The update of Applications is provided by the Package Manager of the Android Software.

(71) The Package Manager will install new or updated APK file which are delivered by the Terminal management system. The Package Manager has to control the APK files in order to avoid re-loading of old packages which can contain security weaknesses. The Application update processes comprises of the following steps:

(72) Download new version of applications (APK files) to data storage

(73) Install new versions of APK files via Package Manager

(74) Package Manager will check signature of APK files and installs files to target application repository. Standard Android key store is used for verification of signature.

(75) Application Package signature is checked every time application process is Created.

(76) An update of the entire system image is also possible. It is done via the same application.

(77) One of the critical points during the lifetime of a secure system is at boot time (FIG. 5,6). Many Attackers attempt to break the software while the device is powered down; performing an attack that, for example, replaces the secure world software image in flash with one that has been tampered with. If a system boots an image from flash, without first checking that it is authentic, the system is vulnerable. One of the principles applied here is the generation of a chain of trust for all terminal software established from a root of trust that cannot easily be tampered with.

(78) The boot process is divided into several parts; first level which is executed is a “Secure Boot” stopping the boot process if a measurement fails (checking of signature). The second level boot is booting the main processor MC and continuing measurement of the entire System Package, stopping the process if the measurement fails. The FIG. 5 draws the principle of the terminals boot sequence.

(79) When the device is powered on, the SC takes the control, the MC is still switched off. The SC boots from its pre-boot loader based in the internal ROM and executes customized ROM code which verifies the x-loader, u-boot and certificates necessary for booting the Android system. These components are located in the NAND2 flash memory. If these components are checked positive, the SC releases the MC by switching the PWR_ON signal. For verification purposes a public key (PuK) and a checksum of the components to be verified is stored in the NV SRAM of the SC; the key is issued by the terminal vendor and loaded in a secure manufacture environment. Customization of the first level boot is impossible, the device always boots from its internal customized ROM code. The code is loaded during device manufacturing in a secure environment of the Terminal Vendor.

(80) The u-boot performs CPU dependent and board dependent initialization and configuration not done in the x-loader. The u-boot also includes an integrity check routine which verifies the System Package. After initialization of the global device list and enabling the interrupts, u-boot loads and starts the Kernel. At this time the Kernel assumes the responsibility and operates checked and verified software components.

(81) The following components of the MC are verified during the first level boot of the SC:

(82) Bootstrapping (x-load.bin.ift)

(83) Boot loader (u-boot.bin)

(84) Certificates

(85) SRAM content

(86) The following components are verified during the second level boot.

(87) Kernel Image (uImage)

(88) Basic Filesystem (rootfs)

(89) PCI Firmware (PCI PTS relevant SW components)

(90) The following Processor signals [7] are relevant for boot configuration and need modifications in order to hard wire the boot location to NAND 2.

(91) This First Level Booter of the SC is customized ROM code which is executed when the device is powered on. It verifies following components which are located in the NAND 2 flash memory.

(92) Root Certificate CertTV

(93) BSP Certificate CertSI

(94) Public device key MSPKauth

(95) NV SRAM content

(96) Binary of x-loader

(97) Binary of u-boot

(98) After successful execution and verification it releases the PWR_ON signal of the Power Management Unit TPS65920. This starts the execution of the MC internal ROM code and forces the loading of the x-loader code which starts the second boot level.

(99) The x-loader is determined by a set of GPIO configuration which can not be changed. It is always located on a fixed address in the NAND 2 flash and it doesn't contain any security measures. The x-loader is responsible for some configuration and loading of the u-boot loader into the internal memory.

(100) The u-boot is derived from the MPCB vendor's u-boot loader and enhanced for verification of the System Package. For verification of the integrity checksums a Vendor Certificate (CertSI) is used. The u-boot verifies the entire System Package.

(101) The Authenticator is a program which is started by the init-process of the Android OS. It has the responsibility to implement a security protocol for mutual authentication with the SB and uses a Crypto API in order to access Key material and crypto functions of the SC.

(102) The security protocol is based on T-DES using a Base Key generated by the SB (Kbk).

(103) Another task is the verification of the System Packages for example every 24 hours.

(104) The Crypto Manager implements the Crypto API which uses the underlying Security Architecture of the SC and provides low level cryptographic functionality to the Payment Provider and Secure HID Driver. For integration of the touch screen the platform provides a USB-HID driver which links the touch controller of the SB to the Android system. The signals are translated by this Kernel Input Device Driver and submitted to the Android EventHub component. The Android InputReader component then decodes the input events according to the device class (HID) and produces a stream of Android input events. As part of this process, the Linux input protocol event codes are translated into Android event codes according to the input device configuration, e.g. various mapping tables. At the end the input reader sends the events to the input dispatcher and hence to the top application window. The HID driver in a possible embodiment doesn't implement en-/decryption. During PIN entry no touch events are submitted. So far this behavior is standard Android behavior and has no impact to the Add-On Application development. One restriction exists; the platform verifies the integrity of security relevant software components. If the verification is positive, the platform sends a notification to the SB embedded into a mutual authentication protocol. This notification will force the SB to release the submission of touch events to the MPCB. If the authentication or the integrity checks failed, no events will be submitted and the device will be powered down.

(105) The SB Crypto Driver provides the low level USB interface to the SB. It implements active cryptography analogue to the Secure HID Driver and communicates with the SB. It provides low level functions to the Payment provider.

(106) The Payment provider is a set of components which provides a common interface for all applications which need payment functionality or security functionality. The following describes the high level functionality of the Payment Provider.

(107) It provides interface relevant to EMV (Europay, MasterCard and Visa) transaction processing. This interface serves a common high level building block for payment application which covers the following.

(108) Application selection (reading EMV applications, process candidate list regarding to configured applications in AID configuration table.

(109) Offline processing—processes reading of records from ICC card, checking necessary data. It process also SDA, DDA, CDA authentication and CVM processing (handling of offline or online PIN entry) and terminal risk management steps.

(110) 1st Cryptogram—processing of 1st cryptogram task regarding to results gathered by Offline processing

(111) 2nd Cryptogram—in case of transaction which are done in Online mode 2.sup.nd cryptogram generates final cryptogram calculation after (successful or unsuccessful) online communication, it handles processing of critical and uncritical EMV script.

(112) The whole transaction processing is responsibility of payment application. Handling of offline/online transaction process and printing have to be processed by Payment application.

(113) EMV Contact Less interface (PayPass, PayWave) provides the interface for contactless cards processing. Contactless cards are processed regarding to rules defined in EMV Book A and B using the PayPass or PayWave kernels. It means that there are processed all steps which are mandatory for successful transaction.

(114) Read record processing

(115) Generation of cryptogram

(116) Processing of CVM list or CTQ and TTQ indicators

(117) The whole transaction processing is responsibility of payment application. The CVM processing, printing and handling of offline/online transaction process have to be processed by the Payment application.

(118) The Card reader interface Provides interface for relevant card reading functions which depends on used card media types.

(119) For magnetic stripe card it provides information about read data (Track 1, Track 2, Track 3) and detection of swiped card.

(120) For ICC interface it provides possibility to detect insertion of card to card reading slot, to process EMV reset (include the handling of necessary data) and low level interface (on APDU base) which can be used for non EMV cards or for handling any special local enhancements of standard EMV cards.

(121) Contact less cards can be detected via this interface; interface provides additionally information about detected card (payment cards are then processed by EMV Contact Less interface). For non standard or private contact less cards can be used direct pass-through interface which uses low level data protocol.

(122) The Secure Storage Interface is used to store secure relevant Payment data in rest, e.g. for storing offline transactions or store and forward queues. For the data storing the standard flash internal memory of main PCB board (data partition) is used, but all data are encrypted by two level of keys.

(123) The Security Interface provides an interface for standard security functions used during transaction processing or during communication with the payment backend system.

(124) MAC interface

(125) interface for calculating MAC codes of messages

(126) Key Loading Interface

(127) Encryption interface

(128) For Key Management (KMS) purpose the Terminal provides DUKPT [14] and CBA [4] specific functions in order to adapt the Payment Application to KMS.

(129) The PIN Interface is used for PIN handling functions and PIN block encryption functions. It is used during offline PIN handling process (clear text PIN processing, enciphered offline PIN processing) and Online PIN processing.

(130) Offline clear text PIN process (used by EMV transaction interface)

(131) Offline enciphered PIN process (used by EMV transaction interface)

(132) Online enciphered PIN process (used by common transaction processing parts and EMV transaction interface), it is divided to two parts

(133) PIN entry process and PIN block calculation and retrieving task.

(134) The Payment App (Application) is built on top of standard Android interfaces and on custom Payment provider interfaces. The Payment application implements all necessary steps for processing successful payment transaction requested by the customer (acquirer). Main responsibilities are the following.

(135) Process input of all necessary data for transaction (merchant inputs)

(136) Process of card reading and card processing tasks (there is used Payment provider)

(137) Process transaction accordingly to transaction flow requested by card scheme or card media type (ICC, contact less, mag. Stipe).

(138) These steps includes PIN entry processing, EMV or Contact Less processing, risk management processing

(139) Application is responsible for communication with host and for implementation of host protocol interface.

(140) Application is responsible for implementation of ECR protocols used for integration with Cash registers.

(141) An application collects data about transactions and prepares data for Close of the day process (in case of dual-message systems uses store and forward queues protected by Security interface of Payment provider).

(142) In addition to the Payment App a set of Value added applications can be installed on the device. The prompt control of these Apps is under the responsibility of the Terminal Acquirer. These Apps deliver additional functionality and more convenience to the merchant like

(143) Dynamic Currency Conversion (DCC)

(144) Point Of Sale/Electronic Cash Register integration capability

(145) Simple Split Bill

(146) etc.

(147) This application allows the capture of cash and cheque purchases and provides the merchant information about all purchases from a terminal, including the card, cash and cheque purchases.

(148) The Security Concept allows also the services provided by Google Wallet. The device acts as a NFC reader device which will be approved with the Mastercard PayPass payment method.

(149) The Terminal will be equipped with a central logging service. The log-information is written to a file which can be transferred to the Terminal Management System. There are several Security Controls which can be reported by means of the Terminal Management Agent; further information is in “Security Controls” in Section “Terminal Life Cycle”.

(150) The TMS Agent is responsible to manage a Terminal installed in the network. It delivers information about the actual HW and SW status of the terminal and is further responsible for downloading Add-On Applications and PCI Firmware. It interacts with the central TMS System. In principle the TMS Agent provides the Terminal Data to a Device Manager which is operated by the Sponsor. The Device Manager Downloads the Terminal Settings to the Terminal. The TMS Agent collects security information which can be analyzed by e.g. the Device Manager. The exact information and structures will be specified in a separate document. The following information is intended to provide but is not limited to this list.

(151) After Power On (FIG. 7), the default modus of the SB is the Secure Mode, which prevents the SB from submitting touch events. After Secure Boot with successful verification of the System Package, the Terminal processes a mutual authentication with the SB, the Authenticator is responsible. After successful authentication the SB is transferred into Clear Text Mode which allows the submission of touch events.

(152) The Process which is responsible for mutual authentication is started by the init-program of the Android System. The mutual authentication is based on the Pkauth and Skauth and the Terminal Vendor Certificate.

(153) The Clear Text Mode is terminated when the terminal is powered off or a defined time frame is exhausted (24 h); the time frame is controlled by the Terminal Management Agent. For PIN entry the SB is transferred into the Secure PIN Mode, no PIN codes or touch events are transmitted via the HID class except replacement coordinates. A Payment Application which starts the Secure PIN Mode needs to authenticate with the SB using a cryptographic key which is generated by the SB and transferred to the payment application during registration. Registration is the process when the HID device driver and the generic USB device driver register to the security box. The Secure PIN Mode is terminated when a function key (Cancel, Clear) is pressed, or the maximum PIN characters are entered by the cardholder. The following state diagram outlines the different modes.

(154) The Android mobile platform was designed to be open to all kind of applications development which makes use of advanced hardware and software. The applications executed on the Terminal Platform must rely on this architecture provided; additionally specific platform hardening will be applied and described in the chapter Android Hardening. The Android Platform Security Architecture consists of the following key security features.

(155) Linux Kernel which shall provide robust security to the OS

(156) Application Sandboxing

(157) Secure interprocess communication

(158) Application-defined and user-granted permissions

(159) A general description of the Android Security Platform is provided on the developer's page http://source.android.com/tech/security/index.html

(160) The following components interact with the security boundary of the Terminal.

(161) For the device a switchable Privacy Filter is used. The switchable filter is operated in combination of a random shifted soft PIN Pad displayed on the screen. The LCD panel will be covered by a transparent foil. Lenses integrated in the foil focus the light of selected sub pixels in a limited solid protection angle in compliance with the requirements for attended devices [2]. The outside of this solid angle information from these sub pixels is not visible.

(162) In normal mode all pixels of the LCD panel are active. The information will be visible from all sides. In pin entry mode only the selected sub pixels with lenses will be used to show the virtual PIN Pad on the screen. Only the user who enters the PIN and looks perpendicular to the screen can see the virtual PIN Pad. It is possible that a small part of the screen is in normal mode and another part is in PIN entry mode at the same time. For technical reasons the PIN Pad can be shown monochrome only. Resolution and brightness of the screen in PIN entry mode is limited because only a subset of pixels will be used.

(163) The size and position of the PIN Pad on the screen is flexible and will randomly vary with every transaction. Without the information from the screen it will be impossible to spy out the PIN with detection of the finger position on the touch screen. It is recommended to show only the numeric keys in Pin entry mode and the function keys at a fixed position on the screen in normal mode.

(164) The combination of the camera optics (viewing angle) and the placement of the camera prevent from spying finger positions during PIN entry mode.

(165) Sensor Events are submitted from the kernel driver to the Dalvik and are presented in the class Sensor Event. All values are in radians/second and measure the rate of rotation around the device's local X, Y and Z axis. This might be used from a software based PIN disclosing bug which displays a virtual PIN pad on the screen by measuring the rate of rotation during PIN entry instead of receiving touch events. The following measures prevent against installation of a software based PIN disclosing Bug.

(166) The Terminal executes only acquirer signed applications. These Apps are qualified, signed and under control of the acquirer. Installation of unknown Apps is prevented by the integrity measurement system of the Terminal during its Boot Sequence. A hardware based attack is out of scope.

(167) The following Communication Devices can be included in the Hardening Concept.

(168) PCIE 3G Module

(169) Ethernet IF Module

(170) WiFi, BlueTooth, GPS

(171) The vendor of the terminal is responsible for System Package Signing and embeds a certificate CertSI in the Boot Loader for verification. The Boot Loader itself is verified by using a different public key which is embedded in the NV SRAM of the SB controller.

(172) The Android system requires that all installed applications be digitally signed with a certificate whose private key is held by the issuer of the application.

(173) The Android system uses the certificate as a means of identifying the author of an application and establishing trust relationships between applications. The certificate is used to control which applications the issuer can install. The techniques that are used according Key Life Cycle and related services are in compliance of ISO 11568-2 and ANSI X9.24. For device key management symmetric and asymmetric cryptography for different purpose is applied. The minimum key sizes and parameters for the algorithms provided by the terminal follow the PCI requirements.

LIST OF REFERENCE NUMERALS

(174) [1] PIN Transaction Security Point of Interaction, Ver. 3.1 Oct. 2011 PCI Modular Security Requirements [2] PIN Transaction Security Point of Interaction, Ver. 3.1 Oct. 2011 PCI Modular Derived Test Requirements [3] Encrypting USB Intellihead, Technical Reference Manual, 99875370-2 MagTek April 2009 [4] CBA EFTPOS Specification, Ver. 1.5 Aug. 2006 Commonwealth Bank of Australia [7] OMAP4460 Multimedia Device Silicon Revision 1.0 Q, Texas Instruments [8] Maxim MAXQ1850 Data sheet. [9] H26M52002CKR eMMC Memory HYNIX data sheet [14] ANSI X9.24-1, Retail Financial Services Symmetric Key Management