WO2018040972A1

WO2018040972A1 - Method and system for improving application security of payment terminal

Info

Publication number: WO2018040972A1
Application number: PCT/CN2017/098252
Authority: WO
Inventors: 吴旋
Original assignee: 福建联迪商用设备有限公司
Priority date: 2016-08-31
Filing date: 2017-08-21
Publication date: 2018-03-08
Also published as: CN106372496A

Abstract

A method for improving application security of a payment terminal, and apparatus for same. The method comprises: pre-configuring permissions of an application program, and generating a permission list corresponding to the application program; an issuer digitally signing the application program and the permission list thereof; after a terminal authenticates the digital signature, acquiring the application program and the permission list thereof, and allocating an identifier to the application program; establishing an association relationship of the application program, identifier, and permission list; when the application program calls a function related to a payment operation, the terminal acquiring the identifier of the application program; the terminal acquiring, according to the association relationship, the permission list corresponding to the identifier; and the terminal determining, according to the permission list, whether the application program has the permission to call said function. The method of the present invention establishes, on the basis of coordination between a signing tool, a permission management service, and a device driver back-end service, a permission management mechanism for third-party application programs, thus achieving permission management of third-party applications, and improving payment security of terminals.

Description

Description: Method and system for improving security of payment terminal application

[0001] The present invention relates to the field of secure payment, and in particular, to a method and system for improving security of a payment terminal application.

[0002] Currently, terminals used in the payment field basically support multiple applications. With the introduction of intelligent terminals, the terminal customers, in addition to self-issuing applications, also commission third-party application software, such as: Invoicing system, navigation /Map service, etc.

[0003] The application scenarios of the terminal customers are basically payment-related applications, and financial security needs to be considered. Therefore, if third-party application software is installed on the terminal, there may be security vulnerabilities due to problems such as low security awareness of third-party applications, and there may be malicious use of payment-related devices. This requires the security of third-party applications.

[0004] At present, customers can only guarantee the security of third-party software used by reviewing the source code of third-party application software or by signing an agreement with a third party. However, the above methods have the following disadvantages: 1. Third-party applications are mostly complicated, and it is difficult to determine their security risks by auditing source code. 2. Some third-party application senders are unwilling to release source code to terminal owners for commercial secrets. 3, even if the signing of a security risk agreement, it is only after the occurrence of security problems, can not effectively prevent security problems.

[0005] Therefore, it is necessary to provide a method and system for improving the security of a payment terminal application.

technical problem

The technical problem to be solved by the present invention is to provide a method and system for improving the security of a payment terminal application, and effectively prohibiting a third party application from illegally using the payment related function.

Problem solution

Technical solution

[0007] In order to solve the above technical problem, the technical solution adopted by the present invention is:

[0008] A method for improving security of a payment terminal application includes:

[0009] presetting the permission of the application, generating a permission table corresponding to the application; [0010] The publisher digitally signs the application and its permission table;

[0011] after the terminal verifies that the digital signature is passed, acquiring the application and its permission table, and assigning an identifier to the application;

[0012] establishing an association relationship between an application, an identifier, and a permission table;

[0013] when the application invokes a function related to the payment operation, the terminal acquires the identifier of the application;

[0014] the terminal acquires the permission table corresponding to the identifier according to the association relationship;

[0015] The terminal determines, according to the permission table, whether the application has the right to invoke the function.

[0016] Another technical solution provided by the present invention is:

[0017] A system for improving security of a payment terminal application, comprising:

[0018] a generating module, configured to preset a permission of the application, and generate a permission table corresponding to the application;

[0019] a signature module, configured by the publisher to digitally sign the application and its permission table;

[0020] an allocation module, configured to: after the terminal verifies that the digital signature is passed, obtain the application and its permission table

And assigning an identifier to the application;

[0021] an association module, configured to establish an association relationship between an application, an identifier, and a permission table;

[0022] a first obtaining module, configured to: when the application invokes a function related to the payment operation, the terminal acquires an identifier of the application;

[0023] a second obtaining module, configured to acquire, according to the association relationship, a permission table corresponding to the identifier; [0024] a determining module, configured to determine, according to the permission table, whether the application has the call Functional permissions.

Advantageous effects of the invention

Beneficial effect

