Security authentication method and device, equipment, storage medium and product

Abstract

The invention discloses a security authentication method and device, equipment, a storage medium and a product, and relates to the technical field of terminal verification, and the method comprises the steps: updating a lock value of a security lock of a corresponding block of terminal equipment based on a risk level of a user interaction behavior on the terminal equipment; when a data query request of a target block is received, determining the current state of the security lock of the target block based on the lock value of the security lock of the target block; and when the current state of the security lock of the target block is an unlocked state, safely returning data of the target block. Through the above mode, a security lock mechanism is added to the block to which the terminal equipment belongs, and automatic locking and unlocking are performed according to the risk level, so that the security of data is ensured.

Description

Technical Field

[0001] The present application relates to the field of terminal authentication technology, and in particular to security authentication methods, devices, equipment, storage media and products. Background Art

[0002] At present, verification codes are usually sent to users during login, so that users can identify and verify the verification codes, thereby preventing malicious programs (such as crawlers or ticket grabbing software) from maliciously accessing websites. However, with the development of artificial intelligence technology, malicious programs have surpassed humans in their ability to identify and verify verification codes, resulting in existing verification code technology that not only fails to prevent malicious programs, but also increases the difficulty of verification for normal users. At the same time, there are information security risks, and user data is easily accessed maliciously.

[0003] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0004] The main purpose of this application is to provide a security authentication method, device, equipment, storage medium and product, aiming to solve the technical problems in the prior art that traditional verification methods have information security risks and user data is easily accessed maliciously.

[0005] To achieve the above object, the present application provides a security authentication method, which is applied to a consortium chain, wherein the consortium chain is provided with a plurality of blocks, wherein the plurality of blocks correspond to different terminal devices one by one, and the plurality of blocks are provided with security locks, wherein the method comprises:

[0006] Based on the risk level of the user interaction behavior on the terminal device, updating the lock value of the security lock of the corresponding block of the terminal device;

[0007] When receiving a data query request for a target block, determining a current state of a security lock of the target block based on a lock value of the security lock of the target block;

[0008] When the current state of the security lock of the target block is unlocked, the data of the target block is safely returned.

[0009] In one embodiment, before the step of updating the lock value of the security lock of the corresponding block of the terminal device based on the risk level of the user interaction behavior on the terminal device, the step further includes:

[0010] Obtaining the operating environment detection results, historical interaction records, device identity information, and device address information of the terminal device;

[0011] After the operating environment detection result, device identity information, and device address information of the terminal device pass integrity verification and validity verification, the risk coefficient of the user interaction behavior on the terminal device is calculated based on the operating environment detection result and historical interaction records of the terminal device;

[0012] Determining an initial risk level of the user interaction behavior on the terminal device based on a risk level range within which the risk coefficient of the terminal device complies;

[0013] Based on the device address information of the terminal device, the initial risk level is adjusted to obtain the risk level of the user interaction behavior on the terminal device.

[0014] In one embodiment, the alliance chain has a consensus-based smart contract, and the step of calculating the risk coefficient of the user interaction behavior on the terminal device based on the operating environment detection result and the historical interaction record of the terminal device includes:

[0015] Based on the operating environment detection result of the terminal device, determine the number of problems existing in the environment detection content of the terminal device;

[0016] Determining the interaction risk value of the interactive software in the terminal device based on the historical interaction record of the terminal device;

[0017] Based on the smart contract, determine the number of problems in the environmental detection content, the interaction risk value of the interactive software, the weight of the environmental detection, and the corresponding relationship between the interaction weight and the risk coefficient;

[0018] Based on the number of problems in the environment detection content in the terminal device, the interaction risk value of the interactive software in the terminal device, the weight of the environment detection, the weight of the interaction, the number of interactive software and the corresponding relationship, the risk coefficient of the user interaction behavior on the terminal device is determined.

[0019] In one embodiment, the step of updating the lock value of the security lock of the corresponding block of the terminal device based on the risk level of the user interaction behavior on the terminal device includes:

[0020] When the risk level of the user interaction behavior on the terminal device is a high-risk behavior level, obtaining a lock value of a security lock of a block corresponding to the terminal device;

[0021] When the lock value of the security lock of the block corresponding to the terminal device is an odd number, continue to maintain the lock value of the security lock of the block corresponding to the terminal device;

[0022] When the lock value of the security lock of the block corresponding to the terminal device is an even number, the lock value of the security lock of the block corresponding to the terminal device is increased by a preset incremental value so that the lock value of the security lock of the block corresponding to the terminal device meets an odd number after adjustment.

[0023] In one embodiment, upon receiving a data query request for a target block, the step of determining a current state of a security lock of the target block based on a lock value of the security lock of the target block comprises:

[0024] When the lock value of the security lock of the target block is a first value, determining that the current state of the security lock of the target block is a locked state;

[0025] When the lock value of the security lock of the target block is a second value, determining that the current state of the security lock of the target block is an unlocked state, and the second value is greater than the first value;

[0026] When the lock value of the security lock of the target block is greater than a second value, it is determined that the current state of the security lock of the target block is a repeatedly locked and unlocked state.

[0027] In one embodiment, the method further comprises:

[0028] Generate a preset number of random strategies in nodes that meet the requirements, and randomly divide the random strategies that have reached consensus to other nodes to obtain available strategies for each node;

[0029] When the risk level of the user interaction behavior on the terminal device is a suspected risk behavior level, determining a current use policy based on available policies stored in a request node of the terminal device;

[0030] Based on the current usage policy, security verification is performed on the user interaction behavior to obtain corresponding interaction behavior verification data, and the current usage policy is deleted from the available policies of the requesting node;

[0031] After the user interaction behavior passes the security verification, the user interaction behavior on the terminal device is allowed.

[0032] In addition, to achieve the above purpose, the present application also proposes a security authentication device, the security authentication device comprising:

[0033] A lock value updating module, used to update the lock value of the security lock of the corresponding block of the terminal device based on the risk level of the user interaction behavior on the terminal device;

[0034] A data security module, configured to determine a current state of a security lock of a target block based on a lock value of the security lock of the target block when receiving a data query request of the target block;

