Defense method and device for effectively preventing automatic attack, equipment and medium

By setting the observation time period and using user behavior data scoring rules to distinguish terminal types, the problem that traditional methods cannot protect against short-term high-frequency multi-source automation attacks in time is solved, and effective interception of malicious attacks and rapid access to normal terminals is achieved. .

CN119094162APending Publication Date: 2024-12-06刘勇
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411055645.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-02
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

Traditional methods cannot effectively and promptly protect short-term high-frequency multi-source automated attacks, resulting in the attacker completing the attack after detecting an exception and being unable to intercept it.

Method used

By setting the observation time period, receiving and counting access requests, it is judged that the terminal is malicious, suspicious or normal. The request of the malicious terminal is discarded after the period ends, and the request of the normal terminal is forwarded to the server, and the terminal type is distinguished by the user behavior data scoring rules.

Benefits of technology

It realizes effective and timely protection against short-term high-frequency multi-source automation attacks, ensuring that normal terminals can access the server normally and intercept malicious attacks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094162A_ABST
    Figure CN119094162A_ABST
Patent Text Reader

Abstract

The invention relates to a defense method and device for effectively preventing automatic attacks, equipment and a medium. The method comprises the following steps: acquiring a preset observation time period; for each observation time period, receiving an access request sent to the server during the observation time period, and judging whether the terminal sending the access request is a hostile attack terminal or a normal terminal; if the terminal is a hostile attack terminal, after the observation time period is ended, discarding the access request sent by the hostile attack terminal and received during the observation time period, and if the terminal is a normal terminal, after the observation time period is ended, forwarding the access request sent by the normal terminal and received during the observation time period to the server. According to the invention, short-time high-frequency multi-source automatic attacks can be effectively and timely protected.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of network security, and in particular relates to a defense method, device, equipment and medium for effectively protecting against automated attacks. Background Art

[0002] In the era of digital economy, all walks of life continue to undergo digital transformation, and a large number of business systems have begun to involve the Internet and the Internet of Things. At the same time, various automated attacks have also emerged in an endless stream, such as wool parties, network water armies, various data leakage incidents, and corporate cyber attacks. Behind these security incidents, there are shadows of automated attacks. Automated attacks will cause great security risks to the websites, apps, and various API services of enterprises and institutions, including but not limited to various vulnerability scanning behaviors, ticket swiping and ticket grabbing behaviors, hacker intrusions, various sensitive data acquisition, and even business downtime. Among them, short-term, high-frequency, and multi-source automated attacks are the most complex and difficult to prevent. Its characteristics are: through the method of IP address pool or card pool, cat pool, it is forged into multiple terminals, or even multiple real terminals are controlled to access a certain functional module of a specific business system in a short time (usually about 1-2 minutes) (such as the registration of expert numbers in the hospital registration system). As a result, normal users cannot use the functions of the business normally.

[0003] There are two traditional protection schemes for automated attacks. The first is to analyze access logs to find anomalies, but due to the lag in log analysis, when the anomaly is found, the attacker has already completed the attack and cannot play a protective role. The second is to find anomalies based on changes in IP access frequency, but because the attacker uses short-term multi-source tactics, the IP-based access frequency change detection mechanism still needs a certain amount of time to detect anomalies. When the anomaly is found, the attacker has already completed the attack and cannot play a protective role. Therefore, traditional automated attack protection methods cannot effectively and timely protect against short-term, high-frequency, multi-source automated attacks. Summary of the invention

[0004] The purpose of the present invention is to provide a defense method, device, equipment and medium for effectively protecting against automated attacks, which can effectively and timely protect against short-term, high-frequency and multi-source automated attacks.

[0005] The present invention is achieved through the following technical solutions:

[0006] A method for effectively protecting against automated attacks comprises the following steps:

[0007] Get the preset observation time period;

[0008] For each observation time period, receiving an access request sent to the server during the observation time period, and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal;

[0009] If it is a malicious attack terminal, then after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period will be discarded. If it is a normal terminal, then after the observation time period ends, the access request sent by the normal terminal received during the observation time period will be forwarded to the server.

[0010] Further, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal includes:

[0011] For each access request, obtaining relevant information of the access request, the relevant information at least including a terminal ID of a terminal sending the access request;

[0012] The access requests received during the observation time period are counted according to the terminal ID to obtain the number of access requests sent by each terminal during the observation time period;

[0013] For each terminal, determine whether the number of requests from the terminal is greater than a preset malicious request threshold;

[0014] If yes, the terminal is judged to be a malicious attack terminal;

[0015] If not, it is determined that the terminal is a normal terminal.

[0016] Further, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal includes:

[0017] For each access request, obtain relevant information of the access request, where the relevant information includes non-interaction data or at least one user behavior data, where the user behavior data is one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information;

[0018] For each of the access requests, determining whether the relevant information of the access request is non-interaction data;

[0019] If yes, it is determined that the terminal sending the access request is a malicious attack terminal;

[0020] If not, it is determined that the terminal sending the access request is a normal terminal.

[0021] Further, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal includes:

[0022] receiving an access request sent to the server during an observation time period, and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal, or a normal terminal;

[0023] If it is a malicious attack terminal, after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period is discarded, and if it is a normal terminal, after the observation time period ends, the access request sent by the normal terminal received during the observation time period is forwarded to the server, the step includes:

[0024] If it is a malicious attack terminal, then after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period will be discarded; if it is a suspicious terminal, then after the observation time period ends, the access request sent by the suspicious terminal received during the observation time period will be delayed and forwarded to the server; if it is a normal terminal, then after the observation time period ends, the access request sent by the normal terminal received during the observation time period will be immediately forwarded to the server.

[0025] Further, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal includes:

[0026] For each access request, obtaining relevant information of the access request, the relevant information at least including a terminal ID of a terminal sending the access request;

