Identity authentication method and system, electronic equipment and storage medium
By receiving and verifying the client's identity authentication information, the problem that static identity authentication cannot provide continuous authentication is solved, the security of the zero-trust model is achieved, and the playback and man-in-the-middle attacks are prevented, ensuring the security of access rights.
Patent Information
- Application Number
- CN202410989387.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2044-07-23
AI Technical Summary
Static identity authentication cannot provide continuous authentication and authorization during user access to the application, cannot meet the security requirements of the zero-trust model, and existing dynamic authentication is difficult to defend against replay and man-in-the-middle attacks.
By receiving the client's identity authentication information during the login zero trust period, using the authentication information of the timestamp, token and target authentication items for identity authentication, granting or retaining access rights, and including exclusive tokens and randomly specified authentication in the authentication information update item to prevent replay and man-in-the-middle attacks.
Continuous identity authentication for zero-trust clients is realized, the security of access is enhanced, the playback and man-in-the-middle attacks are prevented, and the security of the zero-trust model is ensured.
Smart Images

Figure CN118965305A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and more specifically, to an identity authentication method, system, electronic device and storage medium. Background Art
[0002] With the continuous development of computer technology, in order to ensure the security of applications, users will be authenticated when they access corresponding applications, that is, the identity of users accessing the application will be authenticated through identity authentication technology, thereby protecting the security of the application.
[0003] The current identity authentication is generally divided into static identity authentication, among which static identity authentication includes password authentication, biometric authentication and hardware authentication; however, static identity authentication can only provide identity verification function before accessing the application, and cannot provide authentication during access to the application. In zero trust, every user, device or system needs to be authenticated and authorized when accessing resources, regardless of whether it is inside or outside the network, so the use of static identity authentication cannot guarantee the security of the zero trust model. Among them, Zero Trust is a network security model whose basic principle is not to trust any entity in the IT environment, which means that in zero trust, every user, device or system needs to be authenticated and authorized when accessing resources, regardless of whether it is inside or outside the network.
[0004] Therefore, providing a continuous authentication method for a zero-trust model to ensure the security of zero-trust during access is an issue that urgently needs to be addressed in this application. Summary of the invention
[0005] In view of this, the present application provides an identity authentication method, system, electronic device and storage medium to achieve continuous identity authentication for clients logging into zero trust, thereby ensuring the security of zero trust during the access period.
[0006] The first aspect of the present application provides an identity authentication method, which is applied to a zero-trust controller, and the method includes:
[0007] Receive identity authentication information sent by the client during zero-trust login; wherein the identity authentication information includes a timestamp, a token, and authentication information of multiple target authentication items;
[0008] If the identity authentication information is the first identity authentication information, determine the identity authentication score of the client according to the authentication information of each second authentication item; the second authentication item is any one of the target authentication items except the first authentication item and the third authentication item;
[0009] If the identity authentication score is greater than or equal to a preset weighted average score, verifying the authentication information of the first authentication item in each of the target authentication items;
[0010] If the authentication information of the first authentication item in each target authentication item is verified, granting the client access to the zero-trust access right and updating the identity authentication information;
[0011] If the identity authentication information is not the first identity authentication information, judging whether the client satisfies the identity authentication condition according to the identity authentication information;
[0012] If the client satisfies the identity authentication condition, determining the identity authentication score of the client according to the authentication information of each of the target authentication items;
[0013] If the identity authentication score is greater than or equal to the preset weighted average score, retain the client's access rights to the zero trust and update the identity authentication information;
[0014] The updated identity authentication information is sent to the client, so that the client sends the updated identity authentication information to the zero trust controller during the zero trust login period.
[0015] Optionally, if the client satisfies the identity authentication condition, determining the identity authentication score of the client according to the authentication information of each of the target authentication items includes:
[0016] If the client satisfies the identity authentication condition, determining whether there is a third authentication item in each of the target authentication items;
[0017] If the third authentication item does not exist in each of the target authentication items, scoring each of the target authentication items according to the authentication information of each of the target authentication items;
[0018] The scores of the target authentication items are weighted averagely calculated to obtain the identity authentication score of the client.
[0019] Optionally, the method further includes:
[0020] If the third authentication item exists in each of the target authentication items, determining whether the authentication information of the third authentication item in each of the target authentication items is the same as the authentication information of the third authentication item in the first identity authentication information;
[0021] If the authentication information of the third authentication item in each of the target authentication items is the same as the authentication information of the third authentication item in the first identity authentication information, the step of determining the identity authentication score of the client according to the authentication information of each of the second authentication items is performed.
[0022] Optionally, determining the identity authentication score of the client according to the authentication information of each second authentication item includes:
[0023] Score each second authentication item according to the authentication information of each second authentication item;
[0024] An average weighted calculation is performed on the scores of each of the second authentication items to obtain the identity authentication score of the client.
[0025] Optionally, when the identity authentication information is the first identity authentication information, updating the identity authentication information includes:
[0026] Generate a unique Token and access timestamp for the client, and randomly specify multiple authentication items from pre-set authentication items;
[0027] The multiple target authentication items in the identity authentication information are updated using the multiple randomly specified authentication items, and the Token and the timestamp in the identity authentication information are updated using the exclusive Token and the access timestamp.
[0028] Optionally, when the identity authentication information is not the first identity authentication information, updating the identity authentication information includes:
[0029] Randomly specify multiple authentication items from pre-set authentication items;
[0030] The plurality of target authentication items in the identity authentication information are updated using the plurality of randomly specified authentication items.
[0031] Optionally, if the identity authentication information is not the first identity authentication information, judging whether the client satisfies an identity authentication condition according to the identity authentication information includes:
[0032] If the identity authentication information is not the first identity authentication information, obtaining a plurality of authentication items randomly specified when the identity authentication of the client was passed last time;
[0033] If the multiple authentication items randomly specified when the last identity authentication of the client was passed are the same as the target authentication items in the identity authentication information, verify the timestamp and the Token;
[0034] If the timestamp and the token are verified, it is determined that the client meets the identity authentication condition;
[0035] If any of the target authentication items is different from at least one authentication item randomly specified when the identity authentication of the client was passed last time, and / or the timestamp verification fails, and / or the Token verification fails, it is determined that the client does not meet the identity authentication conditions.
[0036] A second aspect of the present application provides an identity authentication system, which is applied to a zero-trust controller. The system includes:
[0037] A receiving unit, configured to receive identity authentication information sent by a client during zero-trust login; wherein the identity authentication information includes a timestamp, a token, and authentication information of multiple target authentication items;
[0038] A first identity authentication score determination unit is used to determine the identity authentication score of the client according to the authentication information of each second authentication item if the identity authentication information is the first identity authentication information; the second authentication item is any target authentication item among the target authentication items except the first authentication item and the third authentication item;
[0039] A first verification unit, configured to verify the authentication information of the first authentication item in each of the target authentication items if the identity authentication score is greater than or equal to a preset weighted average score;
[0040] a granting unit, configured to grant the client access to the zero-trust access right and update the identity authentication information if the authentication information of the first authentication item in each target authentication item is verified to be passed;
[0041] A first judgment unit, configured to judge whether the client satisfies an identity authentication condition according to the identity authentication information if the identity authentication information is not the first identity authentication information;
[0042] A second identity authentication score determination unit, configured to determine the identity authentication score of the client according to the authentication information of each of the target authentication items if the client satisfies the identity authentication condition;
[0043] An updating unit, configured to retain the client's access rights to the zero-trust access and update the identity authentication information if the identity authentication score is greater than or equal to a preset weighted average score;
[0044] A sending unit is used to send the updated identity authentication information to the client, so that the client sends the updated identity authentication information to the zero trust controller during the zero trust login period.
[0045] The third aspect of the present application provides an electronic device, comprising: a processor and a memory, wherein the processor and the memory are connected via a communication bus; wherein the processor is used to call and execute a program stored in the memory; and the memory is used to store a program, wherein the program is used to implement the identity authentication method provided in the first aspect of the present application.
[0046] The fourth aspect of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and the computer-executable instructions are used to execute the identity authentication method provided in the first aspect of the present application.
[0047] The present application provides an identity authentication method, system, electronic device and storage medium, which receive identity authentication information sent by a client during zero-trust login; wherein the identity authentication information includes a timestamp, a token and authentication information of multiple target authentication items; if the identity authentication information is the first identity authentication information, the identity authentication score of the client is determined according to the authentication information of each second authentication item; the second authentication item is any one of the target authentication items except the first authentication item and the third authentication; if the identity authentication score is greater than or equal to a preset weighted average score, the authentication information of the first authentication item in each target authentication item is verified; if the first authentication item in each target authentication item is greater than or equal to a preset weighted average score, the authentication information of the first authentication item in each target authentication item is verified; if the first authentication item in each target authentication item is greater than or equal to a preset weighted average score, the authentication information of the first authentication item in each target authentication item is verified. If the authentication information of the authentication item is verified, the client is granted access to zero trust, and the authentication information is updated; if the authentication information is not the first authentication information, determine whether the client meets the authentication conditions based on the authentication information; if the client meets the authentication conditions, determine the client's authentication score based on the authentication information of each target authentication item; if the authentication score is greater than or equal to the preset weighted average score, retain the client's access to zero trust, and update the authentication information; send the updated authentication information to the client, so that the client sends the updated authentication information to the zero trust controller during the zero trust login period. It can be seen that the technical solution provided by the present application can receive the authentication information sent by the client during the client's access to zero trust, authenticate the client using the received authentication information, and grant or retain the client's access to zero trust if the client's authentication passes, and update the authentication information at the same time, so that the client sends the updated authentication information to the zero trust controller during the zero trust login period, so as to achieve continuous authentication of clients accessing zero trust and ensure the security of zero trust during the access period. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] 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, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.
[0049] Figure 1 A flowchart of an identity authentication method provided in an embodiment of the present application;
[0050] Figure 2 A flowchart of another identity authentication method provided in an embodiment of the present application;
[0051] Figure 3 A schematic diagram of the structure of an identity authentication system provided in an embodiment of the present application;
[0052] Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0053] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0054] In this application, relational terms such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.
[0055] It should be noted that user-related data: in the technical solution disclosed in this application, the acquisition, collection, storage, use, processing, transmission, provision, disclosure and application of data are in compliance with the relevant laws and regulations, necessary confidentiality measures have been taken, and do not violate public order and good morals.
[0056] From the above background technology, it can be seen that static identity authentication can only verify the identity of the client accessing the application before accessing the application, and cannot perform identity authentication during access to the application. Zero trust requires each user, device or system to be authenticated and authorized during access, which results in the use of static identity authentication. It is impossible to guarantee the security of zero trust during the access period.
[0057] In the existing technology, the identity of clients accessing zero trust can be continuously authenticated through dynamic authentication, but the existing dynamic authentication is difficult to deal with replay and man-in-the-middle eavesdropping attacks, and also cannot guarantee the security of zero trust during the access period.
[0058] Therefore, the present application provides an identity authentication method, system, electronic device and storage medium, which receives the identity authentication information sent by the client during the zero-trust login period, and uses the timestamp, token and authentication information of each target authentication item in the identity authentication information to authenticate the client, so as to grant or retain the client's access to zero trust when it is determined that the identity authentication of the client has passed, which can effectively prevent clients with security risks from accessing zero trust, and at the same time block attacked clients from accessing zero trust; after retaining the client's access rights, in order to ensure that the authentication process is protected from replay attacks and man-in-the-middle attacks, the identity authentication information can also be updated, and finally the updated identity authentication information and access timestamp are sent to the client, so that the client sends the updated identity authentication information to the zero-trust controller during the zero-trust login period.
[0059] See also Figure 1 , shows a flow chart of an identity authentication method provided in an embodiment of the present application, which is applied to a zero trust controller. The identity authentication method specifically includes the following steps:
[0060] S101: Receive the identity authentication information sent by the client during the zero-trust login period, and determine whether the identity authentication information is the first identity authentication information; wherein the identity authentication information includes a timestamp, a token, and authentication information of multiple target authentication items; if the identity authentication information is the first identity authentication information, execute step S102; if the identity authentication information is not the first identity authentication information, execute step S104.
[0061] In the specific process of executing step S101, since the client that needs to access zero trust needs to perform corresponding authentication and authorization when accessing the corresponding resources, after logging into zero trust, the client can obtain its own timestamp, Token and authentication information of multiple target authentication items, and generate corresponding identity authentication information based on the timestamp, Token and multiple target authentication items and authentication information, so as to send the identity authentication information to zero trust control, so that zero trust control can use the received identity authentication information to perform corresponding identity authentication on the client that logs in to zero trust, thereby ensuring the security of zero trust during the access period.
[0062] In some embodiments, if the identity authentication information sent by the client is the first identity authentication information, then the Token obtained when the client generates the corresponding identity authentication information is a Token pre-determined with zero trust, and the multiple target authentication items are multiple authentication items that are pre-set; if the identity authentication information sent by the client is not the first identity authentication information, then the Token obtained when the client generates the corresponding identity authentication information is an exclusive Token generated when the zero trust control last authenticated the client, and the multiple target authentication items are multiple authentication items randomly specified from the pre-set authentication items when the zero trust control last authenticated the client.
[0063] It should be noted that the pre-set authentication items may include user name and password authentication item AUTH_0, CPU, hard disk and network card authentication item AUTH_1, system security policy authentication item AUTH_2, patch installation authentication item AUTH_3, virus detection authentication item AUTH_4, client sensitive behavior authentication item AUTH_5 and client peripheral perception authentication item AUTH_6, etc., which can be set according to actual applications and are not limited in the embodiments of this application.
[0064] It is worth noting that if the identity authentication information sent by the client is the first identity authentication information, then the identity authentication information must include the Token and the authentication information of all pre-set authentication items, that is, the multiple target authentication items in the identity authentication information include user name and password authentication items, CPU and network card authentication items, system security policy authentication items, patch installation authentication items, virus detection and killing authentication items, client sensitive behavior authentication items and client peripheral perception authentication items; if the identity authentication information is not the first identity authentication information, then the multiple target authentication items in the identity authentication information are 3 authentication items or 4 authentication items randomly specified from the pre-set authentication items when the zero trust control passed the identity authentication of the client last time. They can be specified according to the actual application, and are not limited to this embodiment of the present application.
[0065] Optionally, the process of determining whether the identity authentication information is the first identity authentication information may specifically be as follows: determining whether the currently received identity authentication information is the first identity authentication information sent by the client during the zero-trust login period; if the identity authentication information is not the first identity authentication information sent by the client during the zero-trust login period, determining that the identity authentication is not the first identity authentication information, and then executing step S104; if the identity authentication information is the first identity authentication information sent by the client during the zero-trust login period, determining that the identity authentication information is the first identity authentication information, and then executing step S102.
[0066] It should be noted that if the identity authentication information is the first identity authentication information, then the timestamp in the identity authentication information can be the current timestamp when the client sends the identity authentication information; if the identity authentication information is not the first identity authentication information, then the timestamp in the identity authentication information can be the timestamp generated by the zero trust controller when it uses the first identity authentication information sent by the client to authenticate the client.
[0067] S102: Determine the identity authentication score of the client according to the authentication information of each second authentication item; the second authentication item is any authentication item among the target authentication items except the first authentication item and the third authentication item.
[0068] In the process of specifically executing step S103, when it is determined that the currently received identity authentication information is the first identity authentication information, each authentication item other than the first authentication item and the third authentication item can be further determined from each target authentication item. For the sake of easy distinction, the authentication items other than the first authentication item and the third authentication item are called second authentication items, and the authentication information of each second authentication item is used to determine the client's identity authentication score.
[0069] Optionally, the process of determining the client's identity authentication score based on the authentication information of each second authentication item specifically includes: scoring each second authentication item based on the authentication information of each second authentication item; performing an average weighted calculation on the scores of each second authentication item to obtain the client's identity authentication score.
[0070] In some embodiments, the weighted weight of each authentication item other than the first authentication item and the third authentication item can be pre-configured, so that after obtaining the score of each second authentication item, the score of each second authentication item can be multiplied by the corresponding weighted weight to obtain the weighted score of each second authentication item, and finally the weighted scores of each second authentication item are added to obtain the total weighted score, that is, the client's identity authentication score.
[0071] For example, the weighted weight corresponding to the system security policy authentication item can be preset to 15%, the weighted weight corresponding to the patch installation authentication item to 30%, the weighted weight corresponding to the virus detection authentication item to 15%, the weighted weight of the client sensitive behavior authentication item to 20%, and the weighted weight of the client external device authentication item to 20%.
[0072] It should be noted that the second authentication item can be a system security policy authentication item, a patch installation authentication item, a virus detection authentication item, a client sensitive behavior authentication item and a client peripheral perception authentication item, which can be configured according to actual applications and is not limited in this embodiment of the present application.
[0073] As an implementation method of an embodiment of the present application, if the second authentication item is a system security policy authentication item, the process of scoring the second authentication item based on the authentication information of the second authentication item can specifically be: determining various security policies related to the system security policy; determining at least one target security policy applied in the client from various security policies based on the authentication information of the system security policy authentication item; determining the score of the system security policy authentication item based on the pre-set danger level corresponding to each target security policy and its scoring weight.
[0074] It should be noted that the target security policy item is a security policy item that is not applied in the client.
[0075] In an embodiment of the present application, a system security policy related to a system security policy authentication item may be pre-set, wherein the system security policy may include multiple security policy items, wherein the pre-set system security policy related to the system security policy authentication item may be user and user group management, user login password configuration and login failure processing, system log auditing, sharing policy and remote access, power management, firewall configuration and other security policies, which may be set according to actual applications and are not limited in the embodiment of the present application.
[0076] It should be noted that the danger level can be divided into: serious, high risk, medium risk, etc. Correspondingly, the pre-configured system security policy can include 9 security policies, namely: The danger level is serious: 1.1: Disable the Guest account; 1.2. The password length is not less than 8 characters, including any three of uppercase and lowercase letters, numbers, and characters; 1.3. Turn off Windows default sharing; The danger level is high risk: 2.1. The last login user name is not displayed when logging into the operating system; 2.2. Limit anonymous user connection permissions to prevent users from remotely enumerating local accounts; 2.3. Only designated authorized accounts are allowed to shut down the host; The danger level is medium risk: 3.1. 10 days before the password expires, remind the user to change the password to avoid account invalidation due to forgetting; 3.2. Set the Windows system log file size; 3.3. Set the Windows system log storage path. The specific content of the system security policy can be set according to the actual application, and this embodiment of the application is not limited here.
[0077] For example, the danger level corresponding to each security policy and the scoring weight corresponding to each danger level can be preset, wherein the scoring weight of the danger level of severe is 20%, the scoring weight of the danger level of high risk is 10%, and the scoring weight of the danger level of medium risk is 5%. If the authentication information of the system security policy authentication item in the received identity authentication information indicates that 1.1 has been applied, 1.2 has been applied, 1.3 has not been applied, 2.1 has not been applied, 2.2 has been applied, 2.3 has been applied, 3.1 has been applied, 3.2 has not been applied, and 3.3 has not been applied, it can be determined that the target security policies are divided into 1.3, 2.1, 3.2 and 3.3; if the total score of the system security policy authentication item is 100 points, then according to the preset danger level corresponding to each target security policy and its scoring weight, the score of the system security policy authentication item can be calculated as 100-(100*20%+100*10%+100*5%+100*5%)=60 points.
[0078] As an implementation method of an embodiment of the present application, if the second authentication item is a patch installation authentication item, the process of scoring the second authentication item based on the authentication information of the second authentication item can specifically be: comparing the target patch indicated by the authentication information of the patch installation authentication item with a pre-configured patch library; if the comparison is successful, determining the score of the patch installation authentication item based on the scoring rules of the target patch and the patch installation authentication item; if the comparison fails, determining the score of the patch installation authentication item as 0.
[0079] In actual application, corresponding patch libraries and corresponding scoring rules can be pre-set. For example, the patch library can include vulnerability patches with Common Vulnerability Scoring System (CVSS) levels, high-risk vulnerability patches, medium-risk vulnerability patches, etc. The scoring rule can be that if a vulnerability patch with a serious CVSS level is not installed on the client, the total score of the patch installation authentication item will be directly deducted to 0 points; if a high-risk vulnerability patch is not installed on the client, 20 points will be deducted from the total score of the patch installation authentication item; if the medium-risk vulnerability patch is not installed on the client, 10 points will be deducted from the total score of the patch installation authentication item.
[0080] For example, if it is determined that there are two target patches indicated by the authentication information of the patch installation authentication item in the currently received identity authentication information, and the target patch is the patch currently installed on the client, each target patch is compared with the patch library; if the comparison is successful, that is, the comparison result indicates that one target patch is a vulnerability patch with a CVSS level, and the other target patch is a medium-risk vulnerability patch, then it can be explained that a high-risk vulnerability patch is currently installed on the client, and 20 points can be deducted from the total score (100 points) of the patch installation authentication item, and the score of the patch installation authentication item is 80 points; if the comparison fails, the target patch is not a patch in the patch library, and the score of the patch installation authentication item is determined to be 0.
[0081] As an implementation method of an embodiment of the present application, if the second authentication item is a virus detection authentication item, the process of scoring the second authentication item based on the authentication information of the second authentication item can specifically be: determining the virus detection tool indicated in the authentication information of the virus detection authentication item, and obtaining the timestamp of the virus detection tool's most recent full-disk virus detection; determining the score of the virus detection authentication based on the timestamp of the most recent full-disk virus detection and the timestamp in the identity authentication information.
[0082] In the actual process, the difference between the timestamp of the most recent full-disk virus scan and the timestamp in the identity authentication information can be calculated, and the target time period to which the difference belongs in the pre-set time periods can be determined, and the score weight corresponding to the target time period can be used to calculate the score of the virus scan authentication item.
[0083] For example, multiple preset time periods can be pre-set, wherein the multiple preset time periods are respectively less than 60 days and greater than 30 days, and greater than 60 days. The corresponding scoring weight for less than 60 days and greater than 30 days is 95%, and the corresponding scoring weight for greater than 60 days is 90%, and the total score of the virus detection and killing authentication item is 100 points; if the difference between the timestamp of the most recent full-disk virus detection and the timestamp in the identity authentication information is 40 days, then it can be determined that the target time period to which the difference between the timestamp of the most recent full-disk virus detection and the timestamp in the identity authentication information belongs is less than 60 days and greater than 30 days, and then the score of the virus detection and killing authentication item can be determined to be 95 points.
[0084] As an implementation method of an embodiment of the present application, if the second authentication item is a client-sensitive behavior, the process of scoring the second authentication item based on the authentication information of the second authentication item can specifically be: determining at least one client-sensitive behavior indicated in the authentication information of the client-sensitive behavior authentication item; for each client-sensitive behavior, judging whether the client-sensitive behavior belongs to a sensitive behavior in a pre-set zero-trust blacklist; if so, the score of the client-sensitive behavior authentication item can be determined to be 0; if not, it can be further judged whether the client-sensitive behavior belongs to a sensitive behavior in a pre-set whitelist; if so, the scoring weight that matches the client-sensitive behavior can be determined; if not, the client-sensitive behavior is eliminated; the score of the client-sensitive behavior authentication item is calculated according to the scoring weight of each client-sensitive behavior.
[0085] In actual application, a zero-trust blacklist can be set in advance, wherein the sensitive behavior in the zero-trust blacklist can be a blacklisted program running on the client or the client communicating with a blacklisted IP; accordingly, after determining at least one client sensitive behavior indicated in the authentication information of the client sensitive behavior authentication item, it can be determined whether the program running on the client indicated in the client sensitive behavior is a blacklisted program or whether the IP communicating with the client indicated in the client sensitive behavior is a blacklisted IP; if the program running on the client indicated in the client sensitive behavior is a blacklisted program or the IP communicating with the client indicated in the client sensitive behavior is a blacklisted IP, it can be determined that the client sensitive behavior belongs to the sensitive behavior in the zero-trust blacklist.
[0086] In actual applications, a whitelist is also pre-set, wherein the sensitive behaviors in the whitelist may be a non-whitelisted program running on the client or the client communicating with a non-whitelisted IP, that is, a program outside the whitelist running on the client or the client communicating with an IP outside the whitelist; accordingly, it is determined whether the program running on the client indicated in the client sensitive behavior is a whitelisted program or whether the IP communicating with the client indicated in the client sensitive behavior is a whitelisted IP; if the program running on the client indicated in the client sensitive behavior is not a whitelisted program or the IP communicating with the client indicated in the client sensitive behavior is not a whitelisted IP, it can be determined that the client sensitive behavior belongs to the sensitive behavior in the whitelist, and then the scoring weight of the client sensitive behavior can be determined.
[0087] It should be noted that, when the client sensitive behavior belongs to the sensitive behavior in the whitelist, the scoring weight of the client sensitive behavior can be set to 5%. That is to say, when the client sensitive behavior belongs to the sensitive behavior in the whitelist, 5 points will be deducted from the total score of the client sensitive behavior authentication item.
[0088] It should also be noted that as long as there is one client sensitive behavior that belongs to the sensitive behavior in the zero trust blacklist, the score of the client sensitive behavior authentication item can be set to 0; assuming that there are 5 client sensitive behaviors that belong to the sensitive behavior in the whitelist, 25 points can be deducted from the total score of the client sensitive behavior authentication item, and the score of the client sensitive behavior authentication item is 75 points.
[0089] As an implementation method of an embodiment of the present application, if the second authentication item is a client peripheral perception authentication item, the process of scoring the second authentication item according to the authentication information of the second authentication item can specifically be: determining at least one external device behavior indicated in the authentication information of the client peripheral perception authentication item, and for each external device behavior, judging whether the external device indicated in the external device behavior belongs to an external device in the whitelist; if not, determining the scoring weight corresponding to the external device behavior; if yes, excluding the external device behavior; determining the score of the client peripheral perception authentication item according to the scoring weights of each external device behavior.
[0090] It should be noted that the external device behavior refers to the behavior of an external device accessing the client, wherein the external device may be a USB, a camera, etc., which is not limited in the embodiments of the present application.
[0091] In actual application, the zero-trust architecture opens the peripheral whitelist, and the whitelist includes multiple pre-configured external devices. The score weight of the external device behavior of the external device that is not included in the whitelist and connected to the client can be set to 5%. That is to say, when an external device that is not included in the whitelist is connected to the client, the total score of the client peripheral perception authentication item will be deducted by 5 points. For example, if it is determined based on the authentication information of the client peripheral perception authentication item that there are 5 external devices with external device behavior indications that do not belong to the external devices in the whitelist, then 25 points can be deducted from the total score (100 points) of the client peripheral perception authentication item, and the score of the client peripheral perception authentication item is 75 points.
[0092] It is worth noting that in the process of authenticating the client, the zero-trust controller collects authentication information for the CPU and network card authentication items, system security policy authentication items, patch installation authentication items, and virus killing authentication items, and uses the authentication information of the CPU and network card authentication items, system security policy authentication items, patch installation authentication items, and virus killing authentication items to participate in the client's identity authentication, which can effectively prevent clients with security risks from accessing protected resources in zero trust. At the same time, in the process of authenticating the client, the zero-trust controller collects authentication information for client sensitive behavior authentication items and client external device authentication items, and uses the authentication information of client sensitive behavior authentication items and client external device authentication items to participate in the client's identity authentication, which can promptly block the attacked client from accessing zero trust, thereby protecting the security of zero trust.
[0093] S103: Determine whether the identity authentication score of the client is greater than or equal to a preset weighted average score; if the identity authentication score is greater than or equal to the preset weighted average score, execute step S104.
[0094] In the process of specifically executing step S103, a corresponding preset weighted average score can be set in advance, so that after determining the identity authentication score of the client's first identity authentication, it can be further determined whether the client's identity authentication score is greater than or equal to the preset weighted average score. If the identity authentication score is greater than or equal to the preset weighted average score, it is determined that the client's first identity authentication is passed, and step S104 is executed; if the identity authentication score is not greater than or equal to the preset weighted average score, it is determined that the client's first identity authentication has failed, and the client is not granted access to zero trust, thereby preventing clients with security risks from accessing zero trust and ensuring the security of zero trust.
[0095] It should be noted that the preset weighted average score can be 80 points, 85 points, etc., and can be set according to actual applications, and is not limited in this embodiment of the present application.
[0096] S104: verify the authentication information of the first authentication item in each target authentication item; if the authentication information of the first authentication item in each target authentication item passes the verification, execute step S105.
[0097] In an embodiment of the present application, when the zero-trust controller determines that the client's first identity authentication has passed, it determines a first authentication item from each target authentication item, wherein the first authentication item is a user name and password authentication item, and the authentication information of the first authentication item includes the corresponding user name and password; obtains the target password according to the user name in the authentication information in the first authentication item, and compares the target password with the password in the authentication information of the first authentication item. If they are consistent, it is determined that the authentication information verification of the first authentication item has passed, and then step S105 can be executed; if they are inconsistent, it is determined that the authentication information verification of the first authentication item has failed. At this time, it can be determined that the client's first identity authentication has failed, and the client is not granted access to zero-trust access, thereby preventing clients with security risks from accessing protected resources.
[0098] It should be noted that the target password is the password agreed upon in advance between the client and zero trust corresponding to the user name, and can be configured according to actual applications, and is not limited in this embodiment of the present application.
[0099] Furthermore, in an embodiment of the present application, the CPU and network card authentication items in the pre-set authentication items can also be set as the third authentication, so that when it is determined that the authentication information of the first authentication item has been verified, the authentication information of the third authentication item is recorded, and the timestamp in the currently received identity authentication information is recorded and saved as T_Perv.
[0100] S105: Grant the client access rights to the zero trust and update the identity authentication information.
[0101] During the specific execution of step S105, when it is determined that the client's first identity authentication has passed, the client can be granted access rights to access Zero Trust so that the client can access Zero Trust based on the access rights. At the same time, the currently received authentication information (first identity authentication information) is sealed so that the client can continue to send the updated authentication information to the Zero Trust controller during the period of logging into Zero Trust, thereby achieving continuous authentication of clients accessing Zero Trust and ensuring the security of Zero Trust during the access period.
[0102] As a preferred method of an embodiment of the present application, when the identity authentication information is the first identity authentication information, the process of updating the identity authentication information can specifically be: generating a unique Token and access timestamp for the client, and randomly executing multiple authentication items from pre-set authentication items; using multiple randomly specified authentication items to update multiple target authentication items in the identity authentication information, and using the unique Token to update the Token in the identity authentication information, and then sending the access timestamp and the updated identity authentication information to the client, so that the client sends the updated identity authentication information to the zero trust controller according to the access timestamp during the zero trust login period.
[0103] In some embodiments, when the identity authentication information currently sent by the client is the first identity authentication information, if the client's identity authentication is successful using the identity authentication information, in order to ensure that subsequent continuous authentication processes avoid replay attacks and man-in-the-middle attacks, the client's exclusive Token and access timestamp can be regenerated, and at the same time, multiple authentication items can be randomly specified from the pre-set authentication items as target authentication items for the client's next identity authentication. Finally, the multiple randomly specified authentication items are used to update the multiple target authentication items in the identity authentication information, and the exclusive Token and access timestamp are used to update the Token and timestamp in the identity authentication information.
[0104] Furthermore, in an embodiment of the present application, a time interval T_Intv for the client to send updated authentication information next time may also be specified, so that the client sends the updated authentication information to the zero trust controller when the time from the current authentication is equal to the time interval T_Intv.
[0105] It should be noted that this application implements a challenge response mechanism by randomly specifying the authentication information (exclusive Token, access timestamp and randomly specified multiple authentication items) and time interval T_Intv required for the client's next authentication, thereby protecting the client from replay attacks and man-in-the-middle attacks during the authentication process.
[0106] S106: Determine whether the client satisfies the identity authentication conditions according to the identity authentication information; if the client satisfies the identity authentication conditions, execute step S107.
[0107] In the process of specifically executing step S104, when it is determined that the identity authentication information is not the first identity authentication information, multiple authentication items randomly specified when the last identity authentication of the client was passed can be obtained, and based on the multiple authentication items randomly specified when the last identity authentication of the client was passed, each target authentication item, the timestamp in the identity authentication information and the Token in the identity authentication information, it is judged whether the client meets the identity authentication conditions; if the client meets the identity authentication conditions, execute step S105; if the client does not meet the identity authentication conditions, it is determined that the identity authentication of the client has failed, and the client's access to zero trust is not retained, thereby preventing clients with security risks from accessing zero trust and ensuring the security of zero trust.
[0108] Optionally, if the identity authentication information is not the first identity authentication information, the process of determining whether the client meets the identity authentication conditions based on the identity authentication information can be specifically as follows: if the identity authentication information is not the first identity authentication information, obtain multiple authentication items randomly specified when the client's identity authentication was passed last time; if the multiple authentication items randomly specified when the client's identity authentication was passed last time are the same as the target authentication items in the identity authentication information, verify the timestamp Token in the identity authentication information; if the timestamp and Token in the identity authentication information pass the verification, determine that the client meets the identity authentication conditions; if any target authentication item is different from at least one authentication item randomly specified when the client's identity authentication was passed last time, and / or the timestamp verification in the identity authentication information fails, and / or the Token verification in the identity authentication information fails, determine that the client does not meet the identity authentication conditions.
[0109] It should be noted that the multiple authentication items randomly specified when the identity authentication of the client was successful last time are the multiple authentication items randomly specified when the identity authentication of the client was successful most recently.
[0110] Optionally, the process of verifying the timestamp and Token in the authentication information can specifically be: obtaining the timestamp of the last time the client's authentication was successful; verifying the timestamp in the authentication information based on the timestamp of the last time the client's authentication was successful; verifying the Token in the authentication information using the exclusive Token generated when the client's first authentication was successful.
[0111] In some embodiments, corresponding identity authentication conditions can be set in advance, wherein the identity authentication conditions indicate that when the currently received identity authentication information is not the first identity authentication information, each target authentication item in the currently received identity authentication information is consistent with each authentication item randomly specified when the last identity authentication of the client is passed, the Token in the currently received identity authentication information is consistent with the exclusive Token generated when it is determined that the client's first identity authentication is passed, and the timestamp in the currently received identity authentication information and the timestamp used when the identity authentication of the client is passed once satisfy the inequality T_Prev+T_Intv<=T<=T_Prev+1.2*T_Intv; wherein T_Prev is the timestamp used when the last identity authentication of the client is passed, T is the timestamp in the identity authentication information, and T_Intv is the time interval generated when the last identity authentication of the client is passed.
[0112] It should be noted that if the target authentication items in the currently received authentication information are inconsistent with the authentication items randomly specified when the client's authentication was successfully passed last time, and / or the token in the currently received authentication information is inconsistent with the token generated when the client's authentication was successfully passed last time, it can be considered that the currently received authentication information is incomplete or has more information than required, and the client's authentication can be considered to have failed. For example, the authentication items randomly specified by the zero-trust controller when the client's authentication was successfully passed last time include AUTH_2, AUTH_5, and AUTH_6, but the target authentication items in the authentication information currently sent by the client only include AUTH_2 and AUTH_5, or include AUTH_1, AUTH_2, and AUTH_6, then it can be considered that the authentication information received for this authentication does not match the authentication information required by the zero-trust controller, and the client's authentication can be considered to have failed this time.
[0113] It should also be noted that if the timestamp in the currently received authentication information and the timestamp used when the client's authentication was successful once do not satisfy the inequality T_Prev+T_Intv<=T<=T_Prev+1.2*T_Intv, it can also be considered that the client's authentication has failed.
[0114] S107: Determine the identity authentication score of the client according to the authentication information of each target authentication item.
[0115] In the specific execution of step S107, when it is determined that the client meets the identity authentication condition, it can be first determined whether there is a third authentication item in each target authentication item in the currently received identity authentication information. If not, it can be considered that each target authentication item is a second authentication item, and then each target authentication item can be scored according to the authentication information of each target authentication item; the scores of each target authentication item are averaged and weighted to obtain the identity authentication score of the client. If it exists, the authentication information of the third authentication item can be verified first. If the authentication information of the third authentication item passes the verification, the identity authentication score of the client can be determined according to the authentication information of each second authentication item in each target authentication item. Among them, the determination of the identity authentication score of the client according to the authentication information of each second authentication item in each target authentication item can refer to the corresponding process in step S102, and this embodiment of the present application is not limited here.
[0116] It should be noted that, when there is no third authentication item in each target authentication item, it can be considered that each target authentication item is a second authentication item. Therefore, each target authentication item is scored according to the authentication information of each target authentication item; the scores of each target authentication item are averaged and weighted to obtain the client's identity authentication score, which is equivalent to scoring each second authentication item according to the authentication information of each second authentication item; averaging and weighting the scores of each second authentication item to obtain the client's identity authentication score; accordingly, each second authentication item is scored according to the authentication information of each second authentication item; the scores of each second authentication item are averaged and weighted to obtain the client's identity authentication score. The process can be the corresponding process in step S102, and is not limited to this embodiment of the present application.
[0117] Optionally, the process of verifying the authentication information of the third authentication item may specifically include: determining whether the authentication information of the third authentication item in each target authentication item is the same as the authentication information of the third authentication item in the first identity authentication information; if the authentication information of the third authentication item in each target authentication item is the same as the authentication information of the third authentication item in the first identity authentication information, determining that the authentication information verification of the third authentication item has passed; if the authentication information of the third authentication item in each target authentication item is different from the authentication information of the third authentication item in the first identity authentication information, determining that the authentication information verification of the third authentication item has failed.
[0118] It should be noted that the third certification item is the CPU, hardware and network card certification item.
[0119] S108: Determine whether the identity authentication score of the client is greater than or equal to a preset weighted average score; if the identity authentication score is greater than or equal to the preset weighted average score, execute step S109.
[0120] In the process of specifically executing step S108, a corresponding preset weighted average score can be set in advance, so that after determining the identity authentication score of the client's current identity authentication, it can be further determined whether the client's identity authentication score is greater than or equal to the preset weighted average score. If the identity authentication score is greater than or equal to the preset weighted average score, step S109 is executed; if the identity authentication score is not greater than or equal to the preset weighted average score, it is determined that the client's identity authentication has failed, and the client's access rights to zero trust are not retained, thereby preventing clients with security risks from accessing zero trust and ensuring the security of zero trust.
[0121] It should be noted that the preset weighted average score can be 80 points, 85 points, etc., and can be set according to actual applications, and is not limited in this embodiment of the present application.
[0122] S109: Retain the client's zero-trust access rights and update the identity authentication information.
[0123] In the process of specifically executing step S109, when it is determined that the client's authentication score is greater than or equal to the preset weighted average score, it can be determined that the client's authentication has passed this time, and the client's access rights to zero trust can be retained, that is, the client is allowed to continue to access zero trust, and at the same time, the client's authentication information is updated so that the client can continue to send the updated authentication information to the zero trust controller during the zero trust login period, thereby achieving continuous authentication of clients accessing zero trust and ensuring the security of zero trust during the access period.
[0124] As a preferred method provided by an embodiment of the present application, when the identity authentication information is not the first identity authentication information, the process of updating the identity authentication information can specifically be: randomly executing multiple authentication items from pre-set authentication items; using multiple randomly specified authentication items to update multiple target authentication items in the identity authentication information, and then sending the access timestamp and the updated identity authentication information to the client, so that the client sends the updated identity authentication information to the zero trust controller during the zero trust login period according to the access timestamp.
[0125] In some embodiments, when the identity authentication information currently sent by the client is not the first identity authentication information, if the identity authentication of the client is passed using the identity authentication information, in order to ensure that subsequent continuous authentication processes are protected from replay attacks and man-in-the-middle attacks, multiple authentication items can be randomly specified from the pre-set authentication items while retaining the Token and timestamp as the target authentication items for the client's next identity authentication, so that the multiple target authentication items in the identity authentication information can be updated using the randomly specified multiple authentication items.
[0126] Furthermore, in an embodiment of the present application, a time interval T_Intv for the client to send updated authentication information next time may also be specified, so that the client sends the updated authentication information to the zero trust controller when the time from the current authentication is equal to the time interval T_Intv.
[0127] It should be noted that this application implements a challenge response mechanism by randomly specifying the authentication information (and randomly specified multiple authentication items) and time interval T_Intv required for the client's next authentication, thereby protecting the client from replay attacks and man-in-the-middle attacks during the authentication process.
[0128] S110: Send the updated identity authentication information to the client, so that the client sends the updated identity authentication information to the zero trust controller during the zero trust login period.
[0129] In the process of specifically executing step S110, after the currently received authentication information is updated, the updated authentication information and time interval T_Intv can be sent to the client, so that when the time from the current authentication is equal to the time interval T_Intv, the client sends the updated authentication information to the zero trust controller, thereby achieving continuous authentication of clients accessing zero trust and ensuring the security of zero trust during the access period.
[0130] The present application provides an identity authentication method, which receives identity authentication information sent by a client during a zero-trust login; wherein the identity authentication information includes a timestamp, a token, and authentication information of multiple target authentication items; if the identity authentication information is the first identity authentication information, the identity authentication score of the client is determined according to the authentication information of each second authentication item; the second authentication item is any target authentication item other than the first authentication item and the third authentication item in each target authentication item; if the identity authentication score is greater than or equal to a preset weighted average score, the authentication information of the first authentication item in each target authentication item is verified; if the authentication information of the first authentication item in each target authentication item passes the verification, the client is granted access rights to access zero trust, and the identity authentication information is updated; if the identity authentication information is not the first identity authentication information, whether the client meets the identity authentication conditions according to the identity authentication information; if the client meets the identity authentication conditions, the identity authentication score of the client is determined according to the authentication information of each target authentication item; if the identity authentication score is greater than or equal to the preset weighted average score, the client's access rights to access zero trust are retained, and the identity authentication information is updated; the updated identity authentication information is sent to the client, so that the client sends the updated identity authentication information to the zero-trust controller according to the period of zero-trust login. It can be seen that the technical solution provided by the present application can receive the identity authentication information sent by the client during the period when the client accesses zero trust, authenticate the client using the received identity authentication information, and if the client's identity authentication passes, grant or retain the client's access to zero trust, and update the identity authentication information at the same time, so that the client sends the updated identity authentication information to the zero trust controller during the period of logging into zero trust, thereby realizing continuous identity authentication of clients accessing zero trust and ensuring the security of zero trust during the access period.
[0131] In order to better understand the identity authentication method provided in the embodiment of the present application, the following is explained by way of example. Figure 2 shown.
[0132] A1: The zero-trust controller receives the identity authentication information sent by the client, which includes timestamp, token, and authentication information of multiple target authentication items.
[0133] A2: The zero trust controller determines whether the identity authentication information is the identity authentication information sent by the client for the first time during the zero trust login period; if so, execute A3, if not, execute A9.
[0134] A3: The zero trust controller uses the authentication information of each second authentication item in each target authentication item to score each second authentication item, and uses the scores of each second authentication item to calculate the weighted average score to obtain the client's identity authentication score.
[0135] A4: The zero trust controller determines whether the client's authentication score is greater than or equal to the preset weighted average score; if it is, execute A5; if it is not, determine that the client's authentication has failed, and do not retain the client's access rights to zero trust.
[0136] A5: The zero trust controller verifies the username and password in the authentication information of the first authentication item in each target authentication item; if the verification passes, execute A6; if the verification fails, it is determined that the client's identity authentication has failed, and the client's access to zero trust is not retained.
[0137] A6: Zero Trust Control determines that the client's first identity authentication is successful, grants the client access rights, and generates a unique token and access timestamp for the client.
[0138] A7: The zero-trust controller randomly specifies multiple authentication items from the pre-set authentication items, and uses the exclusive token, access timestamp and randomly specified multiple authentication items to update the token, timestamp and target authentication items in the authentication information. At the same time, it can also randomly specify a time interval T_Intv as the time interval between the client's next authentication and this authentication.
[0139] A8: The zero trust controller sends the time interval T_Intv and the updated authentication information to the client.
[0140] A9: The zero trust controller determines whether the target authentication items in the currently received authentication information are consistent with the multiple authentication items randomly specified when the client's authentication was passed last time; if they are consistent, execute A10; if they are inconsistent, it is determined that the client's authentication has failed, and the client's access to zero trust is not retained.
[0141] A10: Zero trust control determines whether the timestamp T in the currently received authentication information satisfies the inequality T_Prev+T_Intv<=T<=T_Prev+1.2*T_Intv; if so, execute A11; if not, determine that the client's authentication has failed, and do not retain the client's zero trust access rights; where T_Prev is the timestamp used when the last authentication of the client was successful, T is the timestamp in the authentication information, and T_Intv is the time interval generated when the last authentication of the client was successful.
[0142] A11: Zero Trust Control determines whether the Token in the currently received authentication information is consistent with the exclusive Token generated when the Zero Trust Controller determines that the client's first authentication has passed; if they are consistent, execute A12; if they are inconsistent, it is determined that the client's authentication has failed, and the client's access to Zero Trust is not retained.
[0143] A12: The zero trust controller determines whether the authentication information of the third authentication item in each target authentication item is consistent with the authentication information of the third authentication item in the client's first identity authentication information; if they are consistent, execute A13; if they are inconsistent, determine that the client's identity authentication has failed, and do not retain the client's access rights to zero trust. Among them, each target authentication item includes the third authentication item.
[0144] A13: The zero trust controller uses the authentication information of each second authentication item in each target authentication item to score each second authentication item, and uses the scores of each second authentication item to calculate the weighted average score to obtain the client's identity authentication score.
[0145] A14: The zero trust controller determines whether the client's authentication score is greater than or equal to the preset weighted average score; if so, A15; if not, it is determined that the client's authentication has failed and the client's access to zero trust is not retained.
[0146] A15: Zero Trust Control ensures that the client's identity authentication is passed and the client's access rights are retained.
[0147] A16: The zero-trust controller randomly specifies multiple authentication items from the pre-set authentication items, and updates each target authentication item in the identity authentication information. It can also randomly specify a time interval T_Intv as the time interval between the client's next identity authentication and this identity authentication.
[0148] A17: The zero trust controller sends the time interval T_Intv and the updated authentication information to the client.
[0149] Based on the identity authentication method provided in the above embodiment of the present application, correspondingly, the embodiment of the present application also provides an identity authentication system, such as Figure 3 As shown, applied to a zero-trust controller, the identity authentication system includes:
[0150] The receiving unit 31 is used to receive the identity authentication information sent by the client during the zero-trust login; wherein the identity authentication information includes a timestamp, a token, and authentication information of multiple target authentication items;
[0151] The first identity authentication score determination unit 32 is used to determine the identity authentication score of the client according to the authentication information of each second authentication item if the identity authentication information is the first identity authentication information; the second authentication item is any target authentication item among the target authentication items except the first authentication item and the third authentication item;
[0152] A first verification unit 33, configured to verify the authentication information of the first authentication item in each target authentication item if the identity authentication score is greater than or equal to a preset weighted average score;
[0153] A granting unit 34 is used to grant the client access to zero-trust access rights and update the identity authentication information if the authentication information of the first authentication item in each target authentication item is verified to be passed;
[0154] The first judgment unit 35 is used to judge whether the client satisfies the identity authentication condition according to the identity authentication information if the identity authentication information is not the first identity authentication information;
[0155] A second identity authentication score determination unit 36, configured to determine the identity authentication score of the client according to the authentication information of each target authentication item if the client satisfies the identity authentication condition;
[0156] An updating unit 37, configured to retain the client's zero-trust access rights and update the identity authentication information if the identity authentication score is greater than or equal to a preset weighted average score;
[0157] The sending unit 38 is used to send the updated identity authentication information to the client, so that the client sends the updated identity authentication information to the zero trust controller during the zero trust login period.
[0158] The specific principles and execution processes of each unit in the identity authentication system disclosed in the above embodiment of the present application are the same as the identity authentication method disclosed in the above embodiment of the present application. Please refer to the corresponding parts of the identity authentication method disclosed in the above embodiment of the present application, and no further details will be given here.
[0159] The present application provides an identity authentication system, which receives identity authentication information sent by a client during a zero-trust login; wherein the identity authentication information includes a timestamp, a token, and authentication information of multiple target authentication items; if the identity authentication information is the first identity authentication information, the identity authentication score of the client is determined according to the authentication information of each second authentication item; the second authentication item is any target authentication item other than the first authentication item and the third authentication item in each target authentication item; if the identity authentication score is greater than or equal to a preset weighted average score, the authentication information of the first authentication item in each target authentication item is verified; if the authentication information of the first authentication item in each target authentication item passes the verification, the client is granted access rights to access zero trust, and the identity authentication information is updated; if the identity authentication information is not the first identity authentication information, whether the client meets the identity authentication conditions according to the identity authentication information; if the client meets the identity authentication conditions, the identity authentication score of the client is determined according to the authentication information of each target authentication item; if the identity authentication score is greater than or equal to the preset weighted average score, the client's access rights to access zero trust are retained, and the identity authentication information is updated; the updated identity authentication information is sent to the client, so that the client sends the updated identity authentication information to the zero-trust controller according to the period of zero-trust login. It can be seen that the technical solution provided by the present application can receive the identity authentication information sent by the client during the period when the client accesses zero trust, authenticate the client using the received identity authentication information, and if the client's identity authentication passes, grant or retain the client's access to zero trust, and update the identity authentication information at the same time, so that the client sends the updated identity authentication information to the zero trust controller during the period of logging into zero trust, thereby realizing continuous identity authentication of clients accessing zero trust and ensuring the security of zero trust during the access period.
[0160] Optionally, the second identity authentication score determination unit includes:
[0161] A second judgment unit is used to judge whether there is a third authentication item in each target authentication item if the client satisfies the identity authentication condition;
[0162] A first scoring unit, configured to score each target authentication item according to the authentication information of each target authentication item if the third authentication item does not exist in each target authentication item;
[0163] The first calculation unit is used to perform weighted average calculation on the scores of each target authentication item to obtain the identity authentication score of the client.
[0164] Optionally, the identity authentication system provided by this application further includes:
[0165] a third determination unit, configured to determine whether the authentication information of the third authentication item in each target authentication item is the same as the authentication information of the third authentication item in the first identity authentication information if the third authentication item exists in each target authentication item;
[0166] The execution unit is used to determine the identity authentication score of the client according to the authentication information of each second authentication item if the authentication information of the third authentication item in each target authentication item is the same as the authentication information of the third authentication item in the first identity authentication information.
[0167] Optionally, the first identity authentication score determination unit includes:
[0168] A second scoring unit, configured to score each second authentication item according to the authentication information of each second authentication item;
[0169] The second calculation unit is used to perform an average weighted calculation on the scores of each second authentication item to obtain the identity authentication score of the client.
[0170] Optionally, when the identity authentication information is the first identity authentication information, the updating unit includes:
[0171] A first random assignment unit is used to generate a unique Token and access timestamp of the client, and randomly assign multiple authentication items from various pre-set authentication items;
[0172] The first updating subunit is used to update multiple target authentication items in the identity authentication information using multiple randomly specified authentication items, and to update the Token and the timestamp in the identity authentication information using the exclusive Token and the access timestamp.
[0173] Optionally, when the identity authentication information is not the first identity authentication information, the updating unit includes:
[0174] A second random designation unit, used for randomly designating a plurality of authentication items from various pre-set authentication items;
[0175] The second updating subunit is used to update multiple target authentication items in the identity authentication information using multiple randomly specified authentication items.
[0176] Optionally, the first judging unit includes:
[0177] An acquiring unit, configured to acquire, if the identity authentication information is not the first identity authentication information, a plurality of authentication items randomly specified when the identity authentication of the client was passed last time;
[0178] The second verification unit is used to verify the timestamp and the Token if the multiple authentication items randomly specified when the last identity authentication of the client is passed are the same as the target authentication items in the identity authentication information;
[0179] A first determination unit, used to determine that the client meets the identity authentication condition if the timestamp and the token verification pass;
[0180] The second determination unit is used to determine that the client does not meet the identity authentication conditions if any target authentication item is different from at least one authentication item randomly specified when the client's identity authentication was passed last time, and / or the timestamp verification fails, and / or the Token verification fails.
[0181] The present application embodiment provides an electronic device, such as Figure 4 As shown, the electronic device includes a processor 401 and a memory 402, the memory 402 is used to store program codes and data for identity authentication, and the processor 401 is used to call program instructions in the memory to execute the steps shown in the identity authentication method in the above embodiment.
[0182] An embodiment of the present application provides a storage medium, which includes a storage program, wherein when the program is running, the device where the storage medium is located is controlled to execute the physical location management method of the device shown in the above embodiment.
[0183] For the aforementioned method embodiments, for the sake of simplicity, they are all described as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the order of the actions described, because according to the present application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.
[0184] It should be noted that each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other. For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.
[0185] The steps in the methods of the embodiments of the present application can be adjusted in order, combined, and deleted according to actual needs.
[0186] The modules and sub-modules in the devices and terminals in the embodiments of the present application can be combined, divided and deleted according to actual needs.
[0187] In the several embodiments provided in the present application, it should be understood that the disclosed terminals, devices and methods can be implemented in other ways. For example, the terminal embodiments described above are only schematic, for example, the division of modules or submodules is only a logical function division, and there may be other division methods in actual implementation, for example, multiple submodules or modules can be combined or integrated into another module, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or modules, which can be electrical, mechanical or other forms.
[0188] The modules or submodules described as separate components may or may not be physically separated, and the components of the modules or submodules may or may not be physical modules or submodules, that is, they may be located in one place, or they may be distributed on multiple network modules or submodules. Some or all of the modules or submodules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0189] In addition, each functional module or submodule in each embodiment of the present application may be integrated into one processing module, or each module or submodule may exist physically separately, or two or more modules or submodules may be integrated into one module. The above-mentioned integrated modules or submodules may be implemented in the form of hardware or in the form of software functional modules or submodules.
[0190] Finally, it should be noted that, in this application, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0191] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined in the present application may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown in the present application, but will conform to the widest scope consistent with the principles and novel features disclosed in the present application.
[0192] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.
Claims
1. An identity authentication method, characterized in that: Applied to a zero trust controller, the method includes: Receive identity authentication information sent by the client during zero-trust login; wherein the identity authentication information includes a timestamp, a token, and authentication information of multiple target authentication items; If the identity authentication information is the first identity authentication information, determine the identity authentication score of the client according to the authentication information of each second authentication item; the second authentication item is any one of the target authentication items except the first authentication item and the third authentication item; If the identity authentication score is greater than or equal to a preset weighted average score, verifying the authentication information of the first authentication item in each of the target authentication items; If the authentication information of the first authentication item in each target authentication item is verified, granting the client access to the zero-trust access right and updating the identity authentication information; If the identity authentication information is not the first identity authentication information, judging whether the client satisfies the identity authentication condition according to the identity authentication information; If the client satisfies the identity authentication condition, determining the identity authentication score of the client according to the authentication information of each of the target authentication items; If the identity authentication score is greater than or equal to the preset weighted average score, retain the client's access rights to the zero trust and update the identity authentication information; The updated identity authentication information is sent to the client, so that the client sends the updated identity authentication information to the zero trust controller during the zero trust login period.
2. The method according to claim 1, characterized in that If the client satisfies the identity authentication condition, determining the identity authentication score of the client according to the authentication information of each of the target authentication items includes: If the client satisfies the identity authentication condition, determining whether there is a third authentication item in each of the target authentication items; If the third authentication item does not exist in each of the target authentication items, scoring each of the target authentication items according to the authentication information of each of the target authentication items; The scores of the target authentication items are weighted averagely calculated to obtain the identity authentication score of the client.
3. The method according to claim 2, characterized in that The method further comprises: If the third authentication item exists in each of the target authentication items, determining whether the authentication information of the third authentication item in each of the target authentication items is the same as the authentication information of the third authentication item in the first identity authentication information; If the authentication information of the third authentication item in each of the target authentication items is the same as the authentication information of the third authentication item in the first identity authentication information, the identity authentication score of the client is determined according to the authentication information of each of the second authentication items.
4. The method according to claim 1 or 3, characterized in that: Determining the identity authentication score of the client according to the authentication information of each second authentication item includes: Score each second authentication item according to the authentication information of each second authentication item; An average weighted calculation is performed on the scores of each of the second authentication items to obtain the identity authentication score of the client.
5. The method according to claim 1, characterized in that In the case where the identity authentication information is the first identity authentication information, updating the identity authentication information includes: Generate a unique Token and access timestamp for the client, and randomly specify multiple authentication items from pre-set authentication items; The multiple target authentication items in the identity authentication information are updated using the multiple randomly specified authentication items, and the Token and the timestamp in the identity authentication information are updated using the exclusive Token and the access timestamp.
6. The method according to claim 1, characterized in that When the identity authentication information is not the first identity authentication information, updating the identity authentication information includes: Randomly specify multiple authentication items from pre-set authentication items; The plurality of target authentication items in the identity authentication information are updated using the plurality of randomly specified authentication items.
7. The method according to claim 1, characterized in that If the identity authentication information is not the first identity authentication information, judging whether the client satisfies the identity authentication condition according to the identity authentication information includes: If the identity authentication information is not the first identity authentication information, obtaining a plurality of authentication items randomly specified when the identity authentication of the client was passed last time; If the multiple authentication items randomly specified when the last identity authentication of the client was passed are the same as the target authentication items in the identity authentication information, verify the timestamp and the Token; If the timestamp and the token are verified, it is determined that the client meets the identity authentication condition; If any of the target authentication items is different from at least one authentication item randomly specified when the identity authentication of the client was passed last time, and / or the timestamp verification fails, and / or the Token verification fails, it is determined that the client does not meet the identity authentication conditions.
8. An identity authentication system, characterized in that: Applied to a zero-trust controller, the system includes: A receiving unit, configured to receive identity authentication information sent by a client during zero-trust login; wherein the identity authentication information includes a timestamp, a token, and authentication information of multiple target authentication items; A first identity authentication score determination unit is used to determine the identity authentication score of the client according to the authentication information of each second authentication item if the identity authentication information is the first identity authentication information; the second authentication item is any target authentication item among the target authentication items except the first authentication item and the third authentication item; A first verification unit, configured to verify the authentication information of the first authentication item in each of the target authentication items if the identity authentication score is greater than or equal to a preset weighted average score; a granting unit, configured to grant the client access to the zero-trust access right and update the identity authentication information if the authentication information of the first authentication item in each target authentication item is verified to be passed; A first judgment unit, configured to judge whether the client satisfies an identity authentication condition according to the identity authentication information if the identity authentication information is not the first identity authentication information; A second identity authentication score determination unit, configured to determine the identity authentication score of the client according to the authentication information of each of the target authentication items if the client satisfies the identity authentication condition; An updating unit, configured to retain the client's access rights to the zero-trust access and update the identity authentication information if the identity authentication score is greater than or equal to a preset weighted average score; A sending unit is used to send the updated identity authentication information to the client, so that the client sends the updated identity authentication information to the zero trust controller during the zero trust login period.
9. An electronic device, characterized in that: include: A processor and a memory, wherein the processor and the memory are connected via a communication bus; wherein the processor is used to call and execute a program stored in the memory; The memory is used to store a program, and the program is used to implement the identity authentication method as described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to execute the identity authentication method as described in any one of claims 1-7.
Citation Information
Patent Citations
Security authentication and authority control method and device under micro-application architecture and storage medium
CN116192432A
Zero-trust dynamic access control method based on flow identification
CN116582374A
Login authentication method, zero-trust controller and electronic equipment
CN116962088A
Multi-factor identity authentication method, device and system for mail system
CN118264422A
Identity-based authentication and access control mechanism
US11552953B1