[0035] The data security module is further configured to safely return the data of the target block when the current state of the security lock of the target block is an unlocked state.

[0036] In addition, to achieve the above-mentioned purpose, the present application also proposes a security authentication device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the security authentication method as described above.

[0037] In addition, to achieve the above-mentioned purpose, the present invention also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the security authentication method as described above are implemented.

[0038] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the security authentication method as described above are implemented.

[0039] The present application provides a security authentication method, which updates the lock value of the security lock of the corresponding block of the terminal device based on the risk level of the user interaction behavior on the terminal device; when receiving a data query request for the target block, the current state of the security lock of the target block is determined based on the lock value of the security lock of the target block; when the current state of the security lock of the target block is unlocked, the data of the target block is safely returned. The present application adds a security lock mechanism to the block to which the terminal device belongs, automatically locks and unlocks according to the risk level, so that the data corresponding to the terminal device is not easily obtained by people or organizations outside the chain, ensuring the security of the data and preventing user data from being maliciously accessed. The data is stored in a consortium chain, achieving the credibility of data that cannot be tampered with, and solving the technical problems that the traditional verification method has information security risks and user data is easily maliciously accessed. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0041] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0042] Figure 1 This is a flowchart of the first embodiment of the security authentication method of this application;

[0043] Figure 2 A schematic diagram of data storage of a security authentication method provided in Example 1 of the present application;

[0044] Figure 3 This is a flow chart of the second embodiment of the security authentication method of this application;

[0045] Figure 4 This is a flowchart of the third embodiment of the security authentication method of this application;

[0046] Figure 5 A schematic diagram of the overall architecture of the security authentication method provided in Example 2 of the present application;

[0047] Figure 6 This is a schematic diagram of the module structure of the security authentication device according to an embodiment of the present application;

[0048] Figure 7 A schematic diagram of the device structure of the hardware operating environment involved in the security authentication method in the embodiment of the present application.

[0049] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0050] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0051] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0052] The main solution of the embodiment of the present application is: based on the risk level of the user interaction behavior on the terminal device, update the lock value of the security lock of the corresponding block of the terminal device; when receiving a data query request for the target block, determine the current state of the security lock of the target block based on the lock value of the security lock of the target block; when the current state of the security lock of the target block is unlocked, safely return the data of the target block.

[0053] At present, with the development of artificial intelligence technology, malicious programs have surpassed humans in identifying and verifying verification codes, resulting in the existing verification code technology not only failing to prevent malicious programs, but also increasing the difficulty of verification for normal users. At the same time, there are information security risks, and user data can be easily accessed maliciously.

[0054] The present application provides a solution, which adds a security lock mechanism to the block to which the terminal device belongs, automatically locks and unlocks it according to the risk level, so that the data corresponding to the terminal device is not easily obtained by people or organizations outside the chain, thereby ensuring the security of the data and preventing user data from being maliciously accessed. The data is stored in a consortium chain, which achieves the credibility of data that cannot be tampered with, and solves the technical problems of information security risks in traditional verification methods and user data being easily accessed maliciously.

[0055] The present application embodiment provides a security authentication method, referring to Figure 1 , Figure 1 This is a flowchart of the first embodiment of the security authentication method of this application.

[0056] In this embodiment, the security authentication method includes steps S10 to S30:

[0057] Step S10, updating the lock value of the security lock of the corresponding block of the terminal device based on the risk level of the user interaction behavior on the terminal device;

[0058] It should be noted that the execution subject of this embodiment is a consortium chain, in which multiple blocks are provided, and the multiple blocks correspond to the terminal devices of different users one by one, and are used to store the relevant data of each terminal device. The terminal device can be a mobile terminal, such as a smart phone, which is not specifically limited. Since the traditional verification method has information security risks and user data is easily accessed maliciously, in this embodiment, multiple blocks are provided with security locks, and a security lock mechanism is added to the block to which the terminal device belongs, so that the data corresponding to the terminal device is not easily obtained by people or organizations outside the chain, ensuring the security of the data and preventing user data from being maliciously accessed.

[0059] In addition, it should be noted that it is usually necessary to first form a blockchain alliance, that is, a consortium chain. APP software manufacturers on terminal devices can apply to join the consortium chain. The administrator configures the accounts of each manufacturer with necessary information on the operating platform corresponding to the consortium chain management node, and distributes the account configuration to each manufacturer. Each manufacturer integrates the SDK (Software Development Kit) of its own configuration parameters in its own APP, and puts it on the shelves in channels such as the application market for users to download. After the manufacturer joins the consortium chain, it will first synchronize the data of the consortium chain under the current time snapshot. After the synchronization is completed, it can become a normal node to receive data and participate in the consensus process. If more APP software manufacturers join the consortium chain in the future, the above application and configuration process will continue.

[0060] It is understandable that the risk level refers to the degree of risk in user interaction behavior on the terminal device, which can usually be divided into a risk-free behavior level, a suspected risk behavior level, and a high-risk behavior level. User interaction behavior refers to the behavior that needs to determine the risk level, for example: a user attempts to log in to an APP that has integrated the SDK (the APP manufacturer has joined the alliance chain), which can be set according to the actual situation and is not specifically limited. The risk level can be determined based on the operating environment detection results of the terminal device. The operating environment detection results refer to the detection results of the APP operating environment. The detection of the APP operating environment usually includes multiple detection contents, such as: frida, network layer proxy, simulator identification, etc. The detection content can be flexibly adjusted according to the system configuration of the terminal device or the name of the system process, and then identify whether there is this type of risk, obtain the detection results of each detection content, and generate the corresponding operating environment detection results. The operating environment detection results are generated by the SDK and fed back to the alliance chain.

[0061] It should be understood that user interaction behavior usually triggers the operating environment detection, thereby determining the risk level. For example, after the user downloads and installs the APP integrated with the SDK, each time the user clicks the APP icon, the SDK starts to start the operating environment detection, generates the operating environment detection results, and feeds them back to the alliance chain.

