A CC attack protection method based on custom interception identification

Through the CC attack protection method of custom interception identification, the problem of CC protection in the prior art is solved, and the problem of CC protection is easily bypassed and false alarms is achieved, which is higher interception accuracy and flexibility, and is suitable for CC protection of various business systems.

CN115361179BActive Publication Date: 2024-11-05四川启睿克科技有限公司
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210935744.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-08-04
Publication Date
2024-11-05
Estimated Expiration
2042-08-04

AI Technical Summary

Technical Problem

The existing CC protection strategy is easily bypassed by attackers through virtual IP pools, resulting in missed or false alarms. The request path is simply used as the defense standard to distinguish the normal access frequency of different services.

Method used

Using a CC attack protection method with custom interception identifiers, determine the interception identifier fields required by the service, generate interception identifiers and set the access frequency, compare them with the preset interception identifiers according to the user request parameters, and perform protection processing if the rules are met. .

Benefits of technology

It improves the interception accuracy and flexibility of CC protection, reduces false alarms and missed reports, and is suitable for CC protection scenarios of various business systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115361179B_ABST
    Figure CN115361179B_ABST
Patent Text Reader

Abstract

The present invention discloses a CC attack protection method based on a custom interception identifier, including: in the interception rule formulation stage, determining the interception identifier field to be used by the business; recording the corresponding relationship between the selected interception identifier field and the business to form an interception identifier field table; generating an interception identifier; determining the interception frequency; in the CC protection stage, after receiving a user request, querying the corresponding relationship to obtain the interception identifier field table of the business, and sequentially extracting the values ​​of the corresponding parameters of the interception field from the user request; according to the extracted user request parameter value and the interception field name, generating a user request identifier in accordance with the interception rule formulation stage, and comparing the user request identifier with the interception identifier saved by the business; if the comparison result is consistent, it indicates that the request meets the preset interception rule and should be protected, otherwise it is released. The present invention implements CC attack protection by using a custom interception identifier, and the custom interception identifier greatly improves the interception accuracy and flexibility of CC protection.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of front-end information processing, and in particular to a CC attack protection method based on a custom interception identifier. Background Art

[0002] CC (Challenge Collapsar) attack is a type of DDoS (Distributed Denial of Service) and a common website attack method. Its principle is that the attacker controls certain hosts to continuously send data packets to the other server, causing the server resources to be exhausted until it crashes. This attack does not see false IPs or particularly large abnormal traffic. Moreover, the threshold for implementing this technology is relatively low. As long as the right tools and some IP proxies are used, a beginner or intermediate computer user can implement this attack. Therefore, it is very threatening.

[0003] CC attacks are mainly used to attack web pages or web services. Everyone has had this experience: when a web page is visited by a large number of people, the web page opens slowly. CC simulates multiple users constantly accessing pages that require large amounts of data operations, resulting in a waste of server resources. The CPU is at 100% for a long time, and there are always connections that cannot be processed until network congestion occurs, and normal access is terminated.

[0004] The inventor of this application found that the prior art has at least the following technical problems:

[0005] 1. Currently, most mainstream CC protection strategies are implemented by limiting the access frequency of a single IP or a single application. Simply using the access frequency of a single IP as a protection dimension can be easily bypassed by attackers using a virtual IP pool, resulting in missed reports.

[0006] 2. If the access frequency of a single path is limited, due to the complexity of the business system, a single path may be divided into different businesses according to different request methods and request parameters, and the normal access frequencies of different businesses themselves may be different. Simply using the request path as the defense standard cannot distinguish different businesses under the path, which may cause false positives or false negatives of CC attacks. Summary of the invention

[0007] The purpose of the present invention is to provide a CC attack protection method based on a custom interception identifier. This solution adopts a custom CC attack interception identifier to solve the problem that traditional CC attack protection solutions are prone to false positives and false negatives.

[0008] In order to achieve the above object, the present invention adopts the following technical solutions:

[0009] A CC attack protection method based on a custom interception identifier, comprising:

[0010] The interception rule formulation phase includes the following steps:

[0011] Determine the intercept identification field to be used by the business;

