Botnet domain name determination method and apparatus, and electronic device

By constructing a network relationship diagram and community discovery algorithm and analyzing community structure information, the problem of low accuracy in botnet domain name determination in the existing technology is solved, achieving higher accuracy and lower risk of false positives.

CN119030759AActive Publication Date: 2024-11-26HILLSTONE NETWORKS CO LTD +1
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202411066743.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-02
Publication Date
2024-11-26
Estimated Expiration
2044-08-02

AI Technical Summary

Technical Problem

In the prior art, the target domain name is determined by calculating the similarity between the target domain name and the historical botnet domain name, resulting in a low accuracy of determining the botnet domain name.

Method used

By constructing a target network relationship map, using the community discovery algorithm to divide the community, analyze the community structure information, and determine the target botnet domain name. The specific steps include: obtaining the target DNS data, building a network relationship diagram, dividing the community, filtering the community structure information, calculating the ratio of the domain name and IP node, judging the consistency of the registered domain name, performing similarity calculations, and finally determining the target botnet domain name.

Benefits of technology

It improves the accuracy of botnet domain names, reduces the risk of false positives, and avoids the problem of low accuracy due to the lack of domain name similarity in traditional methods.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119030759A_ABST
    Figure CN119030759A_ABST
Patent Text Reader

Abstract

The invention discloses a botnet domain name determination method and device and electronic equipment. Relates to the technical field of data processing, the field of network security and other related technical fields, and comprises the following steps: constructing a target network relation graph according to target DNS data; performing community division on the target network relation graph according to a community discovery algorithm to obtain multiple pieces of community structure information; and determining a target botnet domain name from the target DNS data according to the multiple pieces of community structure information. Through application of the method and the device, the problem that in the related technology, whether the target domain name is the botnet domain name or not is determined by calculating the similarity between the target domain name and the historical botnet domain name, so that the botnet domain name determination accuracy is relatively low is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the fields of data processing technology, network security and other related technical fields, and in particular to a method and device for determining a botnet domain name, and an electronic device. Background Art

[0002] A botnet is a collection of Internet devices controlled by hackers. Botnets are a major threat to network security, and they are used to launch various network attacks such as Distributed Denial of Service (DDos). Therefore, it is of great significance to quickly and accurately discover the command and control server of the botnet, detect the communication behavior in the botnet, and cut off the connection between the controlled device and the botnet control server based on the detection results to ensure network security and reduce the risk of network attacks. The traditional method mainly determines the target botnet domain name based on the difference between the suspected botnet domain name and the historical botnet domain name. This method generally believes that the domain names of the same botnet family have some similarities, so it can be detected by combining statistical features or characterization features with machine learning methods. However, when the domain names of the botnet family do not have similarities, this method is difficult to detect, which leads to a relatively low accuracy rate in determining the botnet domain name.

[0003] Currently, no effective solution has been proposed to solve the problem that the target domain name is determined to be a botnet domain name by calculating the similarity between the target domain name and the historical botnet domain name in the related art, which leads to a relatively low accuracy rate in determining the botnet domain name. Summary of the invention

[0004] The main purpose of the present application is to provide a method and device for determining a botnet domain name, and an electronic device to solve the problem in the related art that the target domain name is determined to be a botnet domain name by calculating the similarity between the target domain name and the historical botnet domain name, resulting in a relatively low accuracy rate in determining the botnet domain name.

[0005] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for determining a botnet domain name is provided. The method comprises: constructing a target network relationship graph based on target DNS data, wherein the target DNS data at least comprises: access domain name information of the target object, IP information of the target object and the access relationship between the IP information and the access domain name information, and the target network relationship graph at least comprises: an IP node corresponding to the IP information and a domain name node corresponding to the access domain name information; performing community division on the target network relationship graph based on a community discovery algorithm to obtain multiple community structure information; and determining the target botnet domain name from the target DNS data based on the multiple community structure information.

[0006] Furthermore, determining the target botnet domain name from the target DNS data based on the multiple community structure information includes: determining an initial botnet from the multiple community structure information based on the number of domain name nodes in each community structure information; and determining the target botnet domain name based on multiple domain names corresponding to the initial botnet.

[0007] Furthermore, according to the number of domain name nodes in each community structure information, determining the initial botnet from the multiple community structure information includes: calculating according to the number of domain name nodes and the number of second-level domain names in each community structure information to obtain a first ratio; calculating according to the number of domain name nodes and the number of multi-level domain names in each community structure information to obtain a second ratio; screening the multiple community structure information according to the number of domain name nodes, the number of edges corresponding to the IP nodes in each community structure information, the first ratio and the second ratio, to obtain the initial botnet.

[0008] Furthermore, determining the target botnet domain name based on the multiple domain names corresponding to the initial botnet includes: judging whether the registered domain names of the multiple domain names corresponding to the initial botnet are the same, and obtaining a judgment result; if the judgment result indicates that the registered domain names of multiple target domain names among the multiple domain names corresponding to the initial botnet are different, similarity calculation is performed on the multiple target domain names to obtain a target similarity; and determining the target botnet domain name from the multiple target domain names based on the target similarity.

[0009] Further, performing similarity calculation on the multiple target domain names to obtain target similarity includes: for a first target domain name and a second target domain name among any two target domain names, performing similarity calculation on a registered domain name of the first target domain name and a multi-level domain name of the second target domain name to obtain a first similarity; performing similarity calculation on the multi-level domain name of the first target domain name and the registered domain name of the second target domain name to obtain a second similarity; and determining the target similarity based on the first similarity and the second similarity.

[0010] Furthermore, before constructing the target network relationship diagram based on the target DNS data, the method also includes: obtaining multiple network access requests triggered by the target object within a historical time period, wherein the multiple network access requests at least include: the IP information and access domain name information of the target object; parsing and processing the multiple network access requests to obtain initial DNS data; and filtering the initial DNS data according to the DNS response type to obtain the target DNS data.

[0011] Furthermore, filtering the initial DNS data according to the DNS response type to obtain the target DNS data includes: filtering the initial DNS data according to the DNS response type to obtain filtered DNS data; calculating, based on the target IP information in the filtered DNS data, a first quantity of DNS data corresponding to the target IP information and a second quantity of network access requests corresponding to the target IP information; filtering the filtered DNS data according to the first quantity and the second quantity to obtain the target DNS data.