[0025] The beneficial effects of the present invention are as follows: There is a problem that there is an insecure factor in the third-party application software used by the terminal in the prior art. The present invention provides a method and device for improving the security of a payment terminal application. The publisher pre-determines the permission table of the third-party application, and then obtains the third-party application securely in the terminal, and obtains the corresponding permission table in the third-party application. After calling the payment related function, it can judge whether the operation is allowed according to the permission table, realize the authority management of the third party application, effectively prohibit the third party application from illegally using the payment related function, and ensure the payment security of the terminal.

Brief description of the drawing DRAWINGS

1 is a schematic flow chart of a method for improving security of a payment terminal application according to the present invention;

2 is an information interaction diagram according to an embodiment of the present invention;

3 is a schematic structural diagram of a system for improving security of a payment terminal application according to the present invention;

4 is a schematic structural diagram of a system for improving security of a payment terminal application according to an embodiment of the present invention.

[0030] Description of the label:

[0031] 1, a generating module; 2, a signature module; 3, an allocation module; 4, an associated module;

[0032] 5, the first acquisition module; 6, the second acquisition module; 7, the determination module; 8, call the module

[0033] 51, the notification unit; 52, the acquisition unit; 71, the determination unit; 72, the return unit;

[0034] 73, an allocation unit.

detailed description

[0035] The most important idea of the present invention is: After the third party application invokes the payment related function, it determines whether there is a calling right according to the permission table preset by the publisher, and ensures the payment security of the terminal.

[0036]

[0037] The technical terms involved in the present invention are explained:

[]

[Table 1]

If the requested function corresponds to your operation, the identifier corresponds to the operation handle.

[0038]

Referring to FIG. 1 and FIG. 2, the present invention provides a method for improving security of a payment terminal application, including: [0040] presetting a permission of an application, and generating a permission table corresponding to the application;

[0041] The publisher digitally signs the application and its permission table;

[0042] after the terminal verifies that the digital signature is passed, acquiring the application and its permission table, and assigning an identifier to the application;

[0043] establishing an association relationship between the application, the identifier, and the permission table;

[0044] When the application invokes a function related to the payment operation, the terminal acquires the identifier of the application; [0045] the terminal acquires the permission table corresponding to the identifier according to the association relationship;

[0046] The terminal determines, according to the permission table, whether the application has the right to invoke the function.

[0047] As can be seen from the above description, the present invention has the following advantages: On the basis of the application rights management mechanism of the terminal operating system, the rights to the payment device and the security-sensitive operation are expanded. After the third-party application is installed, the operation authority of the application declared by the signed publisher is obtained, and the security of the declaration is ensured during the transmission; the third-party application calls the payment related function, and the verification is performed according to the above statement to ensure the terminal's Payment security.

[0048] Further, determining, according to the permission table, whether the application has permission to invoke the function

After that, further include:

[0049] if yes, allowing the application to invoke the function;

[0050] If not, the application is not allowed to invoke the function.

[0051] As can be seen from the above description, only the terminal verifies that the third-party application has the right to legally invoke the function related to the payment operation, so that the calling operation of the third-party application can be allowed to ensure that the operation of the third-party application is within the legal range.

[0052] Further, when the application invokes a function related to the payment operation, the terminal acquires the identifier of the application; the terminal acquires the permission table corresponding to the identifier according to the association relationship, according to the permission table. Determining whether the application has permission to invoke the function, specifically:

[0053] when the application invokes a function related to the payment operation, notifying the device to drive the background service; [0054] the device driver background service acquires the identifier of the application, and sends the identifier to the rights management service

[0055] the rights management service obtains the permission table corresponding to the identifier according to the association relationship;

[0056] the rights management service determines, according to the permission table, whether the application has permission to invoke the function;

[0057] The rights management service returns the determination result to the device driver background service.

[0058] It can be seen from the above description that through the cooperation of the signature tool, the terminal rights management service, and the terminal device driving the background service, the third party application authority is managed, and the third party application illegally uses the payment related function, thereby ensuring the payment terminal. Application security.

[0059] Further, the rights management service returns the determination result to the device driver background service, and then further includes:

[0060] The device driver background service determines, according to the determination result, whether to allocate the device/operation handle corresponding to the function to the application.

[0061] It can be seen from the above description that the device-driven background service determines whether to allocate a third-party application device/operation handle according to the determination result of the rights management service; if the third-party application cannot obtain the device/operation handle, the operation of the payment-related function cannot be performed. Therefore, the operation of the third-party application is effectively controlled, and the legality of the operation of the third-party application is guaranteed from the root cause.

[0062] Further, the identifier is a user ID.