[0027] The access requests received during the observation time period are counted according to the terminal ID to obtain the number of access requests sent by each terminal during the observation time period;

[0028] For each terminal, determine whether the number of requests from the terminal is greater than a preset malicious request threshold;

[0029] If it is greater than the malicious request threshold, the terminal is judged to be a malicious attack terminal;

[0030] If it is less than or equal to the malicious request threshold, determine whether the number of requests from the terminal is greater than the preset suspicious request threshold;

[0031] If it is greater than the suspicious request threshold, the terminal is judged to be a suspicious terminal;

[0032] If it is less than or equal to the suspicious request threshold, the terminal is judged to be a normal terminal.

[0033] Further, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal includes:

[0034] For each access request, obtain relevant information of the access request, where the relevant information includes non-interaction data or at least one user behavior data, where the user behavior data is one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information;

[0035] For each access request, determine whether the relevant information of the access request is non-interaction data;

[0036] If there is no interactive data, it is determined that the terminal sending the access request is a malicious attack terminal;

[0037] If it is not non-interaction data, then count the amount of user behavior data to determine whether the amount of data is greater than or equal to a preset data threshold;

[0038] If it is less than the data threshold, the terminal sending the access request is judged to be a suspicious terminal;

[0039] If it is greater than or equal to the data threshold, it is determined that the terminal sending the access request is a normal terminal.

[0040] Further, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal includes:

[0041] For each access request, obtain relevant information of the access request, the relevant information including non-interaction data or at least one user behavior data, the user behavior data is one of mouse click information, mouse movement information, touch screen operation information and keyboard input information, the mouse click information at least includes mouse click frequency, and the touch screen operation information includes screen click frequency;

[0042] For each access request, determine whether the relevant information of the access request is non-interaction data;

[0043] If there is no interactive data, it is determined that the terminal sending the access request is a malicious attack terminal;

[0044] If it is not non-interaction data, the access request is scored according to a preset scoring rule to obtain a scoring score of the access request, and it is determined whether the scoring score is greater than or equal to a first preset score;

[0045] If it is greater than or equal to a first preset score, it is determined that the terminal sending the access request is a normal terminal;

[0046] If it is less than the first preset score, determine whether the scoring score is greater than or equal to the second preset score;

[0047] If the score is greater than or equal to a second preset score, the terminal sending the access request is determined to be a suspicious terminal;

[0048] If it is less than a second preset score, it is determined that the terminal sending the access request is a malicious attack terminal;

[0049] The step of scoring the access request according to the preset scoring rules includes:

[0050] Set the initial scoring score of the access request to zero;

[0051] Determine whether the mouse click information is included. If the mouse click information is included, add the preset bonus score to the score to obtain a new score, and determine whether the mouse click frequency is greater than the preset first frequency;

[0052] If the mouse click frequency is greater than the preset first frequency, the preset deduction score is subtracted from the score to obtain a new score;

[0053] Determine whether the mouse movement information is included. If the mouse movement information is included, add the preset bonus score to the score to obtain a new score.

[0054] Determine whether touch screen operation information is included. If touch screen operation information is included, add a preset bonus score to the score to obtain a new score, and determine whether the screen click frequency is greater than a preset second frequency;

[0055] If the screen click frequency is greater than the preset second frequency, the preset deduction score is subtracted from the score to obtain a new score;

[0056] Determine whether keyboard input information is included. If touch screen operation information is included, add the preset bonus score to the score to obtain a new score.

[0057] The present invention also provides a defense device for effectively protecting against automated attacks, comprising:

[0058] An acquisition module, used to acquire a preset observation time period;

[0059] A receiving module, for receiving, for each observation time period, an access request sent to the server during the observation time period, and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal;

[0060] The processing module is used to discard the access request sent by the malicious attack terminal during the observation time period after the observation time period ends if it is a malicious attack terminal, and forward the access request sent by the normal terminal during the observation time period to the server after the observation time period ends if it is a normal terminal.

[0061] The present invention also discloses an electronic device, comprising a storage device and a processor, wherein the storage device stores a computer program, and the processor implements the steps of any one of the above methods when executing the computer program.

[0062] The present invention also discloses a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above methods are implemented.

[0063] Compared with the prior art, the beneficial effects of the present invention are as follows: by receiving access requests sent to the server within an observation time period, and judging whether the terminal sending the access request is a malicious attack terminal or a normal terminal, if it is a malicious attack terminal, then after the observation time period ends, the access requests sent to the server by the malicious attack terminal received during the observation time period are discarded; if it is a normal terminal, the access requests sent by the normal terminal received during the observation time period are forwarded to the server, thereby intercepting all attacks on the server by the malicious attack terminal, being able to effectively and timely protect against short-term, high-frequency, and multi-source automated attacks, and ensuring that normal terminals can access the server normally. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] Figure 1 A schematic diagram of a flow chart of a defense method for effectively protecting against automated attacks according to the present invention;

[0065] Figure 2 A schematic diagram of a module of a defense method for effectively protecting against automated attacks according to the present invention;

[0066] Figure 3 A schematic block diagram of the structure of an electronic device according to an embodiment of the present invention;

[0067] Figure 4 It is a schematic diagram of the structure of an embodiment of a computer-readable storage medium of the present invention. DETAILED DESCRIPTION

[0068] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0069] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0070] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0071] It should be noted that, in this article, 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 sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0072] In the description of the present invention, it should be noted that the terms "upper", "lower", "inside", "outside", etc. indicate directions or positional relationships based on the directions or positional relationships shown in the accompanying drawings, or are directions or positional relationships in which the product of the invention is usually placed when in use. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific direction, be constructed and operated in a specific direction, and therefore should not be understood as a limitation on the present invention.

