Account authentication method and system based on risk rule model
Through the account authentication method based on the risk rule model, combined with multiple detection mechanisms to determine the account risk level, the problem that traditional single-point authentication cannot meet the security needs of complex business scenarios is solved, and multi-dimensional authentication and secure access control are realized.
Patent Information
- Application Number
- CN202411413582.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-11
- Publication Date
- 2024-11-08
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Traditional single-point authentication cannot meet the security needs of highly sensitive information systems in complex business scenarios, and cannot comprehensively analyze environmental factors, time factors and historical behaviors for dynamic secondary authentication and confirmation.
Account authentication method based on risk rule model, by obtaining historical behavior data of the account to be authenticated, using the preset risk rule model to judge the account risk level, and performing different authentication actions based on the level, including sudden active detection, brute force cracking detection, and slowness. Attack detection, location detection, device feature detection, library attack detection, multi-account login detection and operating system feature detection.
A multi-dimensional three-dimensional authentication system is realized, authentication security and access control are enhanced, and the risk rule model configuration adjustment is convenient to ensure access security.
Smart Images

Figure CN118916860A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of account authentication, and more specifically, to an account authentication method and system based on a risk rule model. Background Art
[0002] With the digitization process, the business scenarios are becoming more complex, and the traditional single-point authentication can no longer meet the usage requirements, such as business systems that require highly sensitive information to be accessed only within a certain time period. The demand has changed from single-point authentication to a multi-dimensional authentication system that combines time, location, and even behavior. The authentication service needs to be able to make risk assessments based on comprehensive analysis of environmental factors, time factors, historical behaviors, etc., and dynamically schedule secondary authentication requirements for identity confirmation to ensure access security. Summary of the invention
[0003] One of the purposes of the present invention is to provide an account authentication method based on a risk rule model to solve the problem that the existing single-point authentication cannot meet the business system needs and security requirements; the second purpose of the present invention is to provide an account authentication system based on a risk rule model.
[0004] In order to solve the above technical problems, the technical solution of the present invention is as follows: A first aspect of the present invention provides an account authentication method based on a risk rule model, comprising the following steps: When the account to be authenticated logs in, the historical account behavior data of the account to be authenticated is obtained; Based on a preset risk rule model, determine the account risk level according to the historical account behavior data; According to the account risk level, the account to be authenticated is authenticated using a preset risk control strategy.
[0005] In the above technical means, the historical account behavior data of the account is first obtained, and the account risk level of the account is obtained according to the preset risk rule model. Different authentication actions are performed according to the account risk level of the account, wherein the preset risk rule model can be set as judgment conditions in multiple dimensions to realize a multi-dimensional three-dimensional authentication system.
[0006] Furthermore, the historical account behavior data of the account to be authenticated is obtained, including: Obtain a login log of the account to be authenticated, and obtain historical account behavior data of the account to be authenticated from the login log.
[0007] Furthermore, the historical account behavior data includes access location, access time, access account, access device, operating system type, operating system version and access behavior.
[0008] Furthermore, the preset risk rule model includes: 1) Sudden activity detection: detect whether the last access time of the account and the current access time of the account exceed the specified number of days; 2) Brute force attack detection: Check whether the account has multiple authentication failure requests within a short period of time; 3) Slow attack detection: detect whether a certain access address sends authentication failure requests to multiple accounts within a preset time period; 4) Location detection: detect whether the account has logged in outside the set country and city; 5) Device feature detection: detect whether the device used to log in to the current account is not in the list of common devices of the current account; 6) Database attack detection: detect whether a certain access address has multiple authentication success and authentication failure requests within a certain period of time, and among the large number of authentication failure requests, the attempted account does not belong to the current enterprise; 7) Multiple account login detection: detect whether the same access address has logged in multiple accounts within a preset time period; 8) Usage time detection: detect whether the account has logged in outside the set time range; 9) Operating system feature detection: Check whether the operating system type and version used by the account in this request are inconsistent with the operating system type and version used in the past.
[0009] Furthermore, based on a preset risk rule model, the account risk level is determined according to the historical account behavior data, including: If at least one of the test results of tests 4), 5), 7), 8) and 9) in the risk rule model is yes, and the test results of the other tests are no, then the account risk level of the account to be authenticated is judged to be a low risk level; If at least one of the test results of tests 1) and 3) in the risk rule model is yes, and the test results of tests 2) and 6) are no, then the account risk level of the account to be authenticated is determined to be medium risk level; If at least one of the test results of tests 2) and 6) in the risk rule model is yes, then the account risk level of the account to be authenticated is determined to be a high risk level.
[0010] Further, according to the account risk level, the account to be authenticated is authenticated using a preset risk control strategy, including: When the account risk level of the account to be authenticated is a low risk level or a medium risk level, the account risk level of the account to be authenticated is recorded; When the account risk level of the account to be authenticated is a high risk level, the account risk level of the account to be authenticated is recorded, and a secondary authentication is performed on the account to be authenticated.
[0011] Furthermore, if the secondary authentication of the account to be authenticated fails, the authentication of the account to be authenticated fails.
[0012] Furthermore, in the detection 7) in the risk rule model, the account using the most access addresses is checked through the exception list in combination with the authentication passing status of the secondary authentication.
[0013] A second aspect of this aspect provides an account authentication system based on a risk rule model, comprising: An account behavior data acquisition module, which acquires historical account behavior data of the account to be authenticated when the account to be authenticated logs in; An account risk level determination module, wherein the account risk level determination module determines the account risk level according to the historical account behavior data based on a preset risk rule model; An authentication module is used to authenticate the account to be authenticated according to the account risk level using a preset risk control strategy.
[0014] Furthermore, the preset risk rule model includes: 1) Sudden activity detection: detect whether the last access time of the account and the current access time of the account exceed the specified number of days; 2) Brute force attack detection: Check whether the account has multiple authentication failure requests within a short period of time; 3) Slow attack detection: detect whether a certain access address sends authentication failure requests to multiple accounts within a preset time period; 4) Location detection: detect whether the account has logged in outside the set country and city; 5) Device feature detection: detect whether the device used to log in to the current account is not in the list of common devices of the current account; 6) Database attack detection: detect whether a certain access address has multiple authentication success and authentication failure requests within a certain period of time, and among the large number of authentication failure requests, the attempted account does not belong to the current enterprise; 7) Multiple account login detection: detect whether the same access address has logged in multiple accounts within a preset time period; 8) Usage time detection: detect whether the account has logged in outside the set time range; 9) Operating system feature detection: Check whether the operating system type and version used by the account in this request are inconsistent with the operating system type and version used in the past.
[0015] Compared with the prior art, the technical solution of the present invention has the following beneficial effects: The account authentication method based on the risk rule model provided by the present invention realizes a multi-dimensional three-dimensional authentication system, and also realizes the smoothness of the whole process of login records, risk model judgment, enhanced authentication, and access control blocking. In addition, the risk rule model configuration adjustment is quite convenient. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] Figure 1 A flowchart of an account authentication method based on a risk rule model provided by an embodiment of the present invention.
[0017] Figure 2 A module diagram of an account authentication system based on a risk rule model provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0018] The accompanying drawings are only used for illustrative purposes and are not to be construed as limiting the present application; In order to better illustrate the present embodiment, some parts in the drawings may be omitted, enlarged or reduced, and do not represent the size of the actual product; It is understandable to those skilled in the art that some well-known structures and their descriptions may be omitted in the drawings.
[0019] The technical solution of the present invention is further described below in conjunction with the accompanying drawings and embodiments.
[0020] Example This embodiment provides an account authentication method based on a risk rule model, such as Figure 1 As shown, the following steps are included: When the account to be authenticated logs in, the historical account behavior data of the account to be authenticated is obtained; Based on a preset risk rule model, determine the account risk level according to the historical account behavior data; According to the account risk level, the account to be authenticated is authenticated using a preset risk control strategy.
[0021] In a further embodiment, obtaining historical account behavior data of the account to be authenticated includes: Obtain a login log of the account to be authenticated, and obtain historical account behavior data of the account to be authenticated from the login log.
[0022] In a further embodiment, the historical account behavior data includes access location, access time, access account number, access device, operating system type, operating system version and access behavior.
[0023] In a further embodiment, the preset risk rule model includes: 1) Sudden activity detection: Based on the time characteristics of the user portrait, it detects whether the last access time of the account and the current access time exceed the specified number of days; 2) Brute force detection: used to detect whether there are attackers targeting a specific account and using the method of traversing password combinations to guess the correct password. Specifically, it detects whether the account has multiple authentication failure requests in a short period of time. 3) Slow attack detection: used to detect the behavior of a specific IP using some weak passwords to guess a large number of passwords for multiple accounts within a period of time within the threshold range of authentication failure lock times. Specifically, it detects whether a certain access address sends authentication failure requests to multiple accounts within a preset time period; 4) Location detection: detect whether the account has logged in outside the set country and city; 5) Device feature detection: detect whether the device used by the current account to log in is not in the common device list of the current account; specifically, the common device list can store 3 common devices; 6) Database attack detection: used to detect the behavior of a specific IP address using account and password data pulled from a third-party data source to verify the account and password in the current environment within a period of time. Specifically, it detects whether a certain access address has multiple successful and failed authentication requests within a certain period of time, and among the large number of failed authentication requests, the attempted account does not belong to the current enterprise; 7) Multiple account login detection: detect whether the same access address has logged in multiple accounts within a preset time period; 8) Usage time detection: detect whether the account has logged in outside the set time range; 9) Operating system feature detection: Check whether the operating system type and version used by the account in this request are inconsistent with the operating system type and version used in the past.
[0024] In a further embodiment, based on a preset risk rule model, the account risk level is determined according to the historical account behavior data. The corresponding relationship between the risk rule model and the risk label level can be flexibly configured. The current setting, in this embodiment, is set to: If at least one of the test results of tests 4), 5), 7), 8) and 9) in the risk rule model is yes, and the test results of the other tests are no, then the account risk level of the account to be authenticated is judged to be a low risk level; If at least one of the test results of tests 1) and 3) in the risk rule model is yes, and the test results of tests 2) and 6) are no, then the account risk level of the account to be authenticated is determined to be a medium risk level; If at least one of the test results of tests 2) and 6) in the risk rule model is yes, then the account risk level of the account to be authenticated is determined to be a high risk level.
[0025] In a further embodiment, according to the account risk level, the account to be authenticated is authenticated using a preset risk control strategy, including: When the account risk level of the account to be authenticated is a low risk level or a medium risk level, the account risk level of the account to be authenticated is recorded; When the account risk level of the account to be authenticated is a high risk level, the account risk level of the account to be authenticated is recorded, and a secondary authentication is performed on the account to be authenticated.
[0026] In a further embodiment, if the secondary authentication of the account to be authenticated fails, the authentication of the account to be authenticated fails.
[0027] In a further embodiment, in the detection 7) in the risk rule model, the authentication success situation of the secondary authentication is also combined, and the identity of the attacker can be confirmed by recording the authentication success situation or the account most used by the IP can be viewed through the exception list.
[0028] In a specific embodiment, if the last login time of user Zhang San is January 1st and the current login time is June 1st, which is greater than the specified number of days 90 days set in the risk rule model for detection (1) sudden activity detection (based on the time characteristics of the user portrait as the basis for judgment, if the user's last activity time and the current request time exceed the specified number of days, it is considered a violation of the policy), then the record is recorded as a medium risk level, and the backend administrator can focus on the user's subsequent login behavior.
[0029] In another example, when someone logs into the enterprise system, the login account and password are incorrect multiple times, and the account name "gongji" entered does not belong to the employee account of the enterprise. This meets the (6) database attack detection (used to detect the behavior of a specific IP using account and password data dragged from a third-party data source to verify the account and password in the current environment within a period of time. Its characteristic 1 is that a certain IP may have a large number of successful and failed authentication requests within a period of time. Its characteristic 2 is that among a large number of failed authentication requests, the attempted account may not belong to the current enterprise) rule, and is recorded as a high risk level. When someone tries to log in, the enhanced secondary authentication interface is triggered, and the backend administrator can focus on the user's subsequent login behavior.
[0030] Another embodiment of the present invention also provides an account authentication system based on a risk rule model, such as Figure 2 As shown, including: An account behavior data acquisition module, which acquires historical account behavior data of the account to be authenticated when the account to be authenticated logs in; An account risk level determination module, wherein the account risk level determination module determines the account risk level according to the historical account behavior data based on a preset risk rule model; An authentication module is used to authenticate the account to be authenticated according to the account risk level using a preset risk control strategy.
[0031] In a further embodiment, the preset risk rule model includes: 1) Sudden activity detection: Based on the time characteristics of the user portrait, it detects whether the last access time of the account and the current access time exceed the specified number of days; 2) Brute force detection: used to detect whether there are attackers targeting a specific account and using the method of traversing password combinations to guess the correct password. Specifically, it detects whether the account has multiple authentication failure requests in a short period of time. 3) Slow attack detection: used to detect the behavior of a specific IP using some weak passwords to guess a large number of passwords for multiple accounts within a period of time within the threshold range of authentication failure lock times. Specifically, it detects whether a certain access address sends authentication failure requests to multiple accounts within a preset time period; 4) Location detection: detect whether the account has logged in outside the set country and city; 5) Device feature detection: detect whether the device used by the current account to log in is not in the common device list of the current account; specifically, the common device list can store 3 common devices; 6) Database attack detection: used to detect the behavior of a specific IP address using account and password data pulled from a third-party data source to verify the account and password in the current environment within a period of time. Specifically, it detects whether a certain access address has multiple successful and failed authentication requests within a certain period of time, and among the large number of failed authentication requests, the attempted account does not belong to the current enterprise; 7) Multiple account login detection: detect whether the same access address has logged in multiple accounts within a preset time period; 8) Usage time detection: detect whether the account has logged in outside the set time range; 9) Operating system feature detection: Check whether the operating system type and version used by the account in this request are inconsistent with the operating system type and version used in the past.
[0032] The same or similar reference numerals correspond to the same or similar components; The terms used to describe the positional relationship in the drawings are only used for illustrative purposes and should not be construed as limiting the present application; Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not intended to limit the embodiments of the present invention. For those skilled in the art, other different forms of changes or modifications can be made based on the above description. It is not necessary and impossible to list all the embodiments here. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the claims of the present invention.
Claims
1. An account authentication method based on a risk rule model, characterized in that: The following steps are involved: When the account to be authenticated logs in, the historical account behavior data of the account to be authenticated is obtained; Based on a preset risk rule model, determine the account risk level according to the historical account behavior data; According to the account risk level, the account to be authenticated is authenticated using a preset risk control strategy.
2. The account authentication method based on the risk rule model according to claim 1, characterized in that: Obtain the historical account behavior data of the account to be authenticated, including: Obtain a login log of the account to be authenticated, and obtain historical account behavior data of the account to be authenticated from the login log.
3. The account authentication method based on the risk rule model according to claim 1, characterized in that: The historical account behavior data includes access location, access time, access account, access device, operating system type, operating system version and access behavior.
4. The account authentication method based on the risk rule model according to claim 3 is characterized in that: The preset risk rule model includes: 1) Sudden activity detection: detect whether the last access time of the account and the current access time of the account exceed the specified number of days; 2) Brute force attack detection: Check whether the account has multiple authentication failure requests within a short period of time; 3) Slow attack detection: detect whether a certain access address sends authentication failure requests to multiple accounts within a preset time period; 4) Location detection: detect whether the account has logged in outside the set country and city; 5) Device feature detection: detect whether the device used to log in to the current account is not in the list of common devices of the current account; 6) Database attack detection: detect whether a certain access address has multiple authentication success and authentication failure requests within a certain period of time, and among the large number of authentication failure requests, the attempted account does not belong to the current enterprise; 7) Multiple account login detection: detect whether the same access address has logged in multiple accounts within a preset time period; 8) Usage time detection: detect whether the account has logged in outside the set time range; 9) Operating system feature detection: Check whether the operating system type and version used by the account in this request are inconsistent with the operating system type and version used in the past.
5. The account authentication method based on the risk rule model according to claim 4 is characterized in that: Based on the preset risk rule model, the account risk level is judged according to the historical account behavior data, including: If at least one of the detection results of the use location detection, device feature detection, multiple account login detection, use time detection and operating system feature detection in the risk rule model is yes, and the detection results of the other detections are no, then the account risk level of the account to be authenticated is judged to be a low risk level; If at least one of the detection results of sudden activity detection and slow attack detection in the risk rule model is yes, and the detection results of brute force cracking detection and credential stuffing attack detection are no, then the account risk level of the account to be authenticated is determined to be medium risk level; If at least one of the detection results of the brute force cracking detection and the credential stuffing attack detection in the risk rule model is yes, then the account risk level of the account to be authenticated is judged to be a high risk level.
6. The account authentication method based on the risk rule model according to claim 5, characterized in that: According to the account risk level, the account to be authenticated is authenticated using a preset risk control strategy, including: When the account risk level of the account to be authenticated is a low risk level or a medium risk level, the account risk level of the account to be authenticated is recorded; When the account risk level of the account to be authenticated is a high risk level, the account risk level of the account to be authenticated is recorded, and a secondary authentication is performed on the account to be authenticated.
7. The account authentication method based on the risk rule model according to claim 6, characterized in that: If the secondary authentication of the account to be authenticated fails, the authentication of the account to be authenticated fails.
8. The account authentication method based on the risk rule model according to claim 7, characterized in that: In the multi-account login detection in the risk rule model, the account that uses the most access addresses is checked through the exception list in combination with the authentication passing situation of the secondary authentication.
9. An account authentication system based on a risk rule model, characterized in that: include: An account behavior data acquisition module, which acquires historical account behavior data of the account to be authenticated when the account to be authenticated logs in; An account risk level determination module, wherein the account risk level determination module determines the account risk level according to the historical account behavior data based on a preset risk rule model; An authentication module is used to authenticate the account to be authenticated according to the account risk level using a preset risk control strategy.
10. The account authentication system based on the risk rule model according to claim 9, characterized in that: The preset risk rule model includes: 1) Sudden activity detection: detect whether the last access time of the account and the current access time of the account exceed the specified number of days; 2) Brute force attack detection: Check whether the account has multiple authentication failure requests within a short period of time; 3) Slow attack detection: detect whether a certain access address sends authentication failure requests to multiple accounts within a preset time period; 4) Location detection: detect whether the account has logged in outside the set country and city; 5) Device feature detection: detect whether the device used to log in to the current account is not in the list of common devices of the current account; 6) Database attack detection: detect whether a certain access address has multiple authentication success and authentication failure requests within a certain period of time, and among the large number of authentication failure requests, the attempted account does not belong to the current enterprise; 7) Multiple account login detection: detect whether the same access address has logged in multiple accounts within a preset time period; 8) Usage time detection: detect whether the account has logged in outside the set time range; 9) Operating system feature detection: Check whether the operating system type and version used by the account in this request are inconsistent with the operating system type and version used in the past.
Citation Information
Patent Citations
Login interception method and system based on joint anti-collision library platform
CN111083165A
Login verification method and device, equipment and storage medium
CN113194079A
Cloud platform dynamic identity verification method and device, computer equipment and storage medium
CN118740483A
Cited By
Cross-system non-inductive switching authentication method and device for e-commerce
CN120602224A
Cross-system non-sensing switching authentication method and device for e-commerce
CN120602224B
Database adaptive authentication method and system combined with meta-learning model
CN121887550A
A Database Adaptive Authentication Method and System Combining Meta-Learning Model
CN121887550B