[0063] It can be seen from the above description that when the terminal downloads and acquires the third-party application and its permission table, the peer assigns a user ID to it, and establishes a third-party application, a permission table, and a third-party application corresponding user ID. The association provides a basis for subsequently calling the permission table of the third-party application, and realizing the quick and accurate permission for obtaining the preset of the third-party application.

[0064] Referring to FIG. 3 and FIG. 4, another technical solution provided by the present invention is:

[0065] A system for improving the security of a payment terminal application includes:

[0066] The generating module 1 is configured to preset a permission of the application, and generate a permission table corresponding to the application;

[0067] a signature module 2, configured for the publisher to digitally sign the application and its permission table;

[0068] The distribution module 3 is configured to: after the terminal verifies that the digital signature is passed, obtain the application and its permission table, and assign an identifier to the application;

[0069] an association module 4, configured to establish an association relationship between an application, an identifier, and a permission table; [0070] The first obtaining module 5 is configured to: when the application invokes a function related to the payment operation, the terminal acquires an identifier of the application;

[0071] The second obtaining module 6 is configured to acquire, by the terminal, the permission table corresponding to the identifier according to the association relationship; [0072] the determining module 7 is configured to determine, by the terminal, whether the application has a call according to the permission table. The permissions of the function.

[0073] Further, the method further includes:

[0074] The calling module 8 is configured to allow the application to invoke the function if the determination result obtained by the determining module is YES, and to not allow the application to be determined if the determining result obtained by the determining module is negative Call the function.

[0075] Further, the first acquiring module 5 includes:

[0076] the notification unit 51 is configured to notify the device to drive the background service when the application invokes a function related to the payment operation;

[0077] The obtaining unit 52 is configured to: acquire, by the device-driven background service, an identifier of the application, and send the identifier to the rights management service;

[0078] The second obtaining module 6 is specifically configured to acquire, according to the association relationship, a permission table corresponding to the identifier according to the association relationship;

[0079] The determining module 7 includes:

[0080] determining unit 71, configured to determine, by the rights management service, whether the application has the right to invoke the function according to the permission table;

[0081] The returning unit 72 is configured to return the determination result to the device driver background service by the rights management service.

[0082] Further, the determining module 7 further includes:

[0083] The allocating unit 73 is configured to determine, according to the determining result, whether to allocate the device/operation handle corresponding to the function to the application according to the determining result.

[0084] Further, the identifier is a user ID.

Embodiment 1

[0086] Please refer to FIG. 2, this embodiment provides a method for improving the security of a payment terminal application, which is applicable to a terminal device having a payment function, in particular, a payment terminal that introduces a third-party application, which can well protect the terminal. Payment security. [0087] The method can include the following steps:

[0088] S1: The third-party application publisher declares that the published application may use the payment-related function during use, and corresponds to the permission corresponding to the relevant function setting, and generates a permission table corresponding to the application; The permission table lists whether the IC card, magnetic card, RF card, and print can be used; whether to allow the PIN to be entered; whether to allow the use of payment related functions such as downloading keys; for example, for the invoicing software, disable all payment related functions, Including safety related, card type, printing, etc.

[0089] S2: The publisher digitally signs the application and its permission table; specifically, the permission table may be placed at the end of the application for overall digital signature; this step is used to download the third-party application to the terminal, The terminal verifies that the third party application has been tampered with. Here, the permission table is also digitally signed, which not only ensures the security of the third-party application acquired by the terminal, but also ensures the security of the permission table of the third-party application declared by the publisher, and ensures its security. Not illegally tampering;

[0090] S3: the terminal downloads the foregoing application, and for the terminal, the application is a third-party application; the terminal acquires the digitally signed third-party application and its permission table;

[0091] S4: The terminal verifies the signed third-party application and its permission table according to the key that is legally obtained from the publisher in advance; if the verification is passed, the third-party application and its permission table are obtained, and the terminal is proved to have Higher security; continue to execute S5; if the verification fails, it proves that there is an insecure factor in the third-party application or its permission table, and the third-party application fails to be installed;

[0092] S5: The terminal allocates a unique identifier to the obtained third-party application; preferably, the identifier is a user ID; each application in the Android operating system may be isolated from each other, and each application The program can have a separate Linux user ID and group ID, so the user ID is used as the unique identifier of the third-party application to distinguish different applications;

[0093] S6: establishing an association relationship between the acquired third application and its permission table and user ID; preferably, storing the association relationship into the association table; and storing, in the association table, different third-party applications Associated information;

