Application software security starting method and computer readable storage medium

Abstract

The invention discloses an application software security starting method and a computer readable storage medium, and the method comprises the steps that when application software is started, terminal equipment obtains the state of the application software; if the state of the application software is a preset state, the terminal device and the application server side obtain a new key, and the preset state comprises a first starting state and a risk state; the terminal device obtains to-be-evaluated data, the to-be-evaluated data comprises terminal data, application operation data and key updating data, the to-be-evaluated data is encrypted through the new key, and a ciphertext obtained through encryption is sent to the application server; after receiving the ciphertext, the application server decrypts the ciphertext through a new key to obtain data to be evaluated; the application server performs risk assessment on the to-be-assessed data to obtain a risk value, and executes a corresponding risk strategy according to the risk value, and the risk strategy comprises risk prompting, key updating and limiting operation. According to the invention, safe starting of the application software is realized.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method for securely starting application software and a computer-readable storage medium. Background Art

[0002] At present, in certain industries, such as government departments and financial departments, user information security is very important. How to flexibly restrict the use of application software and protect user information security is very important. At present, when application software is installed on tablets or specific devices, there are usually the following problems:

[0003] Question 1: Designated devices can install non-designated application software. Non-designated application software may obtain the interaction data of some application software through various means, which poses potential risks.

[0004] The second problem is that designated application software can be installed on non-designated devices, and it is impossible to monitor whether there are illegal operations or whether user information is illegally obtained.

[0005] Question three: The specified application software is installed on the specified device, but the execution of the application software is not recorded, making it impossible to confirm whether there is any login at an irregular time or some illegal operations.

[0006] Question 4: In the current application software management, even if application risk items are monitored, releasing the risk items after legal verification requires cumbersome operations and is not smart enough.

[0007] Therefore, how to limit the secure startup of application software in specific industry sectors is an urgent matter.

[0008] Currently, there are several common methods for limiting the launch of application software on devices:

[0009] Solution 1: Add a module to the device. For example, configure a unique medium for storing keys on a tablet, such as an SD card or PSAM card. One or more sets of keys are stored in the unique medium for storing keys (hereinafter referred to as key medium). When the application software is started, the key in the key medium is read for device authentication. This approach can limit the installation of application software to a certain extent. However, when using legal key media on other illegal terminal devices, the specified application software can still be installed, and there is still a risk of user information leakage. That is, different key media are easy to switch, and the security of user information cannot be ensured. At the same time, the cost of the key medium will also increase the cost of the equipment.

[0010] Solution 2: Use whitelist management and user information management to control. Whitelist management determines the legitimacy of the application software by judging the package name or digital signature of the application software. The login information includes the user's account, password, fingerprint information, work badge information, etc., to verify whether the user information of the application software is compliant. This method can protect user information security to a certain extent in a secure device environment. However, it cannot ensure whether there is illegal monitoring. That is, if the security of the device environment cannot be ensured, there is also a risk of user information leakage. Summary of the invention

[0011] The technical problem to be solved by the present invention is to provide a method for securely starting application software and a computer-readable storage medium, which can realize the secure starting of application software.

[0012] In order to solve the above technical problems, the technical solution adopted by the present invention is: a method for securely starting application software, comprising:

[0013] When the application software is started, the terminal device obtains the status of the application software;

[0014] If the state of the application software is a preset state, the terminal device and the application server obtain a new key, and the preset state includes the first startup state and the risk state;

[0015] The terminal device obtains the data to be evaluated, which includes terminal data, application operation data and key update data, encrypts the data to be evaluated by using the new key, and sends the encrypted ciphertext to the application server;

[0016] After receiving the ciphertext, the application server decrypts the ciphertext using the new key to obtain the data to be evaluated;

[0017] The application server performs risk assessment on the data to be assessed, obtains a risk value, and executes a corresponding risk strategy according to the risk value. The risk strategy includes risk warning, key update and restricted operation.

[0018] The present invention also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the method described above is implemented.

[0019] The beneficial effects of the present invention are as follows: by detecting the status of the application software, updating the key in time, and realizing data encryption transmission between the terminal device and the application server through the key, the communication security between the terminal device and the application server can be guaranteed, and the user information security can be ensured; by performing risk assessment on multiple data and executing corresponding risk strategies based on the risk values, it is possible to comprehensively judge whether it is safe to start the application software, ensure the safety of the device environment, and thus realize the safe startup of the application software. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 A flowchart of a method for securely starting application software of the present invention;