[0073] See also Figure 1 , Figure 1 The flowchart of the method for effectively protecting against automated attacks of the present invention is as follows. The method for effectively protecting against automated attacks comprises the following steps:

[0074] S1. Obtain a preset observation time period;

[0075] S2. For each observation time period, receiving an access request sent to the server during the observation time period, and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal;

[0076] S3. If it is a malicious attack terminal, then after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period will be discarded; if it is a normal terminal, then after the observation time period ends, the access request sent by the normal terminal received during the observation time period will be forwarded to the server.

[0077] In the above step S1, a preset observation time period is obtained, and the observation time period can be set according to actual needs. For example, in this embodiment, the observation time period is set to 5 seconds. That is, one observation time period is every 5 seconds, and after one observation time period ends, the next observation time period is immediately entered, so that the access request sent to the server can be monitored from the initial start time to the subsequent duration.

[0078] In the above step S2, for each observation time period, all access requests sent to the server during the observation time period are received, and the received access requests are stored in a queue pool, and the received access requests are temporarily forwarded to the server, so as to judge and process the terminal sending the access request based on the received access request, and judge whether the terminal sending the access request is a malicious attack terminal or a normal terminal, so as to avoid sending automated attack access requests to the server.

[0079] Further, in step S2, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal includes:

[0080] S211. For each access request, obtain relevant information of the access request, where the relevant information at least includes a terminal ID of a terminal sending the access request;

[0081] S212, counting the access requests received during the observation time period according to the terminal ID, and obtaining the number of access requests sent by each terminal during the observation time period;

[0082] S213: for each terminal, determine whether the number of requests from the terminal is greater than a preset malicious request threshold;

[0083] S214: If yes, determine that the terminal is a malicious attack terminal;

[0084] S215: If not, determine that the terminal is a normal terminal.

[0085] In the above step S211, the relevant information of the access request sent by the terminal to the server usually includes the terminal ID. Therefore, when each access request is received, the relevant information of each access request is obtained, and the terminal ID of the terminal sending the access request is obtained from the relevant information.

[0086] In the above step S212, based on the terminal ID in the access request, the access requests received during the observation time period are counted according to the terminal ID to obtain the number of access requests containing the same terminal ID, thereby obtaining the number of access requests sent by each terminal to the server during the observation time period.

[0087] In addition, the relevant information of the access request generally also includes the specific access object to be accessed, such as for the registration system, the access object may be expert number 1, expert number 2, etc. Further, in step S21, the relevant information also includes the access object of the access request;

[0088] In step S212, the step of counting the access requests received during the observation time period according to the terminal ID to obtain the number of access requests sent by each terminal during the observation time period includes:

[0089] S2121. Count the access requests received during the observation time period according to the terminal ID and the access object, and obtain the number of access requests sent by each terminal to the access object during the observation time period.

[0090] In step S2121, the access requests received during the observation time period are counted according to the terminal ID and the access object to obtain the number of access requests containing the same terminal ID and the same access object, thereby obtaining the number of access requests sent by each terminal to the access object during the observation time period.

[0091] In the above steps S213 to S215, a preset malicious request threshold is obtained, and the malicious request threshold can be set according to actual needs. In this embodiment, the malicious request threshold is set to 9. During the observation time period, if the number of requests of the terminal is greater than the malicious request threshold, such as the number of requests of the terminal is 10, which is greater than 9, then the terminal can be judged to be a malicious attack terminal; if the number of requests of the terminal is less than or equal to the malicious request threshold, such as the number of requests of the terminal is 2, which is less than 9, then the terminal can be judged to be a normal terminal.

[0092] Further, in step S2, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal includes:

[0093] S221. For each access request, obtain relevant information of the access request, where the relevant information includes non-interaction data or at least one user behavior data, where the user behavior data is one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information;

[0094] S222: for each of the access requests, determine whether the relevant information of the access request is non-interactive data;

[0095] S223: If yes, determine that the terminal sending the access request is a malicious attack terminal;

[0096] S224: If not, determine whether the terminal sending the access request is a normal terminal.

[0097] In the above step S221, when the terminal sends an access request, there will generally be user behavior data. These data can be collected and saved in the relevant information. If there is no user behavior data, no interaction data will be displayed in the relevant information. Therefore, when each access request is received, no interaction data or at least one user behavior data can be obtained from the relevant information of each access request.

[0098] In the above steps S222 to S224, for each access request, if the relevant information of the access request is no interactive data, it means that the access request is not sent to the server by a manually operated terminal, and it can be determined that the terminal sending the access request is a malicious attack terminal. On the contrary, if there is user behavior data, it can be determined that the terminal sending the access request is a normal terminal.

[0099] In the above step S3, different processing methods are adopted for different terminals. After the observation time period ends, the access requests of normal terminals received during the observation time period are forwarded to the server, so that the normal terminals can access the server normally. The access requests sent by malicious attack terminals received during the observation time period are discarded and the access requests of malicious attack terminals are rejected. Therefore, before the automated attack reaches the server, the attack access requests of the malicious attack terminals are intercepted, so as to achieve effective and timely protection against short-term, high-frequency and multi-source automated attacks.

[0100] Furthermore, in order to intercept and protect against automated attacks in a more detailed manner, in step S2, the steps of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal include:

[0101] S2a, receiving an access request sent to the server during the observation time period, and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal, or a normal terminal;

[0102] In step S3, if it is a malicious attack terminal, then after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period is discarded, and if it is a normal terminal, then after the observation time period ends, the access request sent by the normal terminal received during the observation time period is forwarded to the server. The steps include:

[0103] S3a. If it is a malicious attack terminal, then after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period will be discarded; if it is a suspicious terminal, then after the observation time period ends, the access request sent by the suspicious terminal received during the observation time period will be delayed and forwarded to the server; if it is a normal terminal, then after the observation time period ends, the access request sent by the normal terminal received during the observation time period will be immediately forwarded to the server.