[0012] Furthermore, based on the target DNS data, constructing the target network relationship graph includes: determining the domain name node based on the access domain name information of the target object and determining the IP node based on the IP information of the target object; determining the edge based on the access relationship of the IP information to the access domain name information; constructing the target network relationship graph based on the domain name node, the IP node and the edge.

[0013] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a device for determining a botnet domain name is provided. The device comprises: a construction unit, which is used to construct a target network relationship graph based on target DNS data, wherein the target DNS data at least comprises: access domain name information of the target object, IP information of the target object and access relationship of the IP information to the access domain name information, and the target network relationship graph at least comprises: an IP node corresponding to the IP information and a domain name node corresponding to the access domain name information; a division unit, which is used to divide the target network relationship graph into communities based on a community discovery algorithm to obtain multiple community structure information; a determination unit, which is used to determine the target botnet domain name from the target DNS data based on the multiple community structure information.

[0014] Furthermore, the determination unit includes: a first determination module, used to determine the initial botnet from the multiple community structure information according to the number of domain name nodes in each community structure information; a second determination module, used to determine the target botnet domain name according to multiple domain names corresponding to the initial botnet.

[0015] Furthermore, the first determination module includes: a first calculation submodule, used to calculate based on the number of domain name nodes and the number of second-level domain names in each community structure information to obtain a first ratio; a second calculation submodule, used to calculate based on the number of domain name nodes and the number of multi-level domain names in each community structure information to obtain a second ratio; a screening submodule, used to screen the multiple community structure information based on the number of domain name nodes, the number of edges corresponding to the IP nodes in each community structure information, the first ratio and at least one of the second ratio to obtain the initial botnet.

[0016] Furthermore, the second determination module includes: a judgment submodule, used to judge whether the registered domain names of the multiple domain names corresponding to the initial botnet are the same, and obtain a judgment result; a third calculation submodule, used to calculate the similarity of the multiple target domain names to obtain the target similarity if the judgment result indicates that the registered domain names of the multiple target domain names among the multiple domain names corresponding to the initial botnet are different; and a determination submodule, used to determine the target botnet domain name from the multiple target domain names based on the target similarity.

[0017] Furthermore, the third calculation submodule includes: a first calculation submodule, used for performing similarity calculation on the registered domain name of the first target domain name and the multi-level domain name of the second target domain name among any two target domain names to obtain a first similarity; a second calculation submodule, used for performing similarity calculation on the multi-level domain name of the first target domain name and the registered domain name of the second target domain name to obtain a second similarity; and a determination submodule, used for determining the target similarity based on the first similarity and the second similarity.

[0018] Furthermore, the device also includes: an acquisition unit, which is used to acquire multiple network access requests triggered by the target object within a historical time period before constructing a target network relationship diagram based on the target DNS data, wherein the multiple network access requests at least include: IP information and access domain name information of the target object; a parsing unit, which is used to parse and process the multiple network access requests to obtain initial DNS data; and a screening unit, which is used to screen the initial DNS data according to the DNS response type to obtain the target DNS data.

[0019] Furthermore, the screening unit includes: a first screening module, used to screen the initial DNS data according to the DNS response type to obtain screened DNS data; a calculation module, used to calculate a first quantity of DNS data corresponding to the target IP information and a second quantity of network access requests corresponding to the target IP information according to the target IP information in the screened DNS data; and a second screening module, used to screen the screened DNS data according to the first quantity and the second quantity to obtain the target DNS data.

[0020] Furthermore, the construction unit includes: a third determination module, used to determine the domain name node based on the access domain name information of the target object and to determine the IP node based on the IP information of the target object; a fourth determination module, used to determine the edge based on the access relationship of the IP information to the access domain name information; and a construction module, used to construct the target network relationship diagram based on the domain name node, the IP node and the edge.

[0021] To achieve the above objective, according to one aspect of the present application, a computer-readable storage medium is provided, wherein the storage medium stores a program, wherein when the program is executed, the device where the storage medium is located is controlled to execute any one of the above methods for determining a botnet domain name.

[0022] In order to achieve the above-mentioned purpose, according to another aspect of the present application, an electronic device is further provided, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for determining the botnet domain name provided in the aforementioned embodiment.

[0023] Through the present application, the following steps are adopted: constructing a target network relationship graph based on target DNS data, wherein the target DNS data at least includes: access domain name information of the target object, IP information of the target object and access relationship between the IP information and the access domain name information, and the target network relationship graph at least includes: IP nodes corresponding to the IP information and domain name nodes corresponding to the access domain name information; dividing the target network relationship graph into communities based on a community discovery algorithm to obtain multiple community structure information; determining the target botnet domain name from the target DNS data based on the multiple community structure information, and through the present application, the problem of low accuracy in determining the botnet domain name in the related art, which is caused by calculating the similarity between the target domain name and the historical botnet domain name to determine whether the target domain name is a botnet domain name, is solved.

[0024] In this scheme, firstly, a target network relationship graph is established according to the access domain name information, IP information and the access relationship between the IP information and the access domain name information of the target object in the target DNS data; then, the target network relationship graph is divided into communities using a community discovery algorithm to obtain multiple community structure information (for example, multiple community clusters); finally, based on the multiple community structure information, an analysis is performed to obtain the target botnet domain name in the target DNS data.

[0025] By constructing a target network relationship graph, we can accurately analyze the network access behavior of the target object, and use the community discovery algorithm to divide the target network relationship graph into communities, thereby quickly obtaining multiple community clusters. Finally, based on multiple community structure information, we can analyze the target botnet domain name in the target DNS data, further reducing the risk of false positives in the results, and avoiding the problem of low accuracy in determining the botnet domain name in the traditional method of determining the target botnet domain name based on the difference between the suspected botnet domain name and the historical botnet domain name. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0027] Figure 1 is a flow chart of a method for determining a botnet domain name provided in an embodiment of the present application;