[0021] Figure 2 A schematic diagram of a secure boot architecture for application software according to a first embodiment of the present invention;

[0022] Figure 3 This is a flow chart of a method according to Embodiment 1 of the present invention. DETAILED DESCRIPTION

[0023] In order to explain the technical content, achieved objectives and effects of the present invention in detail, the following is a detailed description in conjunction with the implementation methods and the accompanying drawings.

[0024] See also Figure 1 , a method for securely starting application software, comprising:

[0025] When the application software is started, the terminal device obtains the status of the application software;

[0026] If the state of the application software is a preset state, the terminal device and the application server obtain a new key, and the preset state includes the first startup state and the risk state;

[0027] The terminal device obtains the data to be evaluated, which includes terminal data, application operation data and key update data, encrypts the data to be evaluated by using the new key, and sends the encrypted ciphertext to the application server;

[0028] After receiving the ciphertext, the application server decrypts the ciphertext using the new key to obtain the data to be evaluated;

[0029] The application server performs risk assessment on the data to be assessed, obtains a risk value, and executes a corresponding risk strategy according to the risk value. The risk strategy includes risk warning, key update and restricted operation.

[0030] From the above description, it can be seen that the beneficial effects of the present invention are: it can ensure the communication security between the terminal device and the application server, ensure the security of user information, and realize the safe startup of the application software.

[0031] Furthermore, when the application software is started, before the terminal device obtains the status of the application software, it further includes:

[0032] Before installing the application software, the terminal device performs whitelist verification on the application software according to a preset whitelist, and if the whitelist verification passes, the application software is installed.

[0033] From the above description, it can be seen that the whitelist verification ensures that the application software is trustworthy.

[0034] Furthermore, if the storage time of the newly acquired key exceeds the preset maximum usage time, the state of the application software is determined to be a risky state.

[0035] From the above description, it can be seen that the key can be updated regularly to further ensure the security of communication between the terminal device and the application server.

[0036] Furthermore, the terminal device and the application server obtain a new key, including:

[0037] Generate a new key through the hardware encryption module in the terminal device;

[0038] The terminal device saves the new key and sends the new key to the application server;

[0039] After receiving the new key, the application server saves it.

[0040] Furthermore, the terminal device and the application server obtain a new key, including:

[0041] The application server generates and saves a new key;

[0042] The application server sends the new key to the terminal device;

[0043] After receiving the new key, the terminal device saves it.

[0044] From the above description, it can be seen that the key can be generated by the hardware encryption module in the terminal device or issued by the background.

[0045] Furthermore, the new key is transmitted between the terminal device and the application server in the form of ciphertext.

[0046] From the above description, it can be seen that the application software cannot store any plaintext keys or ciphertext keys during operation.

[0047] Furthermore, the terminal data includes the number of terminal unique identification logins; the application operation data includes account login data, and the account login data includes the number of account password inputs within a preset period and / or the number of account logins outside a preset period; the key update data includes the number of key forced updates and / or the maximum key usage time.

[0048] Furthermore, the application server performs risk assessment on the data to be assessed to obtain a risk value, including:

[0049] Calculate the score of each data to be evaluated according to each data to be evaluated and its corresponding preset threshold value;

[0050] Perform weighted calculation based on the scores of each data to be evaluated and its corresponding preset weight to obtain the actual value;

[0051] The actual value is subtracted from a preset score threshold to obtain a risk value.

[0052] From the above description, it can be seen that a variety of application information is used to comprehensively judge whether it is safe to start the application software.

[0053] Furthermore, executing a corresponding risk strategy according to the risk value includes:

[0054] If the risk value is within a preset first threshold range, a risk strategy corresponding to a low risk is executed, wherein the risk strategy corresponding to a low risk includes a risk warning;

[0055] If the risk value is within a preset second threshold range, a risk strategy corresponding to a medium risk is executed, wherein the risk strategy corresponding to the medium risk includes key update and user operation restriction;

[0056] If the risk value is within a preset third threshold range, a risk strategy corresponding to a high risk is executed, wherein the risk strategy corresponding to a high risk includes at least one of locking a device, disabling application software, and canceling a user operation.

[0057] From the above description, it can be seen that by dividing different risk levels based on risk values ​​and executing corresponding risk strategies, application risks can be controlled and the flexibility of risk management can be improved.

[0058] The present invention also provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the method described above is implemented.

[0059] Embodiment 1