[0104] Further, in step S2a, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal includes:

[0105] S2a11. For each access request, obtain relevant information of the access request, where the relevant information at least includes a terminal ID of the terminal sending the access request;

[0106] S2a12, counting the access requests received during the observation time period according to the terminal ID, and obtaining the number of access requests sent by each terminal during the observation time period;

[0107] S2a13. For each terminal, determine whether the number of requests from the terminal is greater than a preset malicious request threshold;

[0108] S2a14: If it is greater than the malicious request threshold, the terminal is judged to be a malicious attack terminal;

[0109] S2a15. If it is less than or equal to the malicious request threshold, determine whether the number of requests from the terminal is greater than a preset suspicious request threshold;

[0110] S2a16. If it is greater than the suspicious request threshold, the terminal is determined to be a suspicious terminal;

[0111] S2a17: If it is less than or equal to the suspicious request threshold, the terminal is judged to be a normal terminal.

[0112] In the above steps S2a11 to S2a17, the terminals are divided into three types, normal, suspicious and malicious attack, and a suspicious request threshold is preset. The suspicious request threshold can be set according to actual needs. For example, in this embodiment, the suspicious request threshold is set to 2. During the observation time period, if the number of requests of the terminal is greater than the malicious request threshold, such as the number of access requests of the terminal is 10, which is greater than 9, then the terminal can be judged to be a malicious attack terminal; if the number of requests of the terminal is less than or equal to the malicious request threshold, then it is judged whether the number of requests of the terminal is greater than the preset suspicious request threshold, such as the number of requests of the terminal is 3, which is greater than 2, then the terminal is judged to be a suspicious terminal and marked as a suspicious terminal; if the number of requests of the terminal is less than or equal to the suspicious request threshold, such as the number of requests of the terminal is 1, which is less than 3, then the terminal is judged to be a normal terminal.

[0113] Further, in step S2a, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal includes:

[0114] S2a21. For each access request, obtain relevant information of the access request, where the relevant information includes non-interaction data or at least one user behavior data, where the user behavior data is one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information;

[0115] S2a22, for each of the access requests, determining whether the relevant information of the access request is non-interaction data;

[0116] S2a23. If there is no interactive data, it is determined that the terminal sending the access request is a malicious attack terminal;

[0117] S2a24. If it is not non-interaction data, count the data quantity of the user behavior data and determine whether the data quantity is greater than or equal to a preset data threshold;

[0118] S2a25, if it is less than the data threshold, the terminal sending the access request is determined to be a suspicious terminal;

[0119] S2a26. If it is greater than or equal to the data threshold, it is determined that the terminal sending the access request is a normal terminal.

[0120] In the above steps S2a21 to S2a26, the terminals are divided into three types, normal, suspicious and malicious attack, and a data threshold is preset. The data threshold can be set according to actual needs. For example, in this embodiment, the data threshold is set to 2. For each access request, if the relevant information of the access request is no interactive data, it means that the access request is not sent to the server by a manually operated terminal, and the terminal sending the access request can be judged to be a malicious attack terminal. On the contrary, if there is user behavior data, the data quantity of the user behavior data is counted. If the data quantity of the user behavior data is 1 and less than 2, the terminal is judged to be a suspicious terminal. If the data quantity of the user behavior data is 2 and greater than or equal to 2, the terminal is judged to be a normal terminal.

[0121] Further, the two judgment methods of steps S2a11 to S2a17 and steps S2a21 to S2a26 can be combined to judge the terminal sending the access request. In step S2a, the step of receiving the access request sent to the server during the observation time period and judging whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal includes:

[0122] S2a31. For each access request, obtain relevant information of the access request, the relevant information including the terminal ID of the terminal sending the access request, and the relevant information also including non-interaction data or at least one user behavior data, the user behavior data being one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information;

[0123] S2a32, counting the access requests received during the observation time period according to the terminal ID, and obtaining the number of access requests sent by each terminal during the observation time period;

[0124] S2a33. For each terminal, determine whether the number of requests from the terminal is greater than a preset malicious request threshold;

[0125] S2a34, if it is greater than the malicious request threshold, the terminal is marked as malicious;

[0126] S2a35. If it is less than or equal to the malicious request threshold, determine whether the number of requests from the terminal is greater than a preset suspicious request threshold;

[0127] S2a36. If it is greater than the suspicious request threshold, the terminal is marked as suspicious;

[0128] S2a37, if it is less than or equal to the suspicious request threshold, the terminal is marked as normal;

[0129] S2a38. For each access request, determine whether the relevant information of the access request is non-interaction data;

[0130] S2a39, if there is no interactive data, the terminal sending the access request is marked as malicious;

[0131] S2a310, if it is not non-interaction data, counting the data quantity of the user behavior data, and determining whether the data quantity is greater than or equal to a preset data threshold;

[0132] S2a311, if it is less than the data threshold, the terminal sending the access request is marked as suspicious;

[0133] S2a312: If it is greater than or equal to the data threshold, the terminal sending the access request is marked as normal.

[0134] S2a313: The terminal with the malicious mark is judged as a malicious attack terminal, the terminal with two normal marks is judged as a normal terminal, and the remaining terminals are judged as suspicious terminals.

[0135] In the above steps S2a31 to S2a313, the two judgment methods of steps S2a11 to S2a17 and steps S2a21 to S2a26 are combined. For each judgment method, the terminal judged as a malicious attack terminal is marked as malicious, the terminal judged as a suspicious terminal is marked as suspicious, and the terminal judged as a normal terminal is marked as normal. Only when both judgment methods judge the terminal as a normal terminal, that is, the terminal with two normal marks, is considered a normal terminal. As long as there is one judgment method that judges the terminal as a malicious attack terminal, that is, the terminal with one malicious mark, it is considered a malicious attack terminal, and the remaining terminals are all considered suspicious terminals.

