Policy-based multi-factor login method and system

Through a policy-based multi-factor login method, combining multiple verification factors and policies, login verification is dynamically adjusted, which solves the problem of easy-to-break traditional single password login, improves network security and user experience, and supports customized solutions.

CN119094230APending Publication Date: 2024-12-06INSPUR TIANYUAN COMM INFORMATION SYST CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202411329597.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-24
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The traditional single password login method is easy to be cracked, the risk of misappropriation is high, and it is difficult to meet the needs of modern network security.

Method used

Adopt a policy-based multi-factor login method, dynamically adjust the login verification process by defining and configuring multiple verification factors and policies, combining user equipment and behavior information, and adopting equality, inclusion, exclusion, scope and other verification methods to improve security and users Experience.

Benefits of technology

It effectively improves the security and verification flexibility of the system, supports customized solutions, and enhances the security and experience of user identity authentication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094230A_ABST
    Figure CN119094230A_ABST
Patent Text Reader

Abstract

The invention discloses a strategy-based multi-factor login method and system, and belongs to the technical field of computer software, and the method comprises the steps: 1, defining login verification factors, including parameter names, description and verification modes of the factors; 2, defining a verification strategy and the level of the verification strategy; and step 3, during login, verifying the strategy configured in the step 2 by adopting the strategy meeting the condition in combination with the actual login condition. According to the invention, the security, verification flexibility and user experience of the system can be effectively improved, and a customized scheme can be supported more conveniently.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer software technology, in particular to a policy-based multi-factor login method and system. Background Art

[0002] With the rapid development of the Internet, network security issues are becoming increasingly prominent. The traditional single password login method can no longer meet the needs of modern network security. Problems such as the easiness of password cracking, the risk of theft, and the negligence of users in password management have made network security face huge challenges. Summary of the invention

[0003] The technical task of the present invention is to address the above deficiencies and provide a policy-based multi-factor login method and system that can effectively improve the system's security, verification flexibility, user experience, and more conveniently support customized solutions.

[0004] The technical solution adopted by the present invention to solve its technical problem is:

[0005] A policy-based multi-factor login method, the implementation of which includes:

[0006] Step 1: Define the factors for login verification, including the parameter name, description, and verification method of the factors;

[0007] Step 2: Define the verification strategy and the level of verification strategy;

[0008] Step 3: When logging in, the policy configured in step 2 is combined with the actual login situation and the policy that meets the conditions is used for verification.

[0009] Furthermore, the definition of login verification factors includes multiple aspects of user information that can be verified, such as username, password, image verification code, SMS verification code, IP address, MAC address, mobile phone number, and device number; these factors are used to determine whether the legitimate user is logging into the system;

[0010] The verification methods include equality, inclusion, exclusion, and range.

[0011] Furthermore, the login verification factor information is saved in a database or a json file; in subsequent verification steps, only the factors defined in step 1 can be used.

[0012] Furthermore, the verification strategy has a number of strategies greater than or equal to one; each strategy includes a combination of one or more verification factors, a condition for enabling the strategy, and whether the strategy is available;

[0013] The verification factor is the factor described in step 1; the conditions for enabling the policy are checked in the supported policy pool, such as the login IP address changes, login MAC address changes, etc.;

[0014] A verification strategy can include one or more verification factors. Using multiple verification factors can improve the security of verification. At the same time, using multiple strategies can improve the user experience. The levels of the verification strategies are sorted from low to high. Low-level strategies require fewer verification factors and are more convenient. For example, only using user names and mobile phone verification codes; high-level strategies require more verification factors or are more complex. For example, using mobile phone numbers, image verification codes, mobile phone verification codes, and IP address ranges for simultaneous verification.

[0015] Furthermore, the definition of the verification strategy and the level of the verification strategy includes:

[0016] P1 level: login account + SMS verification code verification, priority 0; condition: the login device number is the same as the previously used device number;

[0017] P2 level: Login account + password + SMS verification code verification, priority 1; condition: the login device number is different from the previously used device number, or the previous level verification fails;