[0060] Please refer to Figure 2-3 , Embodiment 1 of the present invention is: a method for securely starting application software. The method of this embodiment is based on the application software secure startup architecture, such as Figure 2 As shown, it includes a device management module 100, an application management module 200 and a background management module 300.

[0061] The device management module 100 includes a key slave management unit 101 and a device information acquisition unit 102, the key slave management unit 101 includes a key generation subunit 1011 (key generator) and a ciphertext calculation subunit 1012; the application management module 200 includes an interactive transit management unit 201 and an application information setting unit 202; the background management module 300 includes a key master management unit 301, an application information management unit 302 and an application risk execution unit 303, the application information management unit 302 includes an application information configuration subunit 3021, an application information storage subunit 3022, an application information analysis subunit 3023 and an application information evaluation subunit 3024.

[0062] The key slave management unit 101 is used to obey the settings of the key master management unit 301 in the background management module 300 to ensure the communication security of the three modules in this embodiment.

[0063] The key generation subunit 1011 is used to select the hardware encryption module to generate the key when the device is integrated with the hardware encryption module; the ciphertext calculation subunit 1012 mainly provides the interface function of ciphertext calculation for the application software module to ensure that the valid information is transmitted as ciphertext. The device information acquisition unit 102 is used to provide an interface for the application management module 200 to call, and can obtain the unique code of the currently used device, such as the device serial number, MAC address, etc., to ensure the uniqueness of the device.

[0064] The interactive transfer management unit 201 is used for information scheduling and processing with the background management module 300 and the device management module 100, which is equivalent to a transfer station that undertakes the background and the device, and mainly processes the configuration in the application information configuration subunit 3021. For example, the application information configuration subunit 3021 is configured with the device information of the hardware that the application software needs to obtain, which is used to determine whether the application software is running on the device. For another example, if the key master management unit 301 is configured to send the key from the background, the key is forwarded to the key slave management unit 101 for storage through the interactive transfer management unit 201.

[0065] The application information setting unit 202 mainly processes according to the settings of the interactive transfer management unit 201, is not limited to the hardware device information, and is an extended behavior unit.

[0066] The key master management unit 301 is used to decide (according to the background configuration file) which key system to use to encrypt the communication data. In this embodiment, the key can be generated and issued by the background management module 300, or generated and used by the key slave management unit 101.

[0067] The application information management unit 302 is used to decide the application information that needs to be monitored during the use of the application software. Among them, the application information configuration subunit 3021 is used to configure the basic configuration information of the application software and hardware devices, including but not limited to the device unique code, application software login account, password, fingerprint, usage time limit, etc. The application information storage subunit 3022 is used to store the above configuration information one by one, including but not limited to one user name corresponding to multiple device serial numbers, one device serial number corresponding to multiple user names, and one user name and one device serial number corresponding to different information configurations in different usage scenarios. The application information analysis subunit 3023 is used to analyze the application information, for example, the number of device unique code logins, the number of password inputs within five minutes, etc. The application information evaluation subunit 3024 is used to analyze the data based on the configuration file and application information to perform risk level assessment.

[0068] The application risk execution unit 303 is used to determine whether there is any abnormality in the use of the current application software on the supporting device through the application information evaluation value in the application information management unit 302, and provide risk warning information or risk decision-making behavior, such as device locking or application software disabling operations.

[0069] like Figure 3 As shown, the method of this embodiment includes the following steps:

[0070] S1: Before installing the application software on the terminal device, the terminal device performs whitelist verification on the application software according to a preset whitelist to determine whether the verification is successful. If so, execute step S2.

[0071] S2: Install the application software.

[0072] Specifically, when installing an application software on a specific device, the application software is first briefly verified, for example, according to a preset whitelist, the application software is whitelist verified, and the application software can be installed if the verification passes. After the installation is complete, the application software can be started.

[0073] S3: When the application software is started, the terminal device obtains the status of the application software and determines whether it is the first startup state or the risk state. If so, step S4 is executed; if not, the latest key obtained previously is continued to be used.

[0074] If the application software is started for the first time after installation, it is determined to be in the first start state. If the storage time of the key newly obtained by the terminal device exceeds the preset maximum usage time, the state of the application software is determined to be a risky state.

[0075] S4: The terminal device and application server obtain and save the new key.

[0076] Specifically, at the first startup, the application management module 200 requests the background management module 300 to start the program. The background management module 300 determines the status of the application software through the application information management unit 302. If it is in the first startup state or risk state, the key needs to be updated and the status of the application software is fed back to the key master management unit 301. The key master management unit 301 performs key processing according to the key configuration management information stored in the background management module 300.