[0136] Further, in step S2a, the step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal includes:

[0137] S2a41. For each access request, obtain relevant information of the access request, the relevant information including non-interaction data or at least one user behavior data, the user behavior data being one of mouse click information, mouse movement information, touch screen operation information and keyboard input information, the mouse click information at least including mouse click frequency, and the touch screen operation information including screen click frequency;

[0138] S2a42, for each access request, determining whether the relevant information of the access request is non-interaction data;

[0139] S2a43, if there is no interactive data, it is determined that the terminal sending the access request is a malicious attack terminal;

[0140] S2a44. If it is not non-interaction data, score the access request according to a preset scoring rule to obtain a score of the access request, and determine whether the score is greater than or equal to a first preset score;

[0141] S2a45, if it is greater than or equal to the first preset score, determining that the terminal sending the access request is a normal terminal;

[0142] S2a46. If the score is less than the first preset score, determine whether the scoring score is greater than or equal to the second preset score;

[0143] S2a47, if it is greater than or equal to a second preset score, determining that the terminal sending the access request is a suspicious terminal;

[0144] S2a48, if it is less than a second preset score, determining that the terminal sending the access request is a malicious attack terminal;

[0145] The step of scoring the access request according to the preset scoring rules includes:

[0146] S2a441, setting the initial score of the access request to zero;

[0147] S2a442, determining whether mouse click information is included, if mouse click information is included, adding a preset bonus score to the score to obtain a new score, and determining whether the mouse click frequency is greater than a preset first frequency;

[0148] S2a443, if the mouse click frequency is greater than the preset first frequency, subtract the preset deduction score from the scoring score to obtain a new scoring score;

[0149] S2a444, determining whether the mouse movement information is included, and if the mouse movement information is included, adding a preset bonus score to the score to obtain a new score;

[0150] S2a445, determining whether touch screen operation information is included. If touch screen operation information is included, adding a preset bonus score to the score to obtain a new score, and determining whether the screen click frequency is greater than a preset second frequency;

[0151] S2a445, if the screen click frequency is greater than the preset second frequency, subtract the preset deduction score from the scoring score to obtain a new scoring score;

[0152] S2a446, determining whether keyboard input information is included; if touch screen operation information is included, adding a preset bonus score to the score to obtain a new score.

[0153] In the above steps S2a41 to S2a48, an interactive behavior standard is set to determine whether the access request is issued after a normal user operation or by a mechanical operation. For each access request, if the relevant information of the access request is no interactive data, it means that the access request is not sent by a manually operated terminal to the server, and the terminal sending the access request can be judged to be a malicious attack terminal. If the relevant information of the access request has user behavior data, the access request is scored according to the user behavior data to obtain the scoring score of the access request, and then based on the preset first preset score and the second preset score, it is judged whether the interactive behavior of the access request meets the judgment standard. The first preset score and the second preset score can be determined according to the actual needs of the business. If the scoring score of the access request is greater than or equal to the first preset score, it means that the access request meets the interactive judgment standard, so it is judged that the terminal sending the access request is a normal terminal. If the scoring score of the access request is less than the second preset score, it means that the access request does not meet the interactive judgment standard, so it is judged that the terminal sending the access request is a malicious attack terminal. If the scoring score of the access request is less than the first preset score but greater than or equal to the second preset score, it means that the interactive behavior of the access request is suspicious, and therefore it is determined that the terminal sending the access request is a suspicious terminal.

[0154] In the above steps S2a441 to S2a446, the bonus score, deduction score, first frequency and second frequency can be set according to actual business needs. In this embodiment, the bonus score is 1, the deduction score is 2, and the first frequency and the second frequency are both 5 times / second. Then set the initial score of the access request, and set the score to zero. If the user behavior data has mouse click information, the score is increased by 1. If the mouse click frequency is greater than 5 times per second, the score is reduced by 2 points; if there is mouse movement information, the score is increased by 1; if there is touch screen operation information, the score is increased by 1, if the screen click rate is greater than 5 times per second, the score is reduced by 2; if there is keyboard input information, the score is increased by 1. In this way, the score of the access request is finally obtained.

[0155] In the above step S3a, different processing methods are adopted for different terminal IDs. After the observation time period ends, the access request of the normal terminal received during the observation time period is immediately forwarded to the server, so that the normal terminal can access the server normally and quickly; the access request sent by the suspicious terminal received during the observation time period is delayed and forwarded to the server. The delayed forwarding time can be set in advance according to the actual situation, so that the suspicious terminal can access the server after the normal terminal accesses the server; finally, the access request sent by the malicious attack terminal received during the observation time period is discarded, and the access request of the malicious attack terminal is rejected, so that the attack access request is intercepted before the automated attack reaches the server, so as to achieve effective and timely protection against short-term, high-frequency and multi-source automated attacks.

[0156] Please refer to Figure 2 , Figure 2 The module diagram of the defense method for effectively protecting against automated attacks of the present invention is shown in FIG. Corresponding to the embodiment of the defense method for effectively protecting against automated attacks of the present invention, the present invention also provides a defense device for effectively protecting against automated attacks, including:

[0157] An acquisition module 1 is used to acquire a preset observation time period;

[0158] Receiving module 2, for receiving, for each observation time period, an access request sent to the server during the observation time period, and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal;

[0159] Processing module 3 is used to discard the access request sent by the malicious attack terminal during the observation time period after the observation time period ends if it is a malicious attack terminal; if it is a normal terminal, forward the access request sent by the normal terminal during the observation time period to the server after the observation time period ends.

[0160] The defense device for effectively protecting against automated attacks of the present invention is deployed at the front end of the server, and is used for proxying the access request of the terminal, and forwarding and processing the access request sent by the terminal and the request response of the server.