[0028] Figure 2 is a schematic diagram of the results of the community discovery algorithm provided according to an embodiment of the present application;

[0029] Figure 3 is a schematic diagram of a target network relationship diagram provided according to an embodiment of the present application;

[0030] Figure 4 is a schematic diagram of a device for determining a botnet domain name according to an embodiment of the present application;

[0031] Figure 5 is a schematic diagram of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0033] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0034] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0035] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. For example, an interface is set between this system and the relevant user or organization. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0036] The present application provides a method for determining a botnet domain name. The method can be performed by a domain name detection system or a security protection system. The system can be implemented by software or a combination of software and hardware.

[0037] The present invention is described below in conjunction with preferred implementation steps. Figure 1 is a flow chart of a method for determining a botnet domain name according to an embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:

[0038] Step S101, constructing a target network relationship diagram based on the target DNS data, wherein the target DNS data at least includes: the access domain name information of the target object, the IP information of the target object and the access relationship between the IP information and the access domain name information, and the target network relationship diagram at least includes: the IP node corresponding to the IP information and the domain name node corresponding to the access domain name information.

[0039] Optionally, according to the IP information (e.g., the source IP address of the target object) and the access domain name information (e.g., the access domain name address of the target object) in the target DNS data, a target network relationship graph is constructed based on the access behavior (i.e., the access relationship between the IP information and the access domain name information), and the target network relationship graph can be an undirected graph network structure.

[0040] Step S102, dividing the target network relationship graph into communities according to a community discovery algorithm to obtain multiple community structure information.

[0041] Optionally, Figure 2 is a schematic diagram of the results of the community discovery algorithm provided in the embodiment of the present application, such as Figure 2 As shown, in the undirected graph network structure constructed by the target DNS data, community division is performed through the community discovery algorithm to obtain multiple community clusters (i.e., multiple community structure information).

[0042] It should be noted that community discovery algorithms include but are not limited to: Louvain, Leiden and other methods and other community discovery algorithms derived from clustering algorithms.

[0043] It should be noted that the Louvain algorithm is a greedy heuristic algorithm based on modularity optimization, which aims to divide the nodes in the network into different communities, making the connections within the community denser and the connections between communities sparser. The algorithm divides the community by optimizing the modularity within the community, and continuously moves the nodes to the community that increases the modularity until it can no longer increase.

[0044] It should be noted that the Leiden algorithm is an algorithm based on the idea of ​​local optimization. It divides network nodes into different communities to maximize the connection strength within the network and minimize the connection strength between communities. Its advantages lie in the efficiency and scalability of the algorithm, and it can handle large networks with millions of nodes and billions of edges. At the same time, its algorithm also has good stability and robustness, and can produce reasonable community division results for different types of networks.

[0045] Step S103, determining the target botnet domain name from the target DNS data according to the plurality of community structure information.

[0046] Optionally, multiple community structure information (e.g., community clusters) are screened by one or more threshold conditions to determine suspected botnet families. Domain name similarity analysis is performed on the suspected botnet families that have passed the threshold conditions, and the suspected botnet families are further screened by calculating the similarity between multiple domain names in the suspected botnet families, and finally the target botnet domain name in the suspected botnet families is determined.

[0047] The one or more threshold conditions include at least one of the following conditions: Screening condition one: the number of edges corresponding to the IP nodes in the community cluster is greater than or equal to the threshold x1; Screening condition two: the ratio of the number of nodes with an edge number of 1 corresponding to the IP nodes in the community cluster to the number of all IP nodes in the community cluster is greater than or equal to the threshold x2; Screening condition three: the number of domain name nodes in the community cluster is greater than or equal to the threshold x3; Screening condition four: the repetition degree k of the second-level domain names in the community cluster is greater than or equal to the threshold x4 (i.e., the first ratio), where k is the ratio of the number of second-level domain names in each community cluster to the number of domain name nodes; Screening condition five: the proportion of the number of multi-level domain names in the community cluster to the number of domain name nodes (i.e., the second ratio) is greater than or equal to the threshold x5.

[0048] In some examples, in order to further improve the accuracy of determining the botnet domain name, a community cluster that meets the above five screening conditions may be determined as an initial botnet, and the botnet domain name may be determined from the initial botnet.

[0049] In summary, first, a target network relationship graph is established based on the target object's access domain name information, IP information, and the access relationship between the IP information and the access domain name information in the target DNS data; then, the target network relationship graph is divided into communities using a community discovery algorithm to obtain multiple community clusters (i.e., community structure information); finally, based on multiple community structure information, the target botnet domain name in the target DNS data is obtained through analysis. By constructing a target network relationship graph, the network access behavior of the target object can be accurately analyzed, and the target network relationship graph can be divided into communities using a community discovery algorithm to quickly obtain multiple community clusters. Finally, based on multiple community structure information, the target botnet domain name in the target DNS data is determined through analysis, which further reduces the risk of false positives in the results and avoids the problem of low accuracy in determining the botnet domain name caused by the traditional method of determining the target botnet domain name based on the difference between the suspected botnet domain name and the historical botnet domain name.

[0050] Optionally, in the method for determining a botnet domain name provided in an embodiment of the present application, determining a target botnet domain name from target DNS data based on multiple community structure information includes: determining an initial botnet from multiple community structure information based on the number of domain name nodes in each community structure information; and determining a target botnet domain name based on multiple domain names corresponding to the initial botnet.

[0051] In an optional embodiment, screening conditions are set according to information such as domain name nodes, IP nodes, and the number of edges corresponding to IP nodes, so as to screen multiple community clusters and obtain a suspected DGA family community cluster (i.e., the initial botnet). The target botnet domain name is determined by calculating the string similarity between subdomain names in the domain name nodes within the suspected DGA family community cluster.

[0052] In some embodiments, the method may further include: determining a botnet domain name family according to a community structure to which the target botnet domain name belongs.

[0053] By screening multiple community clusters, we can accurately locate suspected DGA family community clusters, which in turn helps identify key domain names in botnets, facilitating further investigation and prevention of botnet activities.