[0077] In an optional embodiment, when the key configuration management is configured to use the background key for communication, the background management module 300 issues a new key, and the new key is forwarded to the key slave management unit 101 for storage through the interactive transfer management unit 201. The application software cannot store any plaintext key or ciphertext key during operation.

[0078] In another optional embodiment, when the key configuration management is configured to generate a new key by the device management module 100, the application software calls the key generation subunit 1011 to generate a new key and forwards it to the background management module 300 in the form of ciphertext.

[0079] S5: The terminal device obtains the data to be evaluated, where the data to be evaluated includes terminal data, application operation data and key update data.

[0080] In this embodiment, the terminal data includes the number of logins of the terminal unique identification (such as the device unique code); the application operation data includes the account login data, and the account login data includes the number of account password input times within a preset period (such as the number of password input times within five minutes) and the number of account logins outside the preset time period (such as the number of operations during non-working hours), and may also include login duration, etc.; the key update data includes the number of forced key updates and the maximum key usage time.

[0081] S6: The terminal device encrypts the data to be evaluated by using the new key, and sends the encrypted ciphertext to the application server.

[0082] S7: After receiving the ciphertext, the application server decrypts the ciphertext using the new key to obtain the data to be evaluated.

[0083] For steps S5-S7, specifically, when the key status of the application software is correct (i.e., the key in the terminal device can satisfy the normal communication of the application program and can correctly encrypt and decrypt the data), the application information management unit 302 sends the configuration information in the application information configuration subunit 3021 to the interactive transfer management unit 201, wherein the configuration information includes but is not limited to the device unique code, the application software login account, password, biometric data (such as fingerprint), etc. The interactive transfer management unit 201 calls the corresponding unit in the device management module 100 and the application information setting unit 202 according to the settings in the application information configuration subunit 3021 and the key master management unit 301. Then call the device information acquisition unit 102 to obtain the device information, including but not limited to the device unique code. In calling the application information setting unit 202, all the required data are called to the ciphertext calculation subunit 1012 to generate ciphertext data. The background management module 300 receives the ciphertext data sent by the application management module 200, sends it to the application information storage subunit 3022 for decryption, and stores the accurate application information securely.

[0084] S8: The application server performs risk assessment on the data to be assessed to obtain a risk value.

[0085] Specifically, the application information analysis subunit 3023 analyzes the current application information according to the requirements of the application information configuration subunit 3021 and outputs the risk value. For example, in the application information configuration, the threshold of "number of device unique code logins" is set to 2, the threshold of "number of password inputs within five minutes" is set to 5, the threshold of "number of operations during non-working hours" is set to 3, the threshold of "number of key forced updates" is set to 4, etc. Each configuration specifies a score, and a score will be calculated if the threshold is exceeded. For example, the threshold of "number of device unique code logins" is 2, and each time it exceeds 1-2 times, the score is 5 points, and each time it exceeds 3-4 times, the score of each additional number is 10 points, and so on.

[0086] The risk value can be calculated according to the preset risk calculation rules (such as the proportion method and the threshold method). For example, a proportion coefficient (weight) is set for each data to be evaluated, and then the score and proportion coefficient of each data to be evaluated are weighted and summed to obtain the actual value, and then the preset score threshold is subtracted from the actual value to obtain the risk value.

[0087] In actual application, the risk calculation rules can be changed according to the actual scenario.

[0088] S9: Execute a corresponding risk strategy according to the risk value.

[0089] The application information evaluation subunit 3024 outputs an application risk strategy according to the application information risk value. When the application risk strategy needs to be executed, the application risk execution unit 303 is started to communicate with the interactive transfer management unit 201 to restrict the application software.

[0090] Specifically, if the risk value is within a preset first threshold range, the risk strategy corresponding to low risk is executed, and the risk strategy corresponding to low risk includes risk warning; if the risk value is within a preset second threshold range, the risk strategy corresponding to medium risk is executed, and the risk strategy corresponding to medium risk includes key update and restriction of user operation; if the risk value is within a preset third threshold range, the risk strategy corresponding to high risk is executed, and the risk strategy corresponding to high risk includes device locking, application software disabling and cancellation of user operation.

[0091] In this embodiment, the first threshold range is [0, 20), the second threshold range is [20, 50), and the third threshold range is [50, 70).