[0018] P3 level: login account + password + picture verification code + SMS verification code verification, priority 2; condition: the previous level verification failed.

[0019] Furthermore, when logging in, first determine whether the lowest level policy meets the conditions, that is, determine whether the device number of the login is the same as the previously commonly used device. If it is the same, directly use policy P1, that is, only use the login account + SMS verification code method to verify. If this login is successful, the verification process ends here; if the login fails, such as the SMS verification code is entered incorrectly, an upgraded verification will be performed, that is, enable policy P2, that is, use the login account + password + SMS verification code verification. If this login is successful, the verification process ends; if the login fails, enable policy P3, login account + password + picture verification code + SMS verification code verification;

[0020] The actual login situations include:

[0021] 1) When logging in, the device number (such as computer, mobile phone) is the same as the common device number. At this time, only P1 policy verification is required, that is, login account + SMS verification code; enter the correct account number and SMS verification code, and the login is successful;

[0022] 2) When logging in, if the device number (such as computer, mobile phone) is the same as the common device number, only P1 strategy verification is required, that is, login account + SMS verification code; if the SMS verification code is entered incorrectly, the verification level will be increased to P2, that is, login account + password + SMS verification code is required for verification; at this time, enter the correct login account, password, and SMS verification code, and the login is successful;

[0023] 3) When logging in, the device number (such as computer, mobile phone) is the same as the common device number. At this time, only P1 strategy verification is required, that is, login account + SMS verification code; if the SMS verification code is entered incorrectly, the verification level will be increased to P2, that is, login account + password + SMS verification code must be used for verification; at this time, the password or SMS verification code is entered incorrectly, resulting in the verification level being increased to P3, that is, login account + password + picture verification code + SMS verification code must be used for verification; enter the correct account, password, picture verification code and SMS verification code, and the login is successful;

[0024] 4) When logging in, the device number (such as computer, mobile phone) is the same as the commonly used device number. At this time, only P1 strategy verification is required, that is, login account + SMS verification code; the SMS verification code is entered incorrectly, resulting in the verification level being raised to P2, that is, the login account + password + SMS verification code is required for verification; at this time, the password or SMS verification code is entered incorrectly, resulting in the verification level being raised to P3, that is, the login account + password + picture verification code + SMS verification code is required for verification; in this verification, there is still a factor of input error. Combined with other login verification strategies, if the number of login failures exceeds N times, the account will be locked and no login will be allowed again within the specified time (such as 5 minutes).

[0025] Furthermore, when verifying on the server side, the verification method is implemented according to different factors, and the isValid() method is used. Returning true indicates that the verification is successful, and false indicates that the verification fails.

[0026] When implementing verification, the verification of various factors in the strategy is implemented according to the strategy. Once the isValid() method returns false during the verification process, the verification is stopped and the login verification fails. Only when the isValid() method of all verification factors in the strategy returns true, it means that the verification is passed.

[0027] The present invention also claims a policy-based multi-factor login system, comprising:

[0028] Verification factor definition module, used to define the parameter name, description, and verification method of the factor;

[0029] A verification strategy definition module is used to define verification strategies and levels of verification strategies;

[0030] The login module is used to perform authentication based on the policies configured in the authentication policy definition module and the actual login situation when logging in.

[0031] The system specifically implements user login verification through the above-mentioned policy-based multi-factor login method.

[0032] The present invention also claims a policy-based multi-factor login device, comprising: at least one memory and at least one processor;

[0033] The at least one memory is used to store a machine-readable program;

[0034] The at least one processor is used to call the machine-readable program to implement the above method.

[0035] The present invention also claims protection for a computer-readable medium having computer instructions stored thereon, which implement the above method when executed by a processor.

[0036] Compared with the prior art, the policy-based multi-factor login method and system of the present invention has the following beneficial effects:

[0037] This method describes an effective and configurable multi-strategy login method, which can dynamically adjust the login verification factors according to the policy at login time, including the definition of policy rules, the adaptation of the verification method at login time, and the verification process of each factor. After configuring the multi-factor and verification policy according to this method, combined with the verification process, it can effectively improve the system's security, verification flexibility, user experience, and more conveniently support customized solutions. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 This is a flow chart for implementing a policy-based multi-factor login method provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0039] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments.