[0054] Optionally, in the method for determining the botnet domain name provided in an embodiment of the present application, determining the initial botnet from multiple community structure information based on the number of domain name nodes in each community structure information includes: calculating based on the number of domain name nodes and the number of second-level domain names in each community structure information to obtain a first ratio; calculating based on the number of domain name nodes and the number of multi-level domain names in each community structure information to obtain a second ratio; screening multiple community structure information based on at least one of the number of domain name nodes, the number of edges corresponding to the IP nodes in each community structure information, the first ratio, and the second ratio to obtain the initial botnet.

[0055] In an optional embodiment, the multi-level domain name includes a first-level domain name (top-level domain name) field, a second-level domain name (customer domain name) field, and a third-level domain name (application domain name) field. For example, the first-level domain name is aaa.com, the second-level domain name is bbb.aaa.com, and the third-level domain name is ccc.bbb.aaa.com. The third-level domain name ccc.bbb.aaa.com is considered a multi-level domain name. Here, ccc is a registered domain name.

[0056] In an optional embodiment, multiple screening conditions can be set to screen multiple community clusters to obtain an initial botnet. Among them, screening condition one: the number of edges corresponding to IP nodes in the community cluster is greater than or equal to the threshold x1; screening condition two: the ratio of the number of nodes with an edge number of 1 corresponding to IP nodes in the community cluster to the number of all IP nodes in the community cluster is greater than or equal to the threshold x2; screening condition three: the number of domain name nodes in the community cluster is greater than or equal to the threshold x3; screening condition four: the repetition degree k of the second-level domain names in the community cluster is greater than or equal to the threshold x4 (i.e., the first ratio), where k is the ratio of the number of second-level domain names in each community cluster to the number of domain name nodes; screening condition five: the proportion of the number of multi-level domain names in the community cluster to the number of domain name nodes (i.e., the second ratio) is greater than or equal to the threshold x5. The community cluster that meets the above five screening conditions is determined as a suspected DGA family community cluster (i.e., the initial botnet).

[0057] Here, the edge corresponding to the IP node can be understood as the edge connected to the IP node.

[0058] It should be noted that x1, x2, x3, x4 and x5 in the above screening conditions are not fixed values ​​and can be adjusted dynamically.

[0059] By setting threshold conditions to screen multiple community clusters obtained by the community discovery algorithm, the risk of false positives in the results is effectively reduced.

[0060] Optionally, in the method for determining a botnet domain name provided in an embodiment of the present application, determining a target botnet domain name based on multiple domain names corresponding to an initial botnet includes: determining whether the registered domain names of the multiple domain names corresponding to the initial botnet are the same, and obtaining a determination result; if the determination result indicates that the registered domain names of multiple target domain names among the multiple domain names corresponding to the initial botnet are different, performing similarity calculation on the multiple target domain names to obtain a target similarity; and determining the target botnet domain name from the multiple target domain names based on the target similarity.

[0061] In an optional embodiment, it is possible to determine whether the multiple domain names corresponding to the initial botnet have the same registered domain name, and to perform a preliminary screening of the multiple domain names corresponding to the initial botnet based on the determination result. If the domain names have the same registered domain name, it can be considered that they do not belong to the botnet domain name. For multiple target domain names with different registered domain names, further screening is performed: the target similarity between any two target domain names in the multiple target domain names with respect to the registered domain name is calculated, and the relationship between the target similarity and the preset threshold value y1 is determined: when the target similarity is greater than or equal to the threshold value y1, it is considered that the two target domain names do not belong to the botnet domain name; when the target similarity is less than the threshold value y1, it is considered that the two target domain names belong to the botnet domain name, wherein the threshold value y1 is a non-fixed value and can be adjusted dynamically.

[0062] It should be noted that a dynamic domain name can be regarded as a top-level domain name. For example, in testdomain1.dynu.com, dynu.com can be regarded as a top-level domain name and testdomain1 can be regarded as a registered domain name.

[0063] By determining whether multiple domain names corresponding to the initial botnet have the same registered domain name, some domain names that do not belong to the botnet can be excluded, reducing the workload of subsequent analysis. At the same time, similarity calculations are performed for target domain names with different registered domain names, and the target botnet domain name is determined by determining the relationship between the target similarity and the preset threshold, which helps to improve the accuracy and pertinence of the analysis.

[0064] Optionally, in the method for determining a botnet domain name provided in an embodiment of the present application, performing similarity calculation on multiple target domain names to obtain target similarity includes: for a first target domain name and a second target domain name among any two target domain names, performing similarity calculation on a registered domain name of the first target domain name and a multi-level domain name of the second target domain name to obtain a first similarity; performing similarity calculation on the multi-level domain name of the first target domain name and the registered domain name of the second target domain name to obtain a second similarity; and determining the target similarity based on the first similarity and the second similarity.

[0065] In an optional embodiment, the similarity between the registered domain name string and the high-level subdomain name (i.e., multi-level domain name) string of the first target domain name and the second target domain name in any two target domain names can be calculated by using an edit distance algorithm or a text similarity calculation method to obtain the target similarity.

[0066] It should be noted that the edit distance algorithm is a method used to measure the similarity between two strings, that is, the minimum number of operations required to make the two strings equal by adding, deleting, and replacing them. The smaller the edit distance, the more similar the two strings are. The similarity between strings can be calculated based on the edit distance. Usually, the similarity value can be normalized by dividing the edit distance by the maximum value of the string length so that the similarity value is between 0 and 1.

[0067] By calculating the similarity of multiple target domain names, we can accurately identify domain names representing the same organization or category and discover their potential associations, thereby better identifying potential botnet domain names or other malicious domain names.

[0068] Optionally, in the method for determining a botnet domain name provided in an embodiment of the present application, before constructing a target network relationship diagram based on target DNS data, the method further includes: obtaining multiple network access requests triggered by the target object within a historical time period, wherein the multiple network access requests include at least: IP information and access domain name information of the target object; parsing the multiple network access requests to obtain initial DNS data; and filtering the initial DNS data based on the DNS response type to obtain target DNS data.