[0092] In this embodiment, through background management, the application information configuration can flexibly control the verification items of the application software, and flexibly make configurations according to different needs. For example, the same application can be released on different platforms, and different application information configuration items can be configured to perform different software verifications. The operation is convenient, and the maintenance cost of different application software versions that need to be released is reduced.

[0093] This embodiment can be used in specific industry sectors where user information needs to be kept confidential. Hardware devices and application software need to be bound to each other, and the background management system intervenes to timely analyze risk items and make prompts, thereby protecting user information security to the maximum extent. At the same time, according to the application information configuration, the use permissions of the application can be flexibly controlled under different requirements.

[0094] Embodiment 2

[0095] This embodiment is a computer-readable storage medium corresponding to the above embodiment, on which a computer program is stored. When the program is executed by the processor, it implements the various steps of an application software secure startup method in the above embodiment and can achieve the same technical effect, which will not be repeated here.

[0096] In summary, the present invention provides a method for securely starting application software and a computer-readable storage medium. By detecting the status of the application software, the key is updated in time, and the data encryption transmission between the terminal device and the application server is realized through the key, the communication security between the terminal device and the application server is ensured, and the user information security is ensured. By performing risk assessment on multiple data and executing corresponding risk strategies based on the risk values, it is possible to comprehensively judge whether it is safe to start the application software, ensure the safety of the device environment, and thus realize the secure startup of the application software.

[0097] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent transformations made using the contents of the present invention's specification and drawings, or directly or indirectly applied in related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for securely starting application software, characterized in that: include: When the application software is started, the terminal device obtains the status of the application software; If the state of the application software is a preset state, the terminal device and the application server obtain a new key, and the preset state includes the first startup state and the risk state; The terminal device obtains the data to be evaluated, which includes terminal data, application operation data and key update data, encrypts the data to be evaluated by using the new key, and sends the encrypted ciphertext to the application server; After receiving the ciphertext, the application server decrypts the ciphertext using the new key to obtain the data to be evaluated; The application server performs risk assessment on the data to be assessed, obtains a risk value, and executes a corresponding risk strategy according to the risk value. The risk strategy includes risk warning, key update and restricted operation.

2. The method for securely starting application software according to claim 1, characterized in that: When the application software is started, before the terminal device obtains the status of the application software, the method further includes: Before installing the application software, the terminal device performs whitelist verification on the application software according to a preset whitelist, and if the whitelist verification passes, the application software is installed.

3. The method for securely starting application software according to claim 1, characterized in that: If the storage time of the newly obtained key exceeds the preset maximum usage time, the state of the application software is determined to be a risky state.

4. The application software secure startup method according to claim 1, characterized in that: The terminal device and the application server obtain a new key, including: Generate a new key through the hardware encryption module in the terminal device; The terminal device saves the new key and sends the new key to the application server; After receiving the new key, the application server saves it.

5. The method for securely starting application software according to claim 1, characterized in that: The terminal device and the application server obtain a new key, including: The application server generates and saves a new key; The application server sends the new key to the terminal device; After receiving the new key, the terminal device saves it.

6. The method for securely starting application software according to claim 4 or 5, characterized in that: The new key is transmitted between the terminal device and the application server in the form of ciphertext.

7. The method for securely starting application software according to claim 1, characterized in that: The terminal data includes the number of terminal unique identification logins; the application operation data includes account login data, and the account login data includes the number of account password inputs within a preset period and / or the number of account logins outside a preset period; the key update data includes the number of key forced updates and / or the maximum key usage time.

8. The method for securely starting application software according to claim 7, characterized in that: The application server performs risk assessment on the data to be assessed to obtain a risk value, including: Calculate the score of each data to be evaluated according to each data to be evaluated and its corresponding preset threshold value; Perform weighted calculation based on the scores of each data to be evaluated and its corresponding preset weight to obtain the actual value; The actual value is subtracted from a preset score threshold to obtain a risk value.

9. The method for securely starting application software according to claim 1, characterized in that: The executing a corresponding risk strategy according to the risk value includes: If the risk value is within a preset first threshold range, a risk strategy corresponding to a low risk is executed, wherein the risk strategy corresponding to a low risk includes a risk warning; If the risk value is within a preset second threshold range, a risk strategy corresponding to a medium risk is executed, wherein the risk strategy corresponding to the medium risk includes key update and user operation restriction; If the risk value is within a preset third threshold range, a risk strategy corresponding to a high risk is executed, wherein the risk strategy corresponding to a high risk includes at least one of locking a device, disabling application software, and canceling a user operation.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images