[0012] Record the corresponding relationship between the selected interception identification field and the service to form an interception identification field table;

[0013] Generate an interception mark;

[0014] Determine interception frequency;

[0015] The CC protection phase includes the following steps:

[0016] After receiving the user request, query the corresponding relationship to obtain the interception identification field table of the service, and extract the values ​​of the corresponding parameters of the interception fields from the user request in sequence;

[0017] According to the extracted user request parameter value and interception field name, a user request identifier is generated according to the interception rule formulation stage, and the user request identifier is compared with the interception identifier saved by the business;

[0018] If the comparison results are consistent, it indicates that the request meets the preset interception rules and should be protected, otherwise it should be released.

[0019] In some embodiments, the determination of the interception identification field to be used by the service includes: field content contained in the http access request header, request line or request body of the service.

[0020] In some embodiments, the generation of the interception identifier includes: according to the selected one or more interception fields, merging all selected field names and field values ​​in a one-to-one correspondence between field names and field values, and generating and saving a unique interception identifier ID, which will be used as an identifier for subsequent judgment of CC attacks.

[0021] In some embodiments, determining the interception frequency includes: setting a maximum access frequency within a period of time under normal circumstances for the business.

[0022] In some embodiments, if the comparison results are consistent, it indicates that the request meets the preset interception rules and protection processing should be performed; including: if the comparison results are consistent, it indicates that the request meets the interception rules of CC protection and protection processing should be performed, specifically: determine whether the number of accesses counted under the interception identifier exceeds the maximum access frequency preset by the business within the time window. If it exceeds, directly intercept the request; if it does not exceed, add 1 to the number of accesses corresponding to the identifier.

[0023] The CC attack protection method based on a custom interception identifier provided in this application has beneficial effects including but not limited to:

[0024] The present invention realizes CC attack protection by means of user-defined interception identifiers. The customized interception identifiers greatly improve the interception accuracy and flexibility of CC protection, can be configured in various business systems, and can be applied to most application scenarios requiring CC protection. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 The following is a flow chart of the CC attack protection solution based on custom interception identifiers. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be described in more detail below in conjunction with the drawings in the preferred embodiments of the present application. In the drawings, the same or similar reference numerals throughout represent the same or similar parts or parts with the same or similar functions. The described embodiments are part of the embodiments of the present application, not all of the embodiments. The embodiments described below with reference to the drawings are exemplary and are intended to be used to explain the present application, and should not be construed as limitations on the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0027] The following will be combined Figure 1 , a CC attack protection method based on a custom interception identifier involved in an embodiment of the present application is described in detail. It is worth noting that the following embodiments are only used to explain the present application and do not constitute a limitation on the present application.

[0028] Embodiment 1:

[0029] The present invention provides a CC attack defense method based on a custom interception identifier to accurately identify CC attacks and achieve effective protection for Web servers. This solution includes an interception rule formulation phase and a CC protection phase; in the interception identifier generation phase, a customized interception identifier is generated based on the normal access frequency of different business scenarios and the characteristics of the access request, and the interception identifier and the maximum access frequency together constitute the CC protection rules of the business; in the CC protection phase, when the business receives a request, the corresponding fields in the user request are extracted according to the fields contained in the custom interception identifier, and the identifier is generated in the same way, and compared with the interception identifier of the business, and whether to perform protection processing is determined based on the comparison result. This solution can effectively improve the interception precision and accuracy, and reduce false positives and false negatives.

[0030] like Figure 1A CC attack protection method based on a custom interception identifier is shown, comprising:

[0031] The interception rule formulation phase includes the following steps:

[0032] Determine the intercept identification field to be used by the business;

[0033] Record the corresponding relationship between the selected interception identification field and the service to form an interception identification field table;

[0034] Generate an interception mark;

[0035] Determine interception frequency;

[0036] The CC protection phase includes the following steps:

[0037] After receiving the user request, query the corresponding relationship to obtain the interception identification field table of the service, and extract the values ​​of the corresponding parameters of the interception fields from the user request in sequence;

[0038] According to the extracted user request parameter value and interception field name, a user request identifier is generated according to the interception rule formulation stage, and the user request identifier is compared with the interception identifier saved by the business;