[0069] In an optional embodiment, a plurality of network access requests triggered by the target object in a historical time period can be obtained through a network packet capture tool, and parsed to extract the target object's IP information, the target object's access domain name information, and the access time information. Then, the above data is subjected to DNS parsing, and the target object's access domain name information is parsed into a corresponding IP address to obtain initial DNS data, and a DNS response type is returned. Finally, the initial DNS data is filtered by multiple filtering conditions such as the DNS response type to obtain the target DNS data.

[0070] It should be noted that the initial DNS data can also be collected through various DNS data collection methods such as network card traffic collection, DNS access logs, and security device DNS data interfaces.

[0071] It should be noted that the DNS response types include at least: NOERROR, SERVFAIL, NOXDOMAIN and REFUSE. NOERROR indicates a successful response, that is, the domain name resolution is successful; SERVFAIL indicates that the DNS server resolution fails, that is, the DNS server of the domain name refuses to respond or responds to REFUSE; NOXDOMAIN indicates that there is no IP address information corresponding to the domain name, that is, the domain name does not exist in the DNS server; REFUSE indicates that the request source IP is not within the service range.

[0072] The initial DNS data can be accurately obtained through a variety of methods, and the initial DNS data can be filtered through multiple filtering conditions to minimize the redundancy of the data, laying the foundation for the subsequent detection and determination of botnet domain names.

[0073] Optionally, in the method for determining the botnet domain name provided in an embodiment of the present application, the initial DNS data is filtered according to the DNS response type to obtain the target DNS data, including: filtering the initial DNS data according to the DNS response type to obtain the filtered DNS data; based on the target IP information in the filtered DNS data, calculating the first number of DNS data corresponding to the target IP information and the second number of network access requests corresponding to the target IP information; filtering the filtered DNS data according to the first number and the second number to obtain the target DNS data.

[0074] In an optional embodiment, multiple screening conditions can be set to screen the initial DNS data to obtain the target DNS data. Among them, screening condition one: the DNS response type is a preset response type (for example, NOXDOMAIN); screening condition two: within a fixed-length sliding time window, the number of DNS response types corresponding to a target IP information that are preset response types (i.e., the first number of DNS data corresponding to the target IP information) is greater than or equal to y1% of the total number (i.e., the second number of network access requests corresponding to the target IP information); screening condition three: within a fixed-length sliding time window, the number of DNS response types corresponding to a target IP information that are preset response types is greater than or equal to a threshold value y2 (i.e., the first number of DNS data corresponding to the target IP information). The initial DNS data is preliminarily screened by screening condition one to obtain the screened DNS data. The screened DNS data is screened again according to screening conditions two and three to obtain the target DNS data.

[0075] It should be noted that the threshold y1 and the threshold y2 in the above screening conditions are not fixed values ​​and can be adjusted dynamically.

[0076] Through the above screening conditions, the initial DNS data can be filtered step by step, reducing the redundancy of the initial DNS data, and then quickly obtaining the target DNS data that meets the conditions, and helping to identify potential abnormal or malicious DNS requests for further analysis and processing.

[0077] Optionally, in the method for determining the botnet domain name provided in an embodiment of the present application, constructing a target network relationship graph based on target DNS data includes: determining domain name nodes based on access domain name information of the target object and determining IP nodes based on IP information of the target object; determining edges based on the access relationship between IP information and access domain name information; and constructing a target network relationship graph based on domain name nodes, IP nodes and edges.

[0078] In an optional embodiment, Figure 3 is a schematic diagram of a target network relationship diagram provided according to an embodiment of the present application, such as Figure 3 As shown, the domain name detection system builds a target network relationship graph based on the relationship between the source IP address (e.g., the IP information of the target object) and the access domain name address (e.g., the access domain name information of the target object) in the target DNS data, and the network relationship (e.g., the access relationship between the IP information and the access domain name information) based on the access behavior. In the network structure, there are two types of nodes, the first type is the IP node, and the second type is the domain name node. The edge attribute between the IP node and the domain name node is the number of visits.

[0079] By constructing a target network relationship diagram, the correspondence between the target object's domain name information and IP information can be clearly displayed, which helps to analyze network traffic and identify potential malicious activities and botnet domain names.

[0080] The method for determining a botnet domain name provided in an embodiment of the present application constructs a target network relationship graph based on target DNS data, wherein the target DNS data at least includes: access domain name information of a target object, IP information of the target object, and an access relationship between the IP information and the access domain name information, and the target network relationship graph at least includes: an IP node corresponding to the IP information and a domain name node corresponding to the access domain name information; the target network relationship graph is divided into communities based on a community discovery algorithm to obtain multiple community structure information; and the target botnet domain name is determined from the target DNS data based on the multiple community structure information, thereby solving the problem in the related art that whether a target domain name is a botnet domain name is determined by calculating the similarity between the target domain name and the historical botnet domain name, resulting in a relatively low accuracy rate in determining the botnet domain name.

[0081] To summarize, in this scheme, firstly, a target network relationship graph is established according to the access domain name information, IP information of the target object in the target DNS data, and the access relationship between the IP information and the access domain name information; then, the target network relationship graph is divided into communities using a community discovery algorithm to obtain multiple community structure information (for example, multiple community clusters); finally, based on multiple community structure information, analysis is performed to obtain the target botnet domain name in the target DNS data.

[0082] By constructing a target network relationship graph, we can accurately analyze the network access behavior of the target object, and use the community discovery algorithm to divide the target network relationship graph into communities, thereby quickly obtaining multiple community clusters. Finally, based on multiple community structure information, we can analyze the target botnet domain name in the target DNS data, further reducing the risk of false positives in the results, and avoiding the problem of low accuracy in determining the botnet domain name in the traditional method of determining the target botnet domain name based on the difference between the suspected botnet domain name and the historical botnet domain name.

[0083] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0084] The embodiments or examples of the present application are not exhaustive, but are only illustrative of some embodiments or examples, and are not intended to be specific limitations on the scope of protection of the present application. In the absence of contradiction, each step in a certain embodiment or example can be implemented as an independent example, and the steps can be combined arbitrarily. For example, the scheme after removing some steps in a certain embodiment or example can also be implemented as an independent example, and the order of the steps in a certain embodiment or example can be arbitrarily exchanged. In addition, the optional methods or optional examples in a certain embodiment or example can be combined arbitrarily; in addition, the various embodiments or examples can be combined arbitrarily, for example, some or all steps of different embodiments or examples can be combined arbitrarily, and a certain embodiment or example can be combined arbitrarily with the optional methods or optional examples of other embodiments or examples.