[0062] In a feasible implementation, when the risk level of the user interaction behavior on the terminal device is a suspected risk behavior level, the user interaction behavior is security verified based on a consensus random strategy to obtain corresponding interaction behavior verification data, and the random strategy at least includes a random verification direction and a random verification strength; when the risk level of the user interaction behavior on the terminal device is a no-risk behavior level, the user interaction behavior on the terminal device is allowed; when the risk level of the user interaction behavior on the terminal device is a high-risk behavior level, the user interaction behavior on the terminal device is prohibited.

[0063] It should be noted that the random strategy is a random verification method used to avoid and identify mechanized behavior (large-scale malicious behavior is often to place rows of simulated clicked mobile phones on a bracket that can be shaken in the horizontal direction). In the present embodiment, the random strategy is a random shake strategy, that is, verification is performed in the form of random shaking. At this time, the random strategy at least includes a random verification direction and a random verification strength. The random verification direction is a random shake direction, for example: up and down, left and right, and oblique directions. The random verification strength is a random shake strength, for example: gently shake (small strength), shake normally (normal strength), and shake vigorously (shake vigorously). Exemplarily, assuming that the random verification direction is divided into up and down, left and right, and oblique directions, and the random verification strength is divided into gently shake, shake normally, and shake vigorously. At this time, after permutations and combinations, there are nine random strategies: ① gently shake up and down; ② shake normally up and down; ③ shake vigorously up and down; ④ shake gently left and right; ⑤ shake normally left and right; ⑥ shake vigorously left and right; ⑦ shake gently in the oblique direction; ⑧ shake normally in the oblique direction; ⑨ shake vigorously in the oblique direction. Each time you verify, you can select a random strategy in the shake.