[0040] A policy-based multi-factor login method, the implementation of which includes:

[0041] Step 1: Define the factors for login verification, including the parameter name, description, and verification method (equal, inclusive, exclusive, range, etc.); verification factors include multiple aspects that can verify user information, such as user name, password, image verification code, SMS verification code, IP address, MAC address, mobile phone number, and device number; use these factors to determine whether the legitimate user is logging into the system.

[0042] Step 2: Define the verification policy and the level of the verification policy. The number of policies is greater than or equal to one; each policy contains a combination of one or more verification factors, the conditions for enabling the policy, and whether the policy is available; the verification factors are the factors described in step 1; the conditions for enabling the policy are checked in the supported policy pool, such as changes in the login IP address, changes in the login MAC address, etc. A verification policy can contain one or more verification factors. Using multiple verification factors can improve the security of verification; at the same time, using multiple policies can improve the user experience.

[0043] The levels of the verification strategies are sorted from low to high. Low-level strategies require fewer verification factors and are more convenient. For example, only using username and mobile phone verification code; high-level strategies require more verification factors or are more complex. For example, using mobile phone number, image verification code, mobile phone verification code, and IP address range for simultaneous verification.

[0044] Step 3: When logging in, the policy configured in step 2 is combined with the actual login situation and the policy that meets the conditions is used for verification.

[0045] The specific implementation of this method is as follows:

[0046] The first step is to define the factors for login verification, which are used to confirm whether the authenticated user is logging in. These factors include but are not limited to the following:

[0047]

[0048] accountName is the login account, which is used to confirm the uniqueness of the account and is case sensitive.

[0049] Password is the password field. For security reasons, it cannot be transmitted in plain text during the login verification process. You can use the RSA public key for transmission encryption.

[0050] textCode is a picture verification code, which is manually identified by numbers and letters on the picture.

[0051] smsCode is the SMS verification code, which will be sent to the mobile phone corresponding to accountName (provided that the user has saved the mobile phone information) or directly to the mobile.

[0052] ipAddress is the IP address of the currently logged in client, which can be an allowed range, such as an intranet IP segment.

[0053] macAddress is the MAC address of the machine.

[0054] mobile is the mobile phone number of the logged-in user.

[0055] deviceSeq is the device ID of the logged-in user.

[0056] …

[0057] The above login verification factor information can be saved in a database or a json file. In the subsequent verification steps, only the factors defined in this step can be used.

[0058] The second step is to define the verification strategy and level in detail according to actual needs. A verification strategy can contain one or more verification factors. For example, according to the verification factors formulated in step 1, the following verification strategies can be configured:

[0059] P1 level: Login account + SMS verification code verification, priority 0. Condition: The login device number is the same as the previously used device number.

[0060] P2 level: Login account + password + SMS verification code verification, priority 1. Condition: The login device number is different from the previously used device number, or the previous level verification fails.

[0061] P3 level: Login account + password + picture verification code + SMS verification code verification, priority 2. Condition: The previous level verification failed.

[0062] The third step is to log in and match different strategies for login verification according to the actual situation.

[0063] When logging in, first determine whether the lowest level policy meets the conditions, that is, determine whether the device number of the login is the same as the previously commonly used device. If it is the same, directly use policy P1, that is, only use the login account + SMS verification code method to verify. If this login is successful, the verification process ends here; if the login fails, such as the SMS verification code is entered incorrectly, an upgraded verification will be performed, that is, policy P2 will be enabled, that is, the login account + password + SMS verification code verification will be used. If this login is successful, the verification process ends; if the login fails, enable policy P3, login account + password + picture verification code + SMS verification code verification.

[0064] According to the three levels configured in step 2, the actual login may be as follows:

[0065] 1. When logging in, the device number (such as computer, mobile phone) is the same as the commonly used device number. At this time, only P1 policy verification is required, that is, login account + SMS verification code; enter the correct account and SMS verification code, and the login is successful.