[0085] The embodiment of the present application also provides a device for determining a botnet domain name. It should be noted that the device for determining a botnet domain name in the embodiment of the present application can be used to execute the method for determining a botnet domain name provided in the embodiment of the present application. The device for determining a botnet domain name provided in the embodiment of the present application is introduced below.

[0086] Figure 4 Schematic diagram of a device for determining a botnet domain name according to an embodiment of the present application. Figure 4 As shown, the device includes: a construction unit 401, a division unit 402, and a determination unit 403.

[0087] The construction unit 401 is used to construct a target network relationship graph according to the target DNS data, wherein the target DNS data at least includes: access domain name information of the target object, IP information of the target object and the access relationship between the IP information and the access domain name information, and the target network relationship graph at least includes: an IP node corresponding to the IP information and a domain name node corresponding to the access domain name information;

[0088] A division unit 402 is used to divide the target network relationship graph into communities according to a community discovery algorithm to obtain multiple community structure information;

[0089] The determination unit 403 is used to determine the target botnet domain name from the target DNS data according to the multiple community structure information.

[0090] The embodiment of the present application provides a device for determining a botnet domain name, wherein a construction unit 401 constructs a target network relationship graph based on target DNS data, wherein the target DNS data at least includes: access domain name information of a target object, IP information of the target object, and an access relationship between the IP information and the access domain name information, and the target network relationship graph at least includes: an IP node corresponding to the IP information and a domain name node corresponding to the access domain name information; a division unit 402 divides the target network relationship graph into communities based on a community discovery algorithm to obtain multiple community structure information; a determination unit 403 determines a target botnet domain name from the target DNS data based on multiple community structure information, thereby solving the problem in the related art that whether a target domain name is a botnet domain name is determined by calculating the similarity between the target domain name and the historical botnet domain name, resulting in a relatively low accuracy rate in determining the botnet domain name.

[0091] In this scheme, firstly, a target network relationship graph is established according to the access domain name information, IP information and the access relationship between the IP information and the access domain name information of the target object in the target DNS data; then, the target network relationship graph is divided into communities using a community discovery algorithm to obtain multiple community structure information (for example, multiple community clusters); finally, based on the multiple community structure information, an analysis is performed to obtain the target botnet domain name in the target DNS data.

[0092] By constructing a target network relationship graph, we can accurately analyze the network access behavior of the target object, and use the community discovery algorithm to divide the target network relationship graph into communities, thereby quickly obtaining multiple community clusters. Finally, based on multiple community structure information, we can analyze the target botnet domain name in the target DNS data, further reducing the risk of false positives in the results, and avoiding the problem of low accuracy in determining the botnet domain name in the traditional method of determining the target botnet domain name based on the difference between the suspected botnet domain name and the historical botnet domain name.

[0093] Optionally, in the device for determining a botnet domain name provided in an embodiment of the present application, the determination unit includes: a first determination module, used to determine an initial botnet from multiple community structure information based on the number of domain name nodes in each community structure information; and a second determination module, used to determine a target botnet domain name based on multiple domain names corresponding to the initial botnet.

[0094] Optionally, in the device for determining a botnet domain name provided in an embodiment of the present application, the first determination module includes: a first calculation submodule, used to calculate based on the number of domain name nodes and the number of second-level domain names in each community structure information to obtain a first ratio; a second calculation submodule, used to calculate based on the number of domain name nodes and the number of multi-level domain names in each community structure information to obtain a second ratio; and a screening submodule, used to screen multiple community structure information based on the number of domain name nodes, the number of edges corresponding to the IP nodes in each community structure information, the first ratio and at least one of the second ratio to obtain an initial botnet.

[0095] Optionally, in the botnet domain name determination device provided in the embodiment of the present application, the second determination module includes: a judgment submodule, used to judge whether the registered domain names of the multiple domain names corresponding to the initial botnet are the same, and obtain a judgment result; a third calculation submodule, used to calculate the similarity of the multiple target domain names to obtain the target similarity if the judgment result indicates that the registered domain names of the multiple target domain names among the multiple domain names corresponding to the initial botnet are different; and a determination submodule, used to determine the target botnet domain name from the multiple target domain names based on the target similarity.

[0096] Optionally, in the botnet domain name determination device provided in the embodiment of the present application, the third calculation submodule includes: a first calculation submodule, used for performing similarity calculation on the registered domain name of the first target domain name and the multi-level domain name of the second target domain name among any two target domain names to obtain a first similarity; a second calculation submodule, used for performing similarity calculation on the multi-level domain name of the first target domain name and the registered domain name of the second target domain name to obtain a second similarity; and a determination submodule, used for determining the target similarity based on the first similarity and the second similarity.

[0097] Optionally, in the device for determining a botnet domain name provided in an embodiment of the present application, the device further includes: an acquisition unit, for acquiring multiple network access requests triggered by a target object within a historical time period before constructing a target network relationship diagram based on target DNS data, wherein the multiple network access requests include at least: IP information and access domain name information of the target object; a parsing unit, for parsing the multiple network access requests to obtain initial DNS data; and a screening unit, for screening the initial DNS data based on a DNS response type to obtain target DNS data.

[0098] Optionally, in the device for determining a botnet domain name provided in an embodiment of the present application, the screening unit includes: a first screening module, used to screen the initial DNS data according to the DNS response type to obtain screened DNS data; a calculation module, used to calculate, based on the target IP information in the screened DNS data, a first number of DNS data corresponding to the target IP information and a second number of network access requests corresponding to the target IP information; and a second screening module, used to screen the screened DNS data according to the first number and the second number to obtain the target DNS data.

[0099] Optionally, in the device for determining the botnet domain name provided in an embodiment of the present application, the construction unit includes: a third determination module, used to determine the domain name node based on the access domain name information of the target object and to determine the IP node based on the IP information of the target object; a fourth determination module, used to determine the edge based on the access relationship between the IP information and the access domain name information; and a construction module, used to construct a target network relationship graph based on the domain name node, IP node and edge.