[0064] It is understandable that if the risk level received by the SDK is a high-risk behavior level (for example, a simulator or machine behavior is detected), the user will be prohibited from logging in or taking the next step; if the risk level received by the SDK is a no-risk behavior level, the SDK does not need to pop up the human-computer interaction verification page, and directly proceeds to the next step without verification; if the risk level received by the SDK is a suspected risk behavior level, the SDK will pop up a shake human-computer interaction verification page according to the shake random strategy. The user can enter the next step of the APP after shaking as required and passing the verification. At the same time, the SDK will transmit the verification data (such as the random strategy used, the strength of the user's shake), device GPS address, device access IP address and other data back to the alliance chain for storage.

[0065] It should be understood that the operating environment detection results, risk levels, and interactive behavior verification data of the terminal device based on the risk levels are stored in the data chain of the corresponding block.

[0066] It should be noted that according to the device ID, check whether there is a block for the device in the alliance chain. If the block exists, the key value of the corresponding double hash table can be found from the block, and the reported data is written into the first hash table as the value of the key value for calculation by the smart contract. At this time, the key and value are configured as follows: Key: hash value in the form of String, calculated according to the device ID, which can ensure that "different devices have different hash values, and the device ID reported by different APPs of the same device is the same"; Value: APPID: operating environment detection results: interactive behavior verification data. If the block does not exist, create a new block, and use the device ID as the hash calculation to obtain the hash value of the double hash table mounted on the block, and execute the above process of writing to the hash table.

[0067] It is understandable that each node of the alliance chain packages the double hash table and block hash value into a data block and distributes it to the alliance chain. After each node of the alliance chain reaches a consensus on the data block, it is stored locally. At this time, the smart contract is used to calculate the risk factor, and the risk factor result is mounted in the second hash table of the double hash with the same hashkey value (that is, the first hash table stores the detailed records required for the risk factor calculation, and the second hash table stores the risk factor results of each time). At this time, the structure of the blockchain can be referred to Figure 2 .

[0068] In a feasible implementation, step S10 may include: when the risk level of the user interaction behavior on the terminal device is a high-risk behavior level, obtaining the lock value of the security lock of the corresponding block of the terminal device; when the lock value of the security lock of the corresponding block of the terminal device is an odd number, continuing to maintain the lock value of the security lock of the corresponding block of the terminal device; when the lock value of the security lock of the corresponding block of the terminal device is an even number, increasing the lock value of the security lock of the corresponding block of the terminal device by a preset incremental value, so that the lock value of the security lock of the corresponding block of the terminal device conforms to an odd number after adjustment.

[0069] It should be noted that the credibility of the block locking and unlocking process is particularly important. At the same time, it is best not to bring great storage pressure and economic costs to the storage system of the alliance chain. For this reason, this embodiment uses a HashMap structure to store the logical security lock of the block. Among them, the Key of the HashMap is the Key calculated based on the device ID stored in the block, and the Value is a number, which defaults to 1. That is, when the data is HashMaped for the first time, it means that the device ID corresponding to the Key is already high risk. When it is continuously unlocked and locked, the Value continues to increase by 1. At this time, there are two types of Value. Case 1: Value = 1 (locked, at this time the terminal device corresponding to the Key is a high-risk behavior level) or Value = 2 (unlocked, at this time the terminal device corresponding to the Key is a non-high-risk behavior level); Case 2: Value> 2 (repeatedly locked and unlocked, at this time the terminal device corresponding to the Key is a high-risk behavior level). The lock value of the security lock is the value of the Value corresponding to the Key calculated based on the device ID in the HashMap.

[0070] It can be understood that if the risk level is a high-risk behavior level, the security lock HashMap stored locally in the node is taken out to check whether the Key calculated based on the device ID is in the HashMap. If it does not exist, it means that it is the first time to lock, and the Key of the HashMap is set to the Key calculated based on the device ID, Value = 1 (locked); if it exists, the Value corresponding to the Key calculated based on the device ID in the HashMap is taken out. If Value = 1 or other odd numbers, it means that it has been locked and there is no need to lock it again. If Value = 2 or other even numbers, it means that it has been unlocked before, and continue to lock it at this time, that is, Value continues to increase the value by the preset increment value, and the preset increment value is usually set to 1, and the value of the adjusted Value is an odd number.

[0071] It should be understood that if the risk level is not a high-risk behavior level (suspected risk behavior level and no-risk behavior level), the security lock HashMap stored locally in the node is taken out to check whether the Key calculated based on the device ID is in the HashMap. If it does not exist, it means that it is not locked and no operation is required at this time; if it exists, the Value corresponding to the Key calculated based on the device ID in the HashMap is taken out. If Value = 1 or other odd numbers, it means that it is locked. At this time, it is unlocked, that is, the Value continues to add 1, and the value of the adjusted Value is an even number. If Value = 2 or an even number, it means that it has been unlocked before, and there is no need to unlock it again.

[0072] Step S20, upon receiving a data query request for a target block, determining a current state of a security lock of the target block based on a lock value of the security lock of the target block;

[0073] In a feasible implementation, step S20 may include: when the lock value of the security lock of the target block is a first value, determining that the current state of the security lock of the target block is a locked state; when the lock value of the security lock of the target block is a second value, determining that the current state of the security lock of the target block is an unlocked state, and the second value is greater than the first value; when the lock value of the security lock of the target block is greater than the second value, determining that the current state of the security lock of the target block is a repeatedly locked and unlocked state.

[0074] It should be noted that the first value is 1, and the second value is 2. A data query request is a request to query data in a certain block, which is usually an external request, and the target block is the block whose data is to be queried in the request.

[0075] It is understandable that when the outside wants to query the data of the target block, each node will first check the locally stored security lock HashMap after receiving the relevant request. If the Key calculated based on the device ID does not exist, it means that the risk level of the device is not a high-risk behavior level, and the data can be returned to the caller normally through the alliance link interface. If the Key calculated based on the device ID exists, it will be processed separately according to the corresponding Value: when Value = 1, it means that it is in a locked state, indicating that the device is at a high-risk behavior level, and the data cannot be returned to the caller normally through the alliance link interface; when Value = 2, it means that it is in an unlocked state, indicating that the device is not at a high-risk behavior level, and the data can be returned to the caller normally through the alliance link interface; when Value>2, it means that the device is repeatedly locked and unlocked, indicating that the device is at a high-risk behavior level, and the data cannot be returned to the caller normally through the alliance link interface.

[0076] Step S30, when the current state of the security lock of the target block is unlocked, securely return the data of the target block.

[0077] It should be noted that data can only be returned to the caller when the security lock of the target block is unlocked to ensure data security.

[0078] This embodiment provides a security authentication method, which updates the lock value of the security lock of the block corresponding to the terminal device based on the risk level of the user interaction behavior on the terminal device; when receiving a data query request for the target block, the current state of the security lock of the target block is determined based on the lock value of the security lock of the target block; when the current state of the security lock of the target block is unlocked, the data of the target block is safely returned. A security lock mechanism is added to the block to which the terminal device belongs, and it is automatically locked and unlocked according to the risk level, so that the data corresponding to the terminal device is not easily obtained by people or organizations outside the chain, ensuring the security of the data and preventing user data from being maliciously accessed. In addition, the data is stored in the form of a consortium chain, realizing the credibility of data that cannot be tampered with.

[0079] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can refer to the above introduction, and will not be repeated later. Figure 3 , before step S10, steps S01 to S04 may be included:

[0080] Step S01, obtaining the operating environment detection result, historical interaction record, device identity information and device address information of the terminal device;

[0081] It should be noted that historical interaction records refer to historical interaction behaviors between users and terminal devices and the risk factors of historical interaction behaviors, and there is no specific limitation on this. Device identity information refers to information related to device identity, such as: APPID, SDK account name, SDK ID, etc., and there is no specific limitation on this. Device address information refers to information related to device address, including at least device geographic location information and device network address information. Device geographic location information refers to the current location of the terminal device, such as: device GPS, and device network address information refers to the IP address of the terminal device, such as: device network IP address.

[0082] Step S02, after the operating environment detection result, device identity information and device address information of the terminal device pass integrity verification and validity verification, the risk coefficient of the user interaction behavior on the terminal device is calculated based on the operating environment detection result and historical interaction records of the terminal device;

[0083] It should be noted that validity refers to the validity of the identity of the terminal device (including SDK) reported to the alliance chain, that is, the device identity information is valid. In other words, the validity verification needs to be verified based on the APP ID, SDK account name, etc. If this information is not on the chain, it is proved to be invalid information and the validity verification fails. If all this information is on the chain, it is proved to be valid information and the validity verification passes.

[0084] In addition, it should be noted that integrity means that important information such as the operating environment detection results, device identity information, and device address information all exist. If all of this information exists, it means that the integrity verification has passed. If at least one type of this information does not exist, then when the validity verification passes, it means that the information reported by the terminal device is suspected to be processed by humans or machines, and the integrity verification fails. There are hidden dangers in user interaction behavior on the terminal device. At this time, the risk level of user interaction behavior on the terminal device can be considered to be a high-risk behavior level.

[0085] It is understandable that after passing integrity verification and validity verification, the risk factor of the user interaction behavior on the terminal device can be calculated.

[0086] In a feasible implementation, step S02 may include steps S021 to S024:

[0087] Step S021, based on the running environment detection result of the terminal device, determining the number of problems existing in the environment detection content of the terminal device;

[0088] It should be noted that the environmental detection content, i.e., the items of the operating environment detection, at least includes frida, network layer proxy, and simulator identification. The number of problems is the total number of risks in the environmental detection content of each interactive software when performing the operating environment detection, that is, the sum of the number of risks in the environmental detection content of each interactive software when performing the operating environment detection. Interactive software is the APP with which users interact. For example, assuming that the environmental detection content is frida, network layer proxy, and simulator identification, and the interactive software is A, B, and C, if interactive software A has 2 risks, if interactive software B has 1 risk, and if interactive software C has 2 risks, then the number of problems is 2+1+2=5, and the number of interactive software is 3.

[0089] Step S022, determining the interaction risk value of the interactive software in the terminal device based on the historical interaction record of the terminal device;

[0090] It should be noted that the interaction risk value of the interactive software can be determined based on the previous risk level. If the interactive software’s previous risk level was a no-risk behavior level, the interaction risk value is 1. If the interactive software’s previous risk level was a suspected risk behavior level, the interaction risk value is 2. If the interactive software’s previous risk level was a high-risk behavior level, the interaction risk value is 3.

[0091] Step S023, based on the smart contract, determining the corresponding relationship between the number of problems in the environment detection content, the interaction risk value of the interactive software, the weight of the environment detection, the weight of the interaction, the number of interactive software and the risk coefficient;

[0092] It should be noted that the alliance chain has a consensus smart contract, which mainly includes contract content and contract functions. The contract content mainly involves environmental detection content synchronized with the SDK. There are two contract functions, which are used for timing and real-time calculation of the risk factor of the terminal device and locking and unlocking the security lock of the block to which the terminal device belongs.

[0093] Generally speaking, you can edit smart contracts on the operation platform corresponding to the alliance chain management node, package the edited smart contracts into the alliance chain block and publish them to the alliance chain. Each node of the alliance chain receives the alliance chain block and saves it in its local main chain after consensus by the consensus algorithm. With the upgrade of human-computer interaction attack and defense technology, for example, when the content of environmental detection increases or decreases, the smart contract can be upgraded, and then it will be published and agreed again.

[0094] It can be understood that the corresponding relationship between the number of problems in the environmental detection content, the interaction risk value of the interactive software, the weight of the environmental detection, the weight of the interaction, the number of interactive software and the risk coefficient, that is, the calculation formula of the risk coefficient, is as follows:

[0095]

[0096] In the formula, L represents the risk factor, W represents the number of problems in the environmental testing content, and λ i represents the interaction risk value of interactive software i, k0 represents the weight of environmental detection, k1 represents the weight of interaction, and N represents the number of interactive software.

[0097] Step S024, determining the risk coefficient of the user interaction behavior on the terminal device based on the number of problems in the environment detection content in the terminal device, the interaction risk value of the interactive software in the terminal device, the weight of the environment detection, the weight of the interaction and the corresponding relationship.

[0098] It can be understood that by substituting the number of problems in the environmental detection content in the terminal device, the interaction risk value of the interactive software in the terminal device, the weight of the environmental detection, and the weight of the interaction into the above calculation formula, the risk coefficient of the user interaction behavior on the terminal device can be obtained.

[0099] Step S03, determining an initial risk level of the user interaction behavior on the terminal device based on the risk level range that the risk coefficient of the terminal device complies with;

[0100] It should be noted that the risk level range is the range of risk level demarcation, which usually includes the risk level range of no-risk behavior level, the risk level range of suspected risk behavior level and the risk level range of high-risk behavior level. Exemplarily, the risk coefficient is a decimal less than 1, and the (0,1) interval is divided into three segments, (0,0.1] is the risk level range of no-risk behavior level, (0.1,0.5] is the risk level range of suspected risk behavior level, and (0.5,1) is the risk level range of high-risk behavior level. The risk level range into which the risk coefficient falls is considered to be in line with the risk level range, thereby obtaining the corresponding risk level. The risk level obtained at this time is a preliminary judgment result, that is, the initial risk level, which needs to be further determined.

[0101] Step S04: Based on the device address information of the terminal device, the initial risk level is adjusted to obtain the risk level of the user interaction behavior on the terminal device.

[0102] It should be noted that this embodiment cross-validates the initial risk level in combination with the device address information.

[0103] It is understandable that if the data on the chain of the device's GPS address and the data on the chain this time are both within a similar distance range, or the data on the chain of the device's IP address and the data on the chain this time are both the same value, it means that the device has not moved, and the risk level is upgraded. In other words, if the initial risk level is a suspected risk behavior level, it is upgraded to a high-risk behavior level, and if the initial risk level is a no-risk behavior level, it is upgraded to a suspected risk behavior level. If the data on the chain of the device's GPS address and the data on the chain this time are not within a similar distance range, or the data on the chain of the device's IP address and the data on the chain this time are not the same value, it means that the device has moved, that is, it moves with the movement of the person to whom the device belongs. At this time, the initial risk level obtained before is maintained, and the initial risk level is used as the final risk level.

[0104] This embodiment provides a security authentication method, which obtains the operating environment detection results, historical interaction records, device identity information and device address information of the terminal device; after the operating environment detection results, device identity information and device address information of the terminal device pass the integrity verification and validity verification, the risk coefficient of the user interaction behavior on the terminal device is calculated based on the operating environment detection results and historical interaction records of the terminal device; the initial risk level of the user interaction behavior on the terminal device is determined based on the risk level range that the risk coefficient of the terminal device meets; based on the device address information of the terminal device, the initial risk level is adjusted to obtain the risk level of the user interaction behavior on the terminal device. A security lock mechanism is added to the block to which the terminal device belongs, which is automatically locked and unlocked according to the risk level, so that the data corresponding to the terminal device is not easily obtained by people or organizations outside the chain, ensuring the security of the data and preventing user data from being maliciously accessed. In addition, the data is stored in the form of a consortium chain, realizing the credibility of data that cannot be tampered with.

[0105] In the third embodiment of the present application, the same or similar contents as those in the above embodiment can be referred to the above description, and will not be described in detail later. Figure 4 The security authentication method further includes steps S10' to S40':

[0106] Step S10', generating a preset number of random strategies in nodes that meet the requirements, and randomly dividing the random strategies that have reached consensus to other nodes to obtain available strategies for each node;

[0107] It should be noted that the random strategy is a random verification method used to avoid and identify mechanized behavior (large-scale malicious behavior often involves placing rows of simulated clicked mobile phones on a bracket that can be shaken in the horizontal direction). In the present embodiment, the random strategy is a shake random strategy, that is, verification is performed in the form of random shaking. The random strategy at least includes a random verification direction and a random verification strength. The random verification direction is a random shake direction, for example: up and down, left and right, and oblique directions. The random verification strength is a random shake strength, for example: gently shake (small strength), shake normally (normal strength), and shake vigorously (shake vigorously). Exemplarily, assuming that the random verification direction is divided into up and down, left and right, and oblique directions, and the random verification strength is divided into gently shake, shake normally, and shake vigorously. At this time, after permutations and combinations, up to nine random strategies can be generated: ① gently shake up and down; ② shake normally up and down; ③ shake vigorously up and down; ④ gently shake left and right; ⑤ shake normally left and right; ⑥ shake vigorously left and right; ⑦ gently shake in the oblique direction; ⑧ shake normally in the oblique direction; ⑨ shake vigorously in the oblique direction.

[0108] In addition, it should be noted that the preset number is the number of random strategies that need to be generated. There are usually multiple nodes in the alliance chain. The preset number is related to the current number of nodes in the alliance chain and the frequency of strategy requests in the previous time period to ensure that the supply of random strategies meets demand and is not wasted. The calculation relationship is as follows:

[0109]

[0110] In the formula, tt represents the minimum number of random strategies assigned to each node, t is the unit time, F is the frequency of strategy requests within the unit time t, and N is the current number of nodes in the alliance chain.

[0111] When the alliance chain is built, the nodes that meet the requirements generate a preset number of random strategies locally, and package these strategies and send them to the alliance chain. After consensus by the consensus algorithm, they are stored in other nodes. The available strategies are the random strategies stored in each node that can be used for verification, that is, the random strategies divided to each node.

[0112] It is understandable that the nodes that meet the requirements will evenly divide the preset number (T) of random strategies to each other node according to the current situation of the alliance chain nodes (number of nodes N, node name) and the order of consensus results fed back by other nodes, that is, each node uses T / N strategies, and the random strategies divided to the first other node that feeds back the consensus result are the first strategy to T / N strategies, and the random strategies divided to the second other node that feeds back the consensus result are the T / N+1th strategy to 2×(T / N)th strategies, and so on, so that each node has its own available strategy. Since the number of nodes in the alliance chain network is variable, and the communication quality of each node is also variable, the strategy division has a strong randomness.

[0113] It should be understood that the nodes that meet the requirements can be the first node to start, the newly added node, and the node whose number of available strategies stored is less than the preset number of strategies. Among them, the preset number of strategies can be set to a specific value according to actual needs, which is usually less than the preset number (T). The mode of generating batch strategies by a single node is faster than the consensus speed of generating batch strategies by multiple nodes. The strategy segmentation based on consensus can ensure that when the blockchain nodes change dynamically, the strategy position and number allocated to each node are dynamically changed each time, which increases the security of the strategy and is not easy to be cracked.

[0114] Step S20', when the risk level of the user interaction behavior on the terminal device is a suspected risk behavior level, determining a current use policy based on available policies stored in the request node of the terminal device;

[0115] It should be noted that the requesting node is the node from which the SDK requests a random strategy, and the currently used strategy is the random strategy randomly selected from the available strategies. Risk levels can generally be divided into risk-free behavior level, suspected risk behavior level, and high risk behavior level. When the risk level of the user's interactive behavior is a suspected risk behavior level, the SDK requests a random strategy for verification from the requesting node, and the requesting node randomly selects a random strategy from the locally stored available strategies as the currently used strategy and returns it to the SDK.

[0116] Exemplarily, when the requesting node receives the request from the SDK, the requesting node retrieves the first random strategy from the available strategies locally and returns it to the SDK.

[0117] In a feasible implementation, the step of determining the risk level of user interaction behavior includes: obtaining the operating environment detection result, historical interaction record, device identity information and device address information of the terminal device; after the operating environment detection result, device identity information and device address information of the terminal device pass integrity verification and validity verification, based on the operating environment detection result and historical interaction record of the terminal device, calculating the risk coefficient of the user interaction behavior on the terminal device; based on the risk level range that the risk coefficient of the terminal device conforms to, determining the initial risk level of the user interaction behavior on the terminal device; based on the device address information of the terminal device, adjusting the initial risk level to obtain the risk level of the user interaction behavior on the terminal device. For details, please refer to the second embodiment above, which will not be repeated here.

[0118] Step S30', based on the current usage policy, perform security verification on the user interaction behavior, obtain corresponding interaction behavior verification data, and delete the current usage policy from the available policies of the requesting node;

[0119] It is understandable that after the SDK receives the current usage policy returned by the requesting node, the SDK can pop up a shake human-computer interaction verification page on the interface of the terminal device according to the obtained current usage policy, and perform security verification on the user interaction behavior. The page will prompt the random verification direction and random verification strength of the current usage policy. If the direction and strength of the user's shake are in line with the current usage policy, the user is considered to have passed the security verification. If at least one of the direction and strength of the user's shake does not comply with the current usage policy, the user is considered to have failed the security verification. At the same time, the SDK will return the human-computer interaction verification data (such as the current usage policy, the strength of the user's shake, the direction of the user's shake), the device GPS address, and the device's network access IP address to the alliance chain for storage.

[0120] It should be understood that in order to ensure that a new strategy can be used when the next request arrives, the currently used strategy will be deleted from the available strategies each time it is retrieved. For example, when the requesting node receives a request from the SDK, if the requesting node retrieves the first random strategy from the available strategies locally as the currently used strategy and returns it to the SDK, the first random strategy that has been used in the available strategies will be deleted.

[0121] Step S40': after the user interaction behavior passes the security verification, the user interaction behavior on the terminal device is allowed.

[0122] It is understandable that users can proceed to the next step of the APP after verification.

[0123] In addition, when the risk level of the user interaction behavior on the terminal device is a no-risk behavior level, the user interaction behavior on the terminal device is allowed; when the risk level of the user interaction behavior on the terminal device is a high-risk behavior level, the user interaction behavior on the terminal device is prohibited.

[0124] In the specific implementation, if the risk level received by the SDK is a high-risk behavior level (for example, a simulator or machine behavior is detected), the user will be prohibited from logging in or taking the next step; if the risk level received by the SDK is a no-risk behavior level, the SDK does not need to pop up the human-computer interaction verification page, and directly proceeds to the next step without verification; if the risk level received by the SDK is a suspected risk behavior level, the SDK will pop up a shake human-computer interaction verification page according to the shake random strategy, and the user can proceed to the next step of the APP after shaking as required and passing the verification.

[0125] This embodiment provides a security authentication method, which divides the risk level into a non-risk behavior level, a suspected risk behavior level, and a high-risk behavior level. The non-risk behavior level does not require human-computer interaction verification, the suspected risk behavior level is verified by a shake method with a random strategy, and the high-risk behavior level prohibits login or the next step, where the random strategy is obtained from the existing consensus of the alliance chain. Security verification is implemented in a shake method that can be easily implemented at all ages, and the consensus random direction and random strength are obtained from the alliance chain. Combined with the device GPS address and the device network IP address, it is convenient for users to verify and can accurately identify and avoid machine behaviors such as simulators.

[0126] For example, to help understand the implementation process of the security authentication method obtained by combining this embodiment with the above-mentioned embodiment 2, please refer to Figure 5 , Figure 5 A schematic diagram of the overall architecture of a security authentication method is provided, specifically:

[0127] The overall architecture consists of the alliance chain and the user's terminal device. The terminal device is installed with multiple APPs with integrated SDK. Among them, the SDK is used to detect the operating environment of the terminal device and divide the users into risk-free users, suspected risk users, and high-risk users according to the risk coefficient calculated by the alliance chain smart contract. No human-computer interaction verification is required for risk-free users, and a shake method with a random strategy is used for suspected risk users. High-risk users are prohibited from logging in or taking the next step. The random strategy is obtained from the existing consensus of the alliance chain. It is implemented in a shake method that can be easily implemented at all ages, and the consensus random direction and strength are obtained from the alliance chain. Combined with the device GPS address and the device network IP address, it is convenient for users to verify human-computer verification, and can also identify and avoid machine behaviors such as simulators. The alliance chain is responsible for storing and consensus on the detection content of each on-chain device environment, the user's interactive verification results of each APP in the on-chain device, and the calculation and consensus storage of the risk coefficient of the terminal device. The risk factor is calculated based on the environmental detection data on the device and the historical data that has been uploaded to the alliance chain. This part of the data is tamper-proof through the alliance chain, and is therefore applicable to all apps on the device. That is, when the device risk factor corresponds to no risk, the verification process of all apps does not require human-computer interaction. When a suspected risk user verifies by shaking the phone, other apps also do not require human-computer interaction.

[0128] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the security authentication method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0129] This application also provides a security authentication device, please refer to Figure 6 , the safety authentication device includes:

[0130] A lock value updating module 10, configured to update a lock value of a security lock of a corresponding block of the terminal device based on a risk level of a user interaction behavior on the terminal device;

[0131] The data security module 20 is used to determine the current state of the security lock of the target block based on the lock value of the security lock of the target block when receiving a data query request of the target block;

[0132] The data security module 20 is further configured to safely return the data of the target block when the current state of the security lock of the target block is unlocked.

[0133] In a feasible implementation manner, the lock value update module 10 is further used to obtain the operating environment detection result, historical interaction record, device identity information and device address information of the terminal device;

[0134] After the operating environment detection result, device identity information, and device address information of the terminal device pass integrity verification and validity verification, the risk coefficient of the user interaction behavior on the terminal device is calculated based on the operating environment detection result and historical interaction records of the terminal device;

[0135] Determining an initial risk level of the user interaction behavior on the terminal device based on a risk level range within which the risk coefficient of the terminal device complies;

[0136] Based on the device address information of the terminal device, the initial risk level is adjusted to obtain the risk level of the user interaction behavior on the terminal device.

[0137] In a feasible implementation manner, the lock value updating module 10 is further used to determine the number of problems existing in the environment detection content of the terminal device based on the operating environment detection result of the terminal device;

[0138] Determining the interaction risk value of the interactive software in the terminal device based on the historical interaction record of the terminal device;