[0066] 2. When logging in, if the device number (such as computer, mobile phone) is the same as the common device number, only P1 strategy verification is required, that is, login account + SMS verification code. If the SMS verification code is entered incorrectly, the verification level will be increased to P2, that is, login account + password + SMS verification code is required for verification; at this time, enter the correct login account, password, and SMS verification code, and the login is successful.

[0067] 3. When logging in, if the device number (such as computer, mobile phone) is the same as the common device number, only P1 strategy verification is required, that is, login account + SMS verification code. If the SMS verification code is entered incorrectly, the verification level will be increased to P2, that is, login account + password + SMS verification code will be used for verification; at this time, the password or SMS verification code is entered incorrectly, resulting in the verification level being increased to P3, that is, login account + password + picture verification code + SMS verification code will be used for verification; enter the correct account, password, picture verification code and SMS verification code, and the login is successful.

[0068] 4. When logging in, the device number (such as computer, mobile phone) is the same as the commonly used device number. At this time, only P1 strategy verification is required, that is, login account + SMS verification code; the SMS verification code is entered incorrectly, resulting in the verification level being raised to P2, that is, the login account + password + SMS verification code is required for verification. At this time, the password or SMS verification code is entered incorrectly, resulting in the verification level being raised to P3, that is, the login account + password + picture verification code + SMS verification code is required for verification. In this verification, there is still a factor of incorrect input. Combined with other login verification strategies, if the number of login failures exceeds N times, the account will be locked and cannot be logged in again within the specified time (such as 5 minutes).

[0069] When verifying on the server side, the verification method is implemented according to different factors, and the isValid() method is used. Returning true indicates that the verification is successful, and false indicates that the verification fails. When implementing verification, the verification of various factors in the strategy is implemented according to the strategy. Once the isValid() method returns false during the verification process, the verification is stopped and the login verification fails. Only when the isValid() method of all verification factors in the strategy returns true, it means that the verification is successful.

[0070] Multi-Factor Authentication (MFA) is an identity verification method that requires users to provide two or more verification information to prove their identity. This information can include what the user knows (such as passwords, PIN codes, etc.), what the user has (such as mobile phones, security tokens, etc.), and what the user has (such as biometrics, such as fingerprints, facial recognition, etc.). This multi-level verification mechanism greatly improves the security of user authentication. The benefits of multi-factor authentication login are as follows:

[0071] Enhanced security: Multi-factor authentication significantly improves the security of user authentication by combining multiple verification methods. Even if an attacker obtains the user's password, they still need to meet other authentication conditions to log in, which greatly reduces the risk of illegal access to the account.

[0072] Flexibility: Multi-factor authentication supports a variety of authentication methods, such as SMS authentication, QR code authentication, mobile tokens, biometric authentication, etc. This flexibility enables multi-factor authentication to adapt to different enterprise scenarios and user needs, providing a precisely adapted authentication method.

[0073] User experience: Although multi-factor authentication adds authentication steps, through reasonable configuration and strategy, it is possible to ensure security while taking into account the user experience. For example, adaptive multi-factor authentication can choose to apply different authentication methods based on the current security situation, which not only ensures security but also improves the user experience.

[0074] Customizability: Multi-factor authentication systems usually provide a wealth of configuration options and policy settings, allowing enterprises to customize authentication processes and trigger conditions according to their own needs and achieve more refined security management.

[0075] The multi-factor authentication login method significantly improves network security and user experience by providing a multi-level authentication mechanism and flexible authentication methods. After configuring the multi-factor and authentication strategy, this method can effectively improve the system's security, authentication flexibility, user experience, and more conveniently support customized solutions by combining the authentication process.

[0076] The embodiment of the present invention also provides a policy-based multi-factor login system, including:

[0077] The verification factor definition module is used to define the parameter name, description, and verification method (equal, inclusive, exclusive, range, etc.) of the factor; the verification factor includes multiple aspects that can verify user information, such as user name, password, image verification code, SMS verification code, IP address, MAC address, mobile phone number, and device number; these factors are used to determine whether the legitimate user is logging into the system.