[0100] The apparatus for determining a botnet domain name includes a processor and a memory. The construction unit 401, the division unit 402, the determination unit 403, etc. are all stored in the memory as program units. The processor executes the program units stored in the memory to accurately determine the botnet domain name.

[0101] The processor includes a kernel, which calls the corresponding program unit from the memory. The kernel can be set to one or more, and the botnet domain name can be accurately determined by adjusting the kernel parameters.

[0102] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0103] An embodiment of the present invention provides a computer-readable storage medium on which a program is stored. When the program is executed by a processor, a method for determining a botnet domain name is implemented.

[0104] An embodiment of the present invention provides a processor, which is used to run a program, wherein the program executes a method for determining a botnet domain name when the program is running.

[0105] like Figure 5 As shown, an embodiment of the present invention provides an electronic device, the device includes one or more processors and a memory, the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the following steps: construct a target network relationship graph based on target DNS data, wherein the target DNS data at least includes: access domain name information of the target object, IP information of the target object and the access relationship between the IP information and the access domain name information, and the target network relationship graph at least includes: an IP node corresponding to the IP information and a domain name node corresponding to the access domain name information; divide the target network relationship graph into communities based on a community discovery algorithm to obtain multiple community structure information; determine the target botnet domain name from the target DNS data based on the multiple community structure information.

[0106] Optionally, determining the target botnet domain name from the target DNS data based on multiple community structure information includes: determining the initial botnet from the multiple community structure information based on the number of domain name nodes in each community structure information; and determining the target botnet domain name based on multiple domain names corresponding to the initial botnet.

[0107] Optionally, determining the initial botnet from multiple community structure information based on the number of domain name nodes in each community structure information includes: calculating based on the number of domain name nodes and the number of second-level domain names in each community structure information to obtain a first ratio; calculating based on the number of domain name nodes and the number of multi-level domain names in each community structure information to obtain a second ratio, wherein the multi-level domain name is different from the second-level domain name; and screening multiple community structure information based on at least one of the number of domain name nodes, the number of edges corresponding to the IP nodes in each community structure information, the first ratio, and the second ratio to obtain the initial botnet.

[0108] Optionally, determining the target botnet domain name based on multiple domain names corresponding to the initial botnet includes: judging whether the registered domain names of the multiple domain names corresponding to the initial botnet are the same, and obtaining a judgment result; if the judgment result indicates that the registered domain names of multiple target domain names among the multiple domain names corresponding to the initial botnet are different, similarity calculation is performed on the multiple target domain names to obtain target similarity; and determining the target botnet domain name from the multiple target domain names based on the target similarity.

[0109] Optionally, performing similarity calculation on multiple target domain names to obtain target similarity includes: for a first target domain name and a second target domain name among any two target domain names, performing similarity calculation on a registered domain name of the first target domain name and a multi-level domain name of the second target domain name to obtain a first similarity; performing similarity calculation on the multi-level domain name of the first target domain name and the registered domain name of the second target domain name to obtain a second similarity; and determining the target similarity based on the first similarity and the second similarity.

[0110] Optionally, before constructing the target network relationship diagram based on the target DNS data, the method also includes: obtaining multiple network access requests triggered by the target object within a historical time period, wherein the multiple network access requests include at least: the IP information and access domain name information of the target object; parsing the multiple network access requests to obtain initial DNS data; and filtering the initial DNS data based on the DNS response type to obtain the target DNS data.

[0111] Optionally, filtering the initial DNS data according to the DNS response type to obtain the target DNS data includes: filtering the initial DNS data according to the DNS response type to obtain filtered DNS data; calculating, based on the target IP information in the filtered DNS data, a first number of DNS data corresponding to the target IP information and a second number of network access requests corresponding to the target IP information; filtering the filtered DNS data according to the first number and the second number to obtain the target DNS data.

[0112] Optionally, based on the target DNS data, constructing the target network relationship graph includes: determining the domain name node based on the access domain name information of the target object and determining the IP node based on the IP information of the target object; determining the edge based on the access relationship between the IP information and the access domain name information; and constructing the target network relationship graph based on the domain name node, IP node and edge.

[0113] The devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0114] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes the following method steps: constructing a target network relationship graph based on target DNS data, wherein the target DNS data at least includes: access domain name information of the target object, IP information of the target object, and an access relationship between the IP information and the access domain name information, and the target network relationship graph at least includes: an IP node corresponding to the IP information and a domain name node corresponding to the access domain name information; dividing the target network relationship graph into communities based on a community discovery algorithm to obtain multiple community structure information; determining a target botnet domain name from the target DNS data based on the multiple community structure information.

[0115] Optionally, determining the target botnet domain name from the target DNS data based on multiple community structure information includes: determining the initial botnet from the multiple community structure information based on the number of domain name nodes in each community structure information; and determining the target botnet domain name based on multiple domain names corresponding to the initial botnet.

[0116] Optionally, determining the initial botnet from multiple community structure information based on the number of domain name nodes in each community structure information includes: calculating based on the number of domain name nodes and the number of second-level domain names in each community structure information to obtain a first ratio; calculating based on the number of domain name nodes and the number of multi-level domain names in each community structure information to obtain a second ratio, wherein the multi-level domain name is different from the second-level domain name; and screening multiple community structure information based on at least one of the number of domain name nodes, the number of edges corresponding to the IP nodes in each community structure information, the first ratio, and the second ratio to obtain the initial botnet.

[0117] Optionally, determining the target botnet domain name based on multiple domain names corresponding to the initial botnet includes: judging whether the registered domain names of the multiple domain names corresponding to the initial botnet are the same, and obtaining a judgment result; if the judgment result indicates that the registered domain names of multiple target domain names among the multiple domain names corresponding to the initial botnet are different, similarity calculation is performed on the multiple target domain names to obtain target similarity; and determining the target botnet domain name from the multiple target domain names based on the target similarity.