[0161] Furthermore, the receiving module 2 includes:

[0162] A first acquisition submodule, configured to acquire, for each access request, relevant information of the access request, wherein the relevant information at least includes a terminal ID of a terminal sending the access request;

[0163] A statistics submodule, used to count the access requests received during the observation time period according to the terminal ID, and obtain the number of access requests sent by each terminal during the observation time period;

[0164] The first judgment submodule is used to judge, for each terminal, whether the number of requests of the terminal is greater than a preset malicious request threshold;

[0165] A second judgment submodule, used to judge that the terminal is a malicious attack terminal if the first judgment submodule judges that the terminal is a malicious attack terminal;

[0166] The third judgment submodule is used to judge whether the terminal is a normal terminal if the first judgment submodule judges that the terminal is a normal terminal.

[0167] Furthermore, the relevant information also includes the access object of the access request; the statistical submodule includes:

[0168] The statistical unit is used to count the access requests received during the observation time period according to the terminal ID and the access object, and obtain the number of access requests sent by each terminal to the access object during the observation time period.

[0169] Furthermore, the receiving module 2 includes:

[0170] A second acquisition submodule is used to acquire relevant information of the access request for each access request, where the relevant information includes non-interaction data or at least one user behavior data, where the user behavior data is one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information;

[0171] A fourth determination submodule, configured to determine, for each access request, whether the relevant information of the access request is non-interaction data;

[0172] a fifth judgment submodule, configured to judge that the terminal sending the access request is a malicious attack terminal if the fourth judgment submodule judges that the terminal is yes;

[0173] The sixth judgment submodule is used to judge whether the terminal sending the access request is a normal terminal if the fourth judgment submodule judges that the terminal is not a normal terminal.

[0174] Furthermore, the receiving module 2 includes:

[0175] A receiving submodule, used to receive an access request sent to the server during an observation time period, and determine whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal;

[0176] Processing module 3 includes:

[0177] The processing submodule is used to discard the access request sent by the malicious attack terminal during the observation time period after the observation time period ends if it is a malicious attack terminal; delay forwarding the access request sent by the suspicious terminal during the observation time period to the server after the observation time period ends if it is a suspicious terminal; and immediately forwarding the access request sent by the normal terminal during the observation time period to the server after the observation time period ends if it is a normal terminal.

[0178] Furthermore, the receiving submodule includes:

[0179] A first acquisition unit, configured to acquire, for each access request, relevant information of the access request, wherein the relevant information at least includes a terminal ID of a terminal sending the access request;

[0180] A first statistical unit, configured to count access requests received during an observation time period according to terminal IDs, and obtain a request count of access requests sent by each terminal during the observation time period;

[0181] A first judging unit, configured to judge, for each terminal, whether the number of requests of the terminal is greater than a preset malicious request threshold;

[0182] A second judgment unit, configured to judge that the terminal is a malicious attack terminal if the number of requests is greater than a malicious request threshold;

[0183] A third judgment unit is used to judge whether the number of requests of the terminal is greater than a preset suspicious request threshold if it is less than or equal to the malicious request threshold;

[0184] A fourth judgment unit, configured to judge the terminal as a suspicious terminal if the request value is greater than a suspicious request threshold;

[0185] The fifth judgment unit is used to judge whether the terminal is a normal terminal if the value is less than or equal to the suspicious request threshold.

[0186] Furthermore, the receiving submodule includes:

[0187] A second acquisition unit is used to acquire, for each access request, relevant information of the access request, where the relevant information includes non-interaction data or at least one user behavior data, where the user behavior data is one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information;

[0188] A sixth judgment unit, configured to judge, for each access request, whether the relevant information of the access request is non-interaction data;

[0189] a seventh judgment unit, configured to judge that the terminal sending the access request is a malicious attack terminal if there is no interactive data;

[0190] The second statistical module is used to count the data quantity of the user behavior data if it is not non-interaction data, and determine whether the data quantity is greater than or equal to a preset data threshold;

[0191] An eighth judgment unit, configured to judge that the terminal sending the access request is a suspicious terminal if the value is less than the data threshold;

[0192] The ninth judgment unit is used to judge whether the terminal sending the access request is a normal terminal if the value is greater than or equal to the data threshold.

[0193] Furthermore, the receiving submodule includes:

[0194] a third acquisition unit, configured to acquire, for each access request, relevant information of the access request, the relevant information including a terminal ID of a terminal sending the access request, and the relevant information also including non-interaction data or at least one user behavior data, the user behavior data being one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information;

[0195] A third statistical unit, configured to count the access requests received during the observation time period according to the terminal ID, and obtain the number of access requests sent by each terminal during the observation time period;

[0196] a tenth judgment unit, configured to judge, for each terminal, whether the number of requests of the terminal is greater than a preset malicious request threshold;

[0197] A first marking unit, configured to mark the terminal as malicious if the number of requests is greater than a malicious request threshold;

[0198] an eleventh judging unit, configured to judge whether the number of requests of the terminal is greater than a preset suspicious request threshold if the number is less than or equal to the malicious request threshold;

[0199] A second marking unit, configured to mark the terminal as suspicious if the request value is greater than a suspicious request threshold;

[0200] A third marking unit, configured to mark the terminal as normal if the number of suspicious requests is less than or equal to the suspicious request threshold;

[0201] a twelfth determination unit, configured to determine, for each access request, whether the relevant information of the access request is non-interaction data;

[0202] A fourth marking unit, configured to mark the terminal sending the access request as malicious if there is no interactive data;

[0203] A fourth statistical unit, for counting the data quantity of the user behavior data if it is not non-interaction data, and determining whether the data quantity is greater than or equal to a preset data threshold;

[0204] A fifth marking unit, configured to mark the terminal sending the access request as suspicious if the value is less than the data threshold;