[0078] The verification policy definition module is used to define verification policies and the levels of verification policies. Among them, the number of policies is greater than or equal to one; each policy contains a combination of one or more verification factors, the conditions for opening the policy, and whether the policy is available; the verification factors are the factors described in step 1; the conditions for opening the policy are checked in the supported policy pool, such as the change of the login IP address, the change of the login MAC address, etc. A verification policy can contain one or more verification factors. Using multiple verification factors can improve the security of verification; at the same time, using multiple policies can improve the user experience. The levels of the verification policies are sorted from low to high. Low-level policies require fewer verification factors and are more convenient. For example, only the user name and mobile phone verification code are used; high-level policies require more verification factors or are more complex. For example, use mobile phone number, picture verification code, mobile phone verification code, and IP address range for simultaneous verification.

[0079] The login module is used to perform authentication based on the policies configured in the authentication policy definition module and the actual login situation when logging in.

[0080] The system specifically implements user login verification through the policy-based multi-factor login method described in the above embodiment.

[0081] An embodiment of the present invention also provides a policy-based multi-factor login device, comprising: at least one memory and at least one processor;

[0082] The at least one memory is used to store a machine-readable program;

[0083] The at least one processor is used to call the machine-readable program to implement the policy-based multi-factor login method described in the above embodiment.

[0084] The embodiment of the present invention also provides a computer-readable medium, on which computer instructions are stored, and when the computer instructions are executed by a processor, the policy-based multi-factor login method described in the above embodiment is implemented. Specifically, a system or device equipped with a storage medium can be provided, on which a software program code that implements the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or device reads and executes the program code stored in the storage medium.

[0085] In this case, the program code itself read from the storage medium can realize the function of any one of the above-mentioned embodiments, and thus the program code and the storage medium storing the program code constitute a part of the present invention.

[0086] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer by a communication network.

[0087] In addition, it should be clear that the functions of any of the above embodiments can be implemented not only by executing the program code read by the computer, but also by enabling an operating system operating on the computer to complete part or all of the actual operations based on instructions from the program code.

[0088] In addition, it can be understood that the program code read from the storage medium is written to a memory provided in an expansion board inserted into the computer or written to a memory provided in an expansion unit connected to the computer, and then based on the instructions of the program code, a CPU installed on the expansion board or the expansion unit is enabled to perform part or all of the actual operations, thereby realizing the functions of any of the above-mentioned embodiments.

[0089] The present invention is shown and described in detail above through the accompanying drawings and preferred embodiments. However, the present invention is not limited to these disclosed embodiments. Based on the above multiple embodiments, those skilled in the art can know that the code review methods in the above different embodiments can be combined to obtain more embodiments of the present invention, and these embodiments are also within the protection scope of the present invention.

Claims

1. A policy-based multi-factor login method, characterized in that: The implementation of this method includes: Step 1: Define the factors for login verification, including the parameter name, description, and verification method of the factors; Step 2: Define the verification strategy and the level of verification strategy; Step 3: When logging in, the policy configured in step 2 is combined with the actual login situation and the policy that meets the conditions is used for verification.

2. A policy-based multi-factor login method according to claim 1, characterized in that: The definition of login verification factors includes username, password, picture verification code, SMS verification code, IP address, MAC address, mobile phone number, and device number; these factors are used to determine whether the legitimate user is logging into the system; The verification methods include equality, inclusion, exclusion, and range.

3. A policy-based multi-factor login method according to claim 1 or 2, characterized in that: The login verification factor information is saved in the database or json file; in the subsequent verification steps, only the factors defined in step 1 can be used.

4. A policy-based multi-factor login method according to claim 1, characterized in that: The verification strategy, the number of strategies is greater than or equal to one; each strategy includes a combination of one or more verification factors, a condition for enabling the strategy, and whether the strategy is available; The verification factor is the factor described in step 1; the conditions for enabling the strategy are checked in the supported strategy pool; The levels of the verification strategies are arranged from low to high. A low-level strategy requires fewer verification factors, while a high-level strategy requires more verification factors.