[0139] Based on smart contracts, determine the number of problems in the environmental detection content, the interaction risk value of the interactive software, the weight of the environmental detection, and the corresponding relationship between the interaction weight and risk coefficient;

[0140] Based on the number of problems in the environment detection content in the terminal device, the interaction risk value of the interactive software in the terminal device, the weight of the environment detection, the weight of the interaction, the number of interactive software and the corresponding relationship, the risk coefficient of the user interaction behavior on the terminal device is determined.

[0141] In a feasible implementation manner, the lock value updating module 10 is further used to obtain the lock value of the security lock of the corresponding block of the terminal device when the risk level of the user interaction behavior on the terminal device is a high risk behavior level;

[0142] When the lock value of the security lock of the block corresponding to the terminal device is an odd number, continue to maintain the lock value of the security lock of the block corresponding to the terminal device;

[0143] When the lock value of the security lock of the block corresponding to the terminal device is an even number, the lock value of the security lock of the block corresponding to the terminal device is increased by a preset incremental value so that the lock value of the security lock of the block corresponding to the terminal device meets an odd number after adjustment.

[0144] In a feasible implementation manner, the data security module 20 is further configured to determine that the current state of the security lock of the target block is a locked state when the lock value of the security lock of the target block is a first value;

[0145] When the lock value of the security lock of the target block is a second value, determining that the current state of the security lock of the target block is an unlocked state, and the second value is greater than the first value;