[0205] The sixth marking unit is used to mark the terminal sending the access request as normal if the data value is greater than or equal to the data threshold.

[0206] The thirteenth judging unit is used to judge a terminal with a malicious mark as a malicious attack terminal, judge a terminal with two normal marks as a normal terminal, and judge the remaining terminals as suspicious terminals.

[0207] Furthermore, the receiving submodule includes:

[0208] a fourth acquisition unit, configured to acquire, for each access request, relevant information of the access request, the relevant information including non-interaction data or at least one user behavior data, the user behavior data being one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information, the mouse click information at least including a mouse click frequency, and the touch screen operation information including a screen click frequency;

[0209] A fourteenth judging unit, configured to judge, for each access request, whether the relevant information of the access request is non-interactive data;

[0210] A fifteenth judging unit, configured to judge that the terminal sending the access request is a malicious attack terminal if there is no interactive data;

[0211] A sixteenth judgment unit, configured to score the access request according to a preset scoring rule if the access request is not non-interaction data, obtain a scoring score of the access request, and judge whether the scoring score is greater than or equal to a first preset score;

[0212] A seventeenth judging unit, configured to judge whether the terminal sending the access request is a normal attack terminal or a normal terminal if the score is greater than or equal to a first preset score;

[0213] An eighteenth judging unit, configured to judge whether the scoring score is greater than or equal to a second preset score if the scoring score is less than the first preset score;

[0214] A nineteenth judging unit, configured to judge that the terminal sending the access request is a suspicious terminal if the score is greater than or equal to a second preset score;

[0215] A twentieth judging unit, configured to judge that the terminal sending the access request is a malicious attack terminal if the score is less than a second preset score;

[0216] Wherein, the sixteenth judgment unit includes:

[0217] A setting subunit, used to set the initial scoring score of the access request to zero;

[0218] A first judgment subunit is used to judge whether the mouse click information is included. If the mouse click information is included, the score is added with a preset bonus score to obtain a new score, and to judge whether the mouse click frequency is greater than a preset first frequency;

[0219] A first calculation subunit is used for, if the mouse click frequency is greater than a preset first frequency, subtracting a preset deduction score from the scoring score to obtain a new scoring score;

[0220] The second judgment subunit is used to judge whether the mouse movement information is included. If the mouse movement information is included, the score is added with a preset bonus score to obtain a new score;

[0221] The third judgment subunit is used to judge whether the touch screen operation information is included. If the touch screen operation information is included, the score is added with the preset bonus score to obtain a new score, and the screen click frequency is greater than the preset second frequency.

[0222] A second calculation subunit is used for, if the screen click frequency is greater than a preset second frequency, subtracting a preset deduction score from the scoring score to obtain a new scoring score;

[0223] The fourth judgment subunit is used to judge whether keyboard input information is included. If touch screen operation information is included, the score is added with a preset bonus score to obtain a new score.

[0224] The implementation process of the functions and effects of each module, sub-module, unit and sub-unit in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, and will not be repeated here.

[0225] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to the partial description of the method embodiments. The system embodiments described above are only illustrative, in which the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units.

[0226] Please refer to Figure 3 , Figure 3A schematic block diagram of the structure of an embodiment of an electronic device of the present invention. Corresponding to the embodiment of the above-mentioned defense method for effectively protecting against automated attacks, an embodiment of the present invention further proposes an electronic device 1001, including a storage 1003 and a processor 1002, the storage 1003 stores a computer program 1004, and the processor 1002 implements any of the above-mentioned steps of the defense method for effectively protecting against automated attacks when executing the computer program 1004, including: S1, obtaining a preset observation time period; S2, for each observation time period, receiving an access request sent to the server during the observation time period, and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal; S3, if it is a malicious attack terminal, then after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period is discarded, and if it is a normal terminal, then after the observation time period ends, the access request sent by the normal terminal received during the observation time period is forwarded to the server.

[0227] Please refer to Figure 4 , Figure 4 The structure schematic diagram of an embodiment of a computer-readable storage medium of the present invention. Corresponding to the embodiment of the above-mentioned defense method for effectively protecting against automated attacks, an embodiment of the present invention further provides a computer-readable storage medium 2001, on which a computer program 1004 is stored. When the computer program 1004 is executed by the processor 1002, the steps of implementing any of the above-mentioned defense methods for effectively protecting against automated attacks include: S1, obtaining a preset observation time period; S2, for each observation time period, receiving an access request sent to the server during the observation time period, and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal; S3, if it is a malicious attack terminal, then after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period is discarded, and if it is a normal terminal, then after the observation time period ends, the access request sent by the normal terminal received during the observation time period is forwarded to the server.

[0228] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to storage, storage, database or other media provided in this application and used in the embodiments may include non-volatile and / or volatile storage. Non-volatile storage may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile storage may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (SSRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct RAMbus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0229] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, device, article or method 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, device, article or method. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, device, article or method including the element.

[0230] The present invention is not limited to the above-mentioned embodiments. If various changes or modifications to the present invention do not depart from the spirit and scope of the present invention, and if these changes and modifications fall within the scope of the claims and equivalent technologies of the present invention, the present invention is also intended to include these changes and modifications.

Claims

1. A defense method for effectively protecting against automated attacks, characterized in that: The following steps are involved: Get the preset observation time period; For each of the observation time periods, receiving an access request sent to the server during the observation time period, and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal; If it is a malicious attack terminal, then after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period will be discarded; if it is a normal terminal, then after the observation time period ends, the access request sent by the normal terminal received during the observation time period will be forwarded to the server.