[0039] If the comparison results are consistent, it indicates that the request meets the preset interception rules and should be protected, otherwise it should be released.

[0040] Embodiment 2:

[0041] Step 1: Before the client request reaches the business service, configure a proxy server in front of the business server for CC attack detection;

[0042] Step 2: Configure the interception identification field for the business service based on the site hosts on the proxy server. The field options include the client IP address client_ip, user request User-agent, user requested hosts address, requested URL path, special parameter values ​​contained in the request, etc.

[0043] Step 3: Generate an interception identifier using the selected fields and preset values; for example, if the preset interception identifier field is: hosts = www.baidu.com & user-agent = xxxxxx & client_ip = 12.2.11.4, that is, only when the IP, UA, and hosts are the same as the preset values, the access frequency of such client requests is counted; the above interception identifier string is hashed as a custom interception identifier for the service;

[0044] Step 4: When a user request arrives, the CC detection module first finds the interception identification field list corresponding to the request according to the hosts of the request, extracts the values ​​of the fields in the field list from the user request and arranges them in the same order. For example, if the interception identification field contains hosts, ua, and client_ip, then the values ​​corresponding to the above fields are found from the user request and arranged in the order of generation of the interception identification as follows: hosts = www.xxx.com & user-agent = xxxxxx & client_ip = 11.4.33.5, and the field is also hashed;

[0045] Step 5: Compare the obtained new identifier with the preset intercept identifier. If the two are consistent, it indicates that CC attack protection is required for the request. It is determined whether the request has reached the preset access frequency value and processed. If the comparison results are inconsistent, the request is directly released.

[0046] The specific implementation method of this solution is not limited to the one given in this example. The selection of the interception identification field can be replaced by any other request field that can meet business requirements.

[0047] This solution uses preset interception identifiers to classify user requests into those that meet the identifiers and those that do not meet the identifiers, and intercepts access behaviors that meet the classification. If the user generates an interception identifier based on the attacker's access characteristics such as the request method, request UA, or special parameter values, targeted interception can be performed accurately. If there are different businesses with the same request URL, different interception identifiers can be formulated based on the request parameters and request methods to distinguish different businesses and configure their respective interception frequencies, so as to achieve more accurate CC protection rule configuration for the business; compared with traditional CC protection methods, this solution has higher interception accuracy and fewer false alarms.

[0048] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. 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 present invention.

Claims

1. A CC attack protection method based on custom interception identification, It is characterized in that include: The interception rule formulation phase includes the following steps: Determine the intercept identification field to be used by the business; Record the corresponding relationship between the selected interception identification field and the service to form an interception identification field table; Generate an interception mark; Determine interception frequency; The CC protection phase includes the following steps: After receiving the user request, query the corresponding relationship to obtain the interception identification field table of the service, and extract the values ​​of the corresponding parameters of the interception field from the user request in sequence; According to the extracted user request parameter value and interception field name, a user request identifier is generated according to the interception rule formulation stage, and the user request identifier is compared with the interception identifier saved by the business; If the comparison results are consistent, it means that the request meets the preset interception rules and should be protected, otherwise it should be released; The generating of the interception identification includes: according to the selected one or more interception fields, merging all the selected field names and field values ​​in a one-to-one correspondence between the field names and the field values, and generating and saving a unique interception identification ID, which will be used as an identification for subsequent determination of CC attacks; If the comparison results are consistent, it indicates that the request meets the preset interception rules and protection processing should be performed; including: if the comparison results are consistent, it indicates that the request meets the interception rules of CC protection and protection processing should be performed, specifically: determine whether the number of accesses counted under the interception identifier exceeds the maximum access frequency preset by the business within the time window. If it exceeds, directly intercept the request; if it does not exceed, add 1 to the number of accesses corresponding to the identifier.

2. According to claim 1, a CC attack protection method based on a custom interception identifier, It is characterized in that The interception identification field to be used by the business is determined, including: the field content contained in the http access request header, request line or request body of the business.

3. According to claim 1, a CC attack protection method based on a custom interception identifier, It is characterized in that Determining the interception frequency includes: setting a maximum access frequency within a period of time under normal circumstances for the business.