[0094] S7: When a third-party application is executed, a function of payment related operations is needed, and the terminal system performs a permission check, and obtains a relationship from the association relationship according to the user ID of the third-party application. Determining the permission table corresponding to the user ID; and then determining, according to the permission table, whether the third-party application has the right to legally invoke the above function; [0095] Preferably, step S7 may include the following sub-steps:

[0096] S71: When the application invokes a function related to the payment operation, the device driver is required to drive the background service to perform the corresponding operation; for example, the RF card is used to acquire the device handle;

[0097] S72: the device driver background service first obtains the user ID of the application, and then sends the user ID to the rights management service check permission;

[0098] S72: The rights management service obtains, according to the user ID, the permission table corresponding to the user ID from the stored association relationship; that is, the application that invokes the function is installed in the permission table;

[0099] S73: The rights management service determines, according to the permission table, whether the application has permission to invoke the function.

If it is determined whether the application has the right to use the RF card; if not, execute S74; if yes, execute S75;

[0100] S74: The rights management service returns a determination result that does not allow the operation to the device driver background service. For example, for a device operation, the device driver background service does not assign a device handle to the application, but directly returns an error; since the application cannot obtain the device handle of the RF card, subsequent RF card operations cannot be performed.

[0101] S75: the rights management service returns a determination result of the permission operation to the device driver background service; the device driver background service allocates a device handle to the third party application; the third party application uses the device handle for subsequent operations.

[0102] It should be noted that most of the peripheral devices are in the device, and the device drives the background service to check the permissions. After the device handle is assigned to the application, the application can use the device handle to perform subsequent peripheral operations. However, some devices need to subdivide different operation rights. Therefore, in addition to checking the permissions of the device, some operations will also perform permission checks. If the permission check fails, the device driver background service will not perform the operation. Return an error to the application. For example: PINPAD devices, in addition to accessing PINPAD device rights, also control whether PIN entry is possible. In this way, in addition to the PINPAD device, there is a permission check. When the application calls the API for PIN input, the permission check is also performed. If the permission check fails, an error is returned, and the PIN input operation is not executed. .

[0103] In this embodiment, based on the cooperation between the signature tool, the rights management service, and the device driver background service, a rights management mechanism for the third-party application is established, and the rights management of the third-party application is implemented, so that the third-party application is implemented. Restricted when using payment-related functions, avoiding the payment terminal being introduced After the application of the three parties, it is misused or misused, resulting in the loss of people's property. At the same time, it is not necessary to spend a lot of energy and financial resources to conduct source code audits on third-party applications, and to improve the security of terminal payment, and to save resources.

Embodiment 2

[0105] Please refer to FIG. 4, the embodiment provides a system for improving security of a payment terminal application, including:

[0106] The generating module 1 is configured to preset a permission of the application, and generate a permission table corresponding to the application; [0107] a signature module 2, configured to perform digital signature on the application and its permission table by the publisher;

[0108] The distribution module 3 is configured to: after the terminal verifies that the digital signature is passed, obtain the application and its permission table, and assign an identifier to the application;

[0109] an association module 4, configured to establish an association relationship between an application, an identifier, and a permission table;

[0110] a first obtaining module 5, configured to: when an application invokes a function related to a payment operation, the terminal acquires an identifier of the application;

[0111] The second obtaining module 6 is configured to acquire, by the terminal, the permission table corresponding to the identifier according to the association relationship; [0112] the determining module 7 is configured to determine, by the terminal, whether the application has a call according to the permission table. The permissions of the function.

[0113] also includes:

[0114] a calling module 8 is configured to allow the application to invoke the function if the determination result obtained by the determining module is YES; and to not allow the application to be determined if the determining result obtained by the determining module is negative Call the function.

[0115] Preferably, the first acquiring module 5 includes:

[0116] the notification unit 51 is configured to notify the device to drive the background service when the application invokes a function related to the payment operation;

[0117] The obtaining unit 52 is configured to acquire, by the device-driven background service, the identifier of the application, and send the identifier to the rights management service. Preferably, the identifier is a user ID.

[0118] The second obtaining module 6 is specifically configured to acquire, according to the association relationship, a permission table corresponding to the identifier according to the association relationship;

[0119] The determining module 7 includes:

[0120] a determining unit 71, configured to determine, by the permission table, whether the application has the call Functional authority;