5. A policy-based multi-factor login method according to claim 1, characterized in that: The definition of the verification strategy and the level of the verification strategy includes: P1 level: login account + SMS verification code verification, priority 0; condition: the login device number is the same as the previously used device number; P2 level: login account + password + SMS verification code verification, priority 1; condition: the login device number is different from the previously used device number, or the previous level verification fails; P3 level: login account + password + picture verification code + SMS verification code verification, priority 2; condition: the previous level verification failed.

6. A policy-based multi-factor login method according to claim 5, characterized in that: When logging in, first determine whether the lowest level policy meets the conditions, that is, determine whether the device number of the login is the same as the previously used device. If it is the same, directly use policy P1, that is, only use the login account + SMS verification code method for verification. If the current login is successful, the verification process ends here; If the login fails, an upgrade verification will be performed, that is, strategy P2 will be enabled, that is, the login account + password + SMS verification code will be used for verification. If the login is successful, the verification process ends; If the login fails, enable policy P3, login account + password + picture verification code + SMS verification code verification; The actual login situations include: 1) When logging in, the device number is the same as the common device number. At this time, only P1 policy verification is required, that is, login account + SMS verification code; enter the correct account number and SMS verification code, and the login is successful; 2) When logging in, the device number is the same as the common device number. At this time, only P1 strategy verification is required, that is, login account + SMS verification code; if the SMS verification code is entered incorrectly, the verification level will be increased to P2, that is, login account + password + SMS verification code is required for verification; at this time, enter the correct login account, password, and SMS verification code, and the login is successful; 3) When logging in, the device number is the same as the commonly used device number. At this time, only P1 strategy verification is required, that is, login account + SMS verification code; if the SMS verification code is entered incorrectly, the verification level will be increased to P2, that is, login account + password + SMS verification code will be required for verification; at this time, the password or SMS verification code is entered incorrectly, resulting in the verification level being increased to P3, that is, login account + password + picture verification code + SMS verification code will be required for verification; enter the correct account, password, picture verification code and SMS verification code, and the login is successful; 4) When logging in, the device number is the same as the commonly used device number. At this time, only P1 strategy verification is required, that is, login account + SMS verification code; the SMS verification code is entered incorrectly, resulting in the verification level being raised to P2, that is, the login account + password + SMS verification code is required for verification; at this time, the password or SMS verification code is entered incorrectly, resulting in the verification level being raised to P3, that is, the login account + password + picture verification code + SMS verification code is required for verification; in this verification, there is still a factor of input error. Combined with other login verification strategies, if the number of login failures exceeds N times, the account will be locked and no login will be allowed again within the specified time.

7. A policy-based multi-factor login method according to claim 1, characterized in that: When verifying on the server side, the verification method is implemented according to different factors, using the isValid() method. Returning true indicates that the verification is successful, and false indicates that the verification fails. When implementing verification, the verification of various factors in the strategy is implemented according to the strategy. Once the isValid() method returns false during the verification process, the verification is stopped and the login verification fails. Only when the isValid() method of all verification factors in the strategy returns true, it means that the verification is passed.

8. A policy-based multi-factor login system, characterized in that: include: Verification factor definition module, used to define the parameter name, description, and verification method of the factor; A verification strategy definition module is used to define verification strategies and levels of verification strategies; The login module is used to perform authentication based on the policies configured in the authentication policy definition module and the actual login situation when logging in. The system specifically implements user login verification through the policy-based multi-factor login method described in any one of claims 1 to 7.

9. A policy-based multi-factor login device, characterized in that: include: at least one memory and at least one processor; The at least one memory is used to store a machine-readable program; The at least one processor is used to call the machine-readable program to implement the method described in any one of claims 1 to 7.

10. A computer-readable medium, characterized in that The computer readable medium stores computer instructions, and when the computer instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Citation Information

Patent Citations

  • User login validation method, device and system

    CN104580075A

  • Method and device for generating verification code

    CN105610806A

  • Verification method and device

    CN107665301A

  • Method of mail service to actively discover abnormality

    CN108833258A

  • Login verification methods and devices, computer equipment and memory medium

    CN109547458A