[0146] When the lock value of the security lock of the target block is greater than a second value, it is determined that the current state of the security lock of the target block is a repeatedly locked and unlocked state.

[0147] In a feasible implementation manner, the data security module 20 is further used to generate a preset number of random strategies in nodes that meet the requirements, and randomly divide the random strategies that have been agreed upon to other nodes to obtain available strategies for each node;

[0148] When the risk level of the user interaction behavior on the terminal device is a suspected risk behavior level, determining a current use policy based on available policies stored in a request node of the terminal device;

[0149] Based on the current usage policy, security verification is performed on the user interaction behavior to obtain corresponding interaction behavior verification data, and the current usage policy is deleted from the available policies of the requesting node;

[0150] After the user interaction behavior passes the security verification, the user interaction behavior on the terminal device is allowed.

[0151] The security authentication device provided by the present application adopts the security authentication method in the above embodiment, which can solve the technical problems that the traditional verification method has information security risks and user data is easily maliciously accessed. Compared with the prior art, the beneficial effects of the security authentication device provided by the present application are the same as the beneficial effects of the security authentication method provided by the above embodiment, and the other technical features in the security authentication device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0152] The present application provides a security authentication device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the security authentication method in the above-mentioned embodiment one.

[0153] Reference below Figure 7, which shows a schematic diagram of the structure of a security authentication device suitable for implementing the embodiment of the present application. The security authentication device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 7 The security authentication device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0154] like Figure 7 As shown, the security authentication device may include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the security authentication device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the security authentication device to communicate with other devices wirelessly or by wire to exchange data. Although the figure shows a security authentication device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.