[0118] Optionally, performing similarity calculation on multiple target domain names to obtain target similarity includes: for a first target domain name and a second target domain name among any two target domain names, performing similarity calculation on a registered domain name of the first target domain name and a multi-level domain name of the second target domain name to obtain a first similarity; performing similarity calculation on the multi-level domain name of the first target domain name and the registered domain name of the second target domain name to obtain a second similarity; and determining the target similarity based on the first similarity and the second similarity.

[0119] Optionally, before constructing the target network relationship diagram based on the target DNS data, the method also includes: obtaining multiple network access requests triggered by the target object within a historical time period, wherein the multiple network access requests include at least: the IP information and access domain name information of the target object; parsing the multiple network access requests to obtain initial DNS data; and filtering the initial DNS data based on the DNS response type to obtain the target DNS data.

[0120] Optionally, filtering the initial DNS data according to the DNS response type to obtain the target DNS data includes: filtering the initial DNS data according to the DNS response type to obtain filtered DNS data; calculating, based on the target IP information in the filtered DNS data, a first number of DNS data corresponding to the target IP information and a second number of network access requests corresponding to the target IP information; filtering the filtered DNS data according to the first number and the second number to obtain the target DNS data.

[0121] Optionally, based on the target DNS data, constructing the target network relationship graph includes: determining the domain name node based on the access domain name information of the target object and determining the IP node based on the IP information of the target object; determining the edge based on the access relationship between the IP information and the access domain name information; and constructing the target network relationship graph based on the domain name node, IP node and edge.

[0122] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0123] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0124] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0125] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0126] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0127] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0128] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

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

[0130] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0131] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for determining a botnet domain name, It is characterized in that include: Constructing a target network relationship graph based on the target DNS data, wherein the target DNS data at least includes: access domain name information of the target object, IP information of the target object and the access relationship between the IP information and the access domain name information, and the target network relationship graph at least includes: an IP node corresponding to the IP information and a domain name node corresponding to the access domain name information; Dividing the target network relationship graph into communities according to a community discovery algorithm to obtain multiple community structure information; According to the plurality of community structure information, a target botnet domain name is determined from the target DNS data.

2. The method according to claim 1, It is characterized in that Determining a target botnet domain name from the target DNS data according to the plurality of community structure information includes: Determining an initial botnet from the plurality of community structure information according to the number of domain name nodes in each community structure information; The target botnet domain name is determined according to the multiple domain names corresponding to the initial botnet.

3. The method according to claim 2, It is characterized in that According to the number of domain name nodes in each community structure information, determining the initial botnet from the plurality of community structure information includes: Calculating according to the number of domain name nodes and the number of secondary domain names in each community structure information to obtain a first ratio; Calculating according to the number of domain name nodes and the number of multi-level domain names in each community structure information to obtain a second ratio, wherein the multi-level domain name is different from the secondary domain name; The plurality of community structure information are screened according to the number of domain name nodes, the number of edges corresponding to the IP nodes in each community structure information, and at least one of the first ratio and the second ratio to obtain the initial botnet.

4. The method according to claim 2, It is characterized in that Determining the target botnet domain name according to the multiple domain names corresponding to the initial botnet includes: Determine whether the registered domain names of the multiple domain names corresponding to the initial botnet are the same, and obtain a determination result; If the judgment result indicates that among the multiple domain names corresponding to the initial botnet, there are multiple target domain names whose registered domain names are different, similarity calculation is performed on the multiple target domain names to obtain target similarity; The target botnet domain name is determined from the multiple target domain names according to the target similarity.

5. The method according to claim 4, It is characterized in that Calculating the similarity of the multiple target domain names to obtain the target similarity includes: For a first target domain name and a second target domain name of any two target domain names, similarity calculation is performed on a registered domain name of the first target domain name and a multi-level domain name of the second target domain name to obtain a first similarity; Calculating similarity between the multi-level domain names of the first target domain name and the registered domain name of the second target domain name to obtain a second similarity; The target similarity is determined according to the first similarity and the second similarity.

6. The method according to claim 1, It is characterized in that Before constructing the target network relationship diagram based on the target DNS data, the method further includes: Acquire multiple network access requests triggered by the target object within a historical time period, wherein the multiple network access requests at least include: IP information and access domain name information of the target object; Parsing the multiple network access requests to obtain initial DNS data; The initial DNS data is screened according to the DNS response type to obtain the target DNS data.

7. The method according to claim 6, It is characterized in that The initial DNS data is screened according to the DNS response type, and the target DNS data obtained includes: Filtering the initial DNS data according to the DNS response type to obtain filtered DNS data; Calculate, based on the target IP information in the filtered DNS data, a first quantity of DNS data corresponding to the target IP information and a second quantity of network access requests corresponding to the target IP information; The filtered DNS data is filtered according to the first quantity and the second quantity to obtain the target DNS data.

8. The method according to claim 1, It is characterized in that Based on the target DNS data, the target network relationship diagram is constructed including: Determine the domain name node according to the access domain name information of the target object and determine the IP node according to the IP information of the target object; Determining an edge according to an access relationship between the IP information and the access domain name information; The target network relationship graph is constructed based on the domain name node, the IP node and the edge.

9. A device for determining a botnet domain name, It is characterized in that include: A construction unit is used to construct a target network relationship graph according to target DNS data, wherein the target DNS data at least includes: access domain name information of a target object, IP information of the target object, and an access relationship between the IP information and the access domain name information, and the target network relationship graph at least includes: an IP node corresponding to the IP information and a domain name node corresponding to the access domain name information; A division unit, used to divide the target network relationship graph into communities according to a community discovery algorithm to obtain multiple community structure information; The determination unit is configured to determine a target botnet domain name from the target DNS data according to the plurality of community structure information.

10. An electronic device, It is characterized in that The invention comprises one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for determining a botnet domain name according to any one of claims 1 to 8.

Citation Information

Patent Citations

  • A zombie network discovery method and a zombie network discovery device

    CN109698814A

  • Domain-floux botnet detection method based on hybrid learning

    CN110336789A

  • Massive network malicious domain name identification and classification method and system

    CN111131260A

  • Controlled host detection method and device based on knowledge graph

    CN112104677A

  • Botnet detection algorithm based on community discovery

    CN116527307A