[0121] The returning unit 72 is configured to return the determination result to the device driver background service by the rights management service.

[0122] Preferably, the determining module 7 further includes:

[0123] The allocating unit 73 is configured to determine, by the device driving background service, whether to allocate the device/operation handle corresponding to the function to the application according to the determining result.

[0124] In summary, the method and device for improving the security of a payment terminal application provided by the present invention not only save the review process of the third-party application source code, but also save manpower and material resources; and belong to pre-verification and effectively prevent security. The problem occurs. Further, the present application does not need to introduce additional equipment, and directly uses the existing configuration of the terminal to perform authority control, which not only improves the versatility of the present invention, but also its security and simplicity are self-evident.

[0125]

Claims

Claim

[Claim 1] A method for improving security of a payment terminal application, comprising:

Presetting the permissions of the application, generating a permission table corresponding to the application;

The publisher digitally signs the application and its permission table;

After the terminal verifies that the digital signature is passed, the application and its permission table are obtained, and an identifier is assigned to the application;

Establish associations between applications, identities, and permission tables;

When the application invokes a function related to the payment operation, the terminal acquires the identification of the application;

The terminal obtains the permission table corresponding to the identifier according to the association relationship;

The terminal determines, according to the permission table, whether the application has the right to invoke the function.

[Claim 2] The method for improving security of a payment terminal application according to claim 1, wherein the determining, according to the permission table, whether the application has permission to invoke the function, and further comprising :

If yes, allowing the application to invoke the function;

If not, the application is not allowed to invoke the function.

[Claim 3] The method for improving security of a payment terminal application according to claim 1, wherein when the application invokes a function related to a payment operation, the terminal acquires an identifier of the application; In the association relationship, the terminal obtains the permission table corresponding to the identifier, and determines, according to the permission table, whether the application has the permission to invoke the function, specifically:

When the application invokes a function related to the payment operation, notifying the device to drive the background service; the device driver background service acquires the identifier of the application, and sends the identifier to the rights management service;

The rights management service obtains the permission table corresponding to the identifier according to the association relationship; the rights management service determines, according to the permission table, whether the application has the right to invoke the function;

The rights management service returns the determination result to the device driver background service.

[Claim 4] The method for improving security of a payment terminal application according to claim 3, wherein the rights management service returns a determination result to the device driver background service, and then further includes:

The device driver background service determines, according to the determination result, whether to allocate the device/operation handle corresponding to the function to the application.

[Claim 5] The method for improving security of a payment terminal application according to claim 1, wherein the identifier is a user ID.

[Claim 6] A system for improving the security of a payment terminal application, comprising:

a generating module, configured to preset a permission of the application, and generate a permission table corresponding to the application;

a signature module, configured to perform a digital signature on the application and its permission table by the publisher; and an allocation module, configured to: after the terminal verifies the digital signature, obtain the application and its permission table, and assign a Identification

An association module, configured to establish an association relationship between the application, the identifier, and the permission table; a first obtaining module, configured to: when the application invokes a function related to the payment operation, the terminal obtains the identifier of the application;

a second obtaining module, configured to acquire, according to the association relationship, a privilege table corresponding to the identifier;

And a determining module, configured by the terminal, according to the permission table, to determine whether the application has the right to invoke the function.

[Claim 7] The system for improving the security of a payment terminal application according to claim 6, further comprising:

Calling a module, if the determining result obtained by the determining module is yes, allowing the application to invoke the function; and if the determining result obtained by the determining module is negative, the application is not allowed to invoke the function .

[Claim 8] The system for improving security of a payment terminal application according to claim 6, wherein the first obtaining module comprises:

a notification unit, configured to notify the device driver when the application calls a function involving a payment operation Background service;

An obtaining unit, configured to: acquire, by the device-driven background service, an identifier of the application, and send the identifier to the rights management service;

The second obtaining module is specifically configured to acquire, according to the association relationship, the permission table corresponding to the identifier;

The determining module includes:

a determining unit, configured to determine, by the permission table, whether the application has permission to invoke the function according to the permission table;

The return unit is used by the rights management service to return the determination result to the device driver background service.

[Claim 9] The system for improving security of a payment terminal application according to claim 8, wherein the determining module further comprises:

And an allocating unit, configured to determine, by the device driving background service, whether to allocate the device/operation handle corresponding to the function to the application according to the determining result.

[Claim 10] The system for improving security of a payment terminal application according to claim 6, wherein the identifier is a user ID.