[0155] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0156] The security authentication device provided by the present application adopts the security authentication method in the above embodiment, which can solve the technical problems that the traditional verification method has information security risks and user data is easily accessed maliciously. Compared with the prior art, the beneficial effects of the security authentication device provided by the present application are the same as the beneficial effects of the security authentication method provided by the above embodiment, and the other technical features in the security authentication device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0157] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0158] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0159] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, wherein the computer-readable program instructions are used to execute the security authentication method in the above-mentioned embodiment.

[0160] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0161] The above-mentioned computer-readable storage medium may be included in the security authentication device; or it may exist independently without being assembled into the security authentication device.

[0162] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the security authentication device, the security authentication device: updates the lock value of the security lock of the corresponding block of the terminal device based on the risk level of the user interaction behavior on the terminal device; when receiving a data query request for the target block, determines the current state of the security lock of the target block based on the lock value of the security lock of the target block; when the current state of the security lock of the target block is unlocked, securely returns the data of the target block.

[0163] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0164] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0165] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.

[0166] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned security authentication method, and can solve the technical problems that the traditional authentication method has information security risks and user data is easily maliciously accessed. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the security authentication method provided by the above-mentioned embodiment, and will not be repeated here.

[0167] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned security authentication method when executed by a processor.

[0168] The computer program product provided by this application can solve the technical problem that the traditional authentication method has information security risks and user data is easily accessed by malicious persons. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as those of the security authentication method provided by the above embodiment, and will not be elaborated here.

[0169] The above are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A security authentication method, characterized in that: Applied to a consortium chain, the consortium chain is provided with a plurality of blocks, the plurality of blocks correspond to different terminal devices one by one, and the plurality of blocks are provided with a security lock, the method comprises: Based on the risk level of the user interaction behavior on the terminal device, updating the lock value of the security lock of the corresponding block of the terminal device; When receiving a data query request for a target block, determining a current state of a security lock of the target block based on a lock value of the security lock of the target block; When the current state of the security lock of the target block is unlocked, the data of the target block is safely returned.

2. The method according to claim 1, characterized in that Before the step of updating the lock value of the security lock of the block corresponding to the terminal device based on the risk level of the user interaction behavior on the terminal device, the method further includes: Obtaining the operating environment detection results, historical interaction records, device identity information, and device address information of the terminal device; After the operating environment detection result, device identity information, and device address information of the terminal device pass integrity verification and validity verification, the risk coefficient of the user interaction behavior on the terminal device is calculated based on the operating environment detection result and historical interaction records of the terminal device; Determining an initial risk level of the user interaction behavior on the terminal device based on a risk level range within which the risk coefficient of the terminal device complies; Based on the device address information of the terminal device, the initial risk level is adjusted to obtain the risk level of the user interaction behavior on the terminal device.

3. The method according to claim 2, characterized in that The alliance chain has a consensus-based smart contract, and the step of calculating the risk coefficient of the user interaction behavior on the terminal device based on the operating environment detection result and the historical interaction record of the terminal device includes: Based on the operating environment detection result of the terminal device, determine the number of problems existing in the environment detection content of the terminal device; Determining the interaction risk value of the interactive software in the terminal device based on the historical interaction record of the terminal device; Based on the smart contract, determine the number of problems in the environmental detection content, the interaction risk value of the interactive software, the weight of the environmental detection, and the corresponding relationship between the interaction weight and the risk coefficient; Based on the number of problems in the environment detection content in the terminal device, the interaction risk value of the interactive software in the terminal device, the weight of the environment detection, the weight of the interaction, the number of interactive software and the corresponding relationship, the risk coefficient of the user interaction behavior on the terminal device is determined.

4. The method according to claim 1, characterized in that The step of updating the lock value of the security lock of the corresponding block of the terminal device based on the risk level of the user interaction behavior on the terminal device includes: When the risk level of the user interaction behavior on the terminal device is a high-risk behavior level, obtaining a lock value of a security lock of a block corresponding to the terminal device; When the lock value of the security lock of the block corresponding to the terminal device is an odd number, continue to maintain the lock value of the security lock of the block corresponding to the terminal device; When the lock value of the security lock of the block corresponding to the terminal device is an even number, the lock value of the security lock of the block corresponding to the terminal device is increased by a preset incremental value so that the lock value of the security lock of the block corresponding to the terminal device meets an odd number after adjustment.

5. The method according to claim 1, characterized in that The step of determining the current state of the security lock of the target block based on the lock value of the security lock of the target block upon receiving the data query request of the target block comprises: When the lock value of the security lock of the target block is a first value, determining that the current state of the security lock of the target block is a locked state; When the lock value of the security lock of the target block is a second value, determining that the current state of the security lock of the target block is an unlocked state, and the second value is greater than the first value; When the lock value of the security lock of the target block is greater than a second value, it is determined that the current state of the security lock of the target block is a repeatedly locked and unlocked state.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Generate a preset number of random strategies in nodes that meet the requirements, and randomly divide the random strategies that have reached consensus to other nodes to obtain available strategies for each node; When the risk level of the user interaction behavior on the terminal device is a suspected risk behavior level, determining a current use policy based on available policies stored in a request node of the terminal device; Based on the current usage policy, security verification is performed on the user interaction behavior to obtain corresponding interaction behavior verification data, and the current usage policy is deleted from the available policies of the requesting node; After the user interaction behavior passes the security verification, the user interaction behavior on the terminal device is allowed.

7. A security authentication device, characterized in that: The device comprises: A lock value updating module, used to update the lock value of the security lock of the corresponding block of the terminal device based on the risk level of the user interaction behavior on the terminal device; A data security module, configured to determine a current state of a security lock of a target block based on a lock value of the security lock of the target block when receiving a data query request of the target block; The data security module is further configured to safely return the data of the target block when the current state of the security lock of the target block is an unlocked state.

8. A security authentication device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the security authentication method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the security authentication method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the security authentication method according to any one of claims 1 to 6 are implemented.

Images