2. The method for effectively protecting against automated attacks according to claim 1, characterized in that: The step of receiving the access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal comprises: For each of the access requests, obtaining relevant information of the access request, the relevant information at least including a terminal ID of a terminal sending the access request; Counting the access requests received during the observation time period according to the terminal ID to obtain the number of access requests sent by each terminal during the observation time period; For each terminal, determining whether the number of requests from the terminal is greater than a preset malicious request threshold; If yes, it is determined that the terminal is a malicious attack terminal; If not, it is determined that the terminal is a normal terminal.

3. The defense method for effectively protecting against automated attacks according to claim 1, characterized in that: The step of receiving the access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal comprises: For each of the access requests, obtain relevant information of the access request, the relevant information including non-interaction data or at least one user behavior data, the user behavior data being one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information; For each of the access requests, determining whether the relevant information of the access request is non-interaction data; If yes, it is determined that the terminal sending the access request is a malicious attack terminal; If not, it is determined that the terminal sending the access request is a normal terminal.

4. The method for effectively protecting against automated attacks according to claim 1, characterized in that: The step of receiving the access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal or a normal terminal comprises: receiving an access request sent to the server during the observation time period, and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal, or a normal terminal; If the terminal is a malicious attack terminal, after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period is discarded, and if the terminal is a normal terminal, after the observation time period ends, the access request sent by the normal terminal received during the observation time period is forwarded to the server, the step includes: If it is a malicious attack terminal, then after the observation time period ends, the access request sent by the malicious attack terminal received during the observation time period will be discarded; if it is a suspicious terminal, then after the observation time period ends, the access request sent by the suspicious terminal received during the observation time period will be delayed and forwarded to the server; if it is a normal terminal, then after the observation time period ends, the access request sent by the normal terminal received during the observation time period will be immediately forwarded to the server.

5. The method for effectively protecting against automated attacks according to claim 4, characterized in that: The step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal comprises: For each of the access requests, obtaining relevant information of the access request, the relevant information at least including a terminal ID of a terminal sending the access request; Counting the access requests received during the observation time period according to the terminal ID to obtain the number of access requests sent by each terminal during the observation time period; For each terminal, determining whether the number of requests from the terminal is greater than a preset malicious request threshold; If it is greater than the malicious request threshold, the terminal is judged to be a malicious attack terminal; If it is less than or equal to the malicious request threshold, determining whether the number of requests from the terminal is greater than a preset suspicious request threshold; If it is greater than the suspicious request threshold, the terminal is judged to be a suspicious terminal; If it is less than or equal to the suspicious request threshold, it is determined that the terminal is a normal terminal.

6. The method for effectively protecting against automated attacks according to claim 4, characterized in that: The step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal comprises: For each of the access requests, obtain relevant information of the access request, the relevant information including non-interaction data or at least one user behavior data, the user behavior data being one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information; For each of the access requests, determining whether the relevant information of the access request is non-interaction data; If there is no interactive data, it is determined that the terminal sending the access request is a malicious attack terminal; If it is not non-interaction data, then count the amount of user behavior data to determine whether the amount of data is greater than or equal to a preset data threshold; If it is less than the data threshold, it is determined that the terminal sending the access request is a suspicious terminal; If it is greater than or equal to the data threshold, it is determined that the terminal sending the access request is a normal terminal.

7. The method for effectively protecting against automated attacks according to claim 4, characterized in that: The step of receiving an access request sent to the server during the observation time period and determining whether the terminal sending the access request is a malicious attack terminal, a suspicious terminal or a normal terminal comprises: For each of the access requests, obtaining relevant information of the access request, the relevant information including non-interaction data or at least one user behavior data, the user behavior data being one of mouse click information, mouse movement information, touch screen operation information, and keyboard input information, the mouse click information at least including mouse click frequency, and the touch screen operation information including screen click frequency; For each of the access requests, determining whether the relevant information of the access request is non-interaction data; If there is no interactive data, it is determined that the terminal sending the access request is a malicious attack terminal; If it is not non-interaction data, scoring the access request according to a preset scoring rule to obtain a scoring score of the access request, and determining whether the scoring score is greater than or equal to a first preset score; If the score is greater than or equal to a first preset score, it is determined that the terminal sending the access request is a normal terminal; If it is less than the first preset score, determining whether the scoring score is greater than or equal to a second preset score; If the score is greater than or equal to a second preset score, the terminal sending the access request is determined to be a suspicious terminal; If it is less than a second preset score, it is determined that the terminal sending the access request is a malicious attack terminal; The step of scoring the access request according to a preset scoring rule includes: Setting the initial scoring score of the access request to zero; Determine whether the mouse click information is included, if the mouse click information is included, add a preset bonus score to the score to obtain a new score, and determine whether the mouse click frequency is greater than a preset first frequency; If the mouse click frequency is greater than a preset first frequency, subtract a preset deduction score from the scoring score to obtain a new scoring score; Determine whether the mouse movement information is included, and if the mouse movement information is included, add a preset bonus score to the score to obtain a new score; Determine whether the touch screen operation information is included. If the touch screen operation information is included, add the preset bonus score to the score to obtain a new score, and determine whether the screen click frequency is greater than a preset second frequency; If the screen click frequency is greater than a preset second frequency, subtracting a preset deduction score from the scoring score to obtain a new scoring score; Determine whether the keyboard input information is included. If the touch screen operation information is included, add a preset bonus score to the score to obtain a new score.

8. A defense device for effectively protecting against automated attacks, characterized in that: include: An acquisition module, used to acquire a preset observation time period; A receiving module, configured to receive, for each observation time period, an access request sent to the server during the observation time period, and determine whether the terminal sending the access request is a malicious attack terminal or a normal terminal; The processing module is used to discard the access request sent by the malicious attack terminal during the observation time period after the observation time period ends if it is a malicious attack terminal, and forward the access request sent by the normal terminal during the observation time period to the server after the observation time period ends if it is a normal terminal.

9. An electronic device comprising a storage device and a processor, wherein the storage device stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

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