Security risk monitoring method, monitoring device, server and storage medium

By obtaining the basic configuration data and alarm log data of asset equipment, and calculating the risk level of asset equipment, the problem of risk supervision blind spots in the existing technology is solved, comprehensive supervision and accurate assessment of asset equipment safety risks is achieved, and effective guidance is provided. Security Ministry’s precautions.

CN110598404BActive Publication Date: 2024-12-03TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN201910877016.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-09-17
Publication Date
2024-12-03
Estimated Expiration
2039-09-17

AI Technical Summary

Technical Problem

The existing technology is prone to blind spots when supervising the safety risks of asset equipment and cannot fully control the overall risk situation. Especially when physical resources are limited, it is difficult to take into account the comprehensiveness and effectiveness of risk supervision.

Method used

By obtaining the basic configuration data of asset equipment and alarm log data, the risk level is calculated based on the security event monitoring data of IP addresses, and combining the asset importance level, event level and event weight, the risk level of asset equipment is comprehensively evaluated to guide the security department. Defense strategy.

Benefits of technology

It has achieved comprehensive supervision of asset equipment safety risks, reduced risk blind spots, provided more accurate and effective risk assessments, and guided targeted security department prevention measures.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN110598404B_ABST
    Figure CN110598404B_ABST
Patent Text Reader

Abstract

The present application provides a security risk supervision method, supervision device, server and storage medium, the method includes obtaining basic configuration data of asset equipment, the basic configuration data includes at least one IP address associated with the asset equipment; obtaining alarm log data of each IP address, the alarm log data includes monitoring data of at least one security event; for each IP address, based on the monitoring data of at least one security event of the IP, calculating the risk level of the IP address, the risk level represents the degree of security risk; calculating the risk level of the asset equipment according to the risk level of each IP address. The present application takes the asset equipment as the dimension, associates the basic configuration data and alarm log data related to the asset equipment to comprehensively supervise the risk situation of the asset equipment, and is used to guide security defense.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of network security technology, and more specifically, to a security risk supervision method, a supervision device, a server and a storage medium. Background Art

[0002] With the continuous development of Internet technology, physical assets such as computers in large-scale systems such as enterprises are becoming increasingly large, and network security issues are receiving more and more attention from users.

[0003] Therefore, how to supervise the security risks faced by assets and equipment is an issue that technical personnel in this field urgently need to solve. Summary of the invention

[0004] In view of this, the present invention provides a security risk supervision method, a supervision device, a server and a storage medium to supervise the security risks of asset equipment.

[0005] To achieve the above objectives, on the one hand, the present application provides a security risk management method, the method comprising:

[0006] Acquire basic configuration data of an asset device, wherein the basic configuration data at least includes at least one IP address associated with the asset device;

[0007] Acquire alarm log data of each of the IP addresses, wherein the alarm log data includes monitoring data of at least one security event;

[0008] For each of the IP addresses, calculate the risk level of the IP address based on monitoring data of at least one security event of the IP address, wherein the risk level represents the degree of security risk;

[0009] The risk level of the asset device is calculated according to the risk level of each of the IP addresses.

[0010] In a possible implementation, the basic configuration data further includes an organization to which the asset device belongs, and the step of calculating the risk level of the IP address based on the monitoring data of at least one security event of the IP address includes:

[0011] Determine an asset importance level that matches the organizational structure, wherein the asset importance level represents the importance of the asset equipment;

[0012] For each security event of the IP address, analyze the monitoring data of the security event to at least determine the event level and event weight of the security event, wherein the event level represents the degree of impact of the security event on the asset device after the occurrence of the security event;

[0013] The risk level of the IP address is calculated based on the asset importance level, the event level of each security event, and the event weight.

[0014] In another possible implementation, the at least one security event includes an attack event, and the analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event includes:

[0015] Determine the attack frequency of the attack event against the IP address;

[0016] When the attack frequency satisfies a preset attack condition, analyzing the monitoring data of the attack event to determine the event level and event weight of the attack event;

[0017] The calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight includes:

[0018] A first risk level of the IP address is calculated based on the asset importance level, the attack frequency, the event level of the attack event, and the event weight.

[0019] In another possible implementation, the at least one security event includes a vulnerability event, and the analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event includes:

[0020] Determine the network location of the IP address, and analyze the monitoring data of the vulnerability event to determine the propagation level, event level and event weight of the vulnerability event, wherein the propagation level represents the degree of propagation of the vulnerability event;

[0021] The calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight includes:

[0022] A second risk level of the IP address is calculated based on the asset importance level, the network location, the propagation level of the vulnerability event, the event level and the event weight.

[0023] In another possible implementation, the at least one security event includes an intrusion event, and the analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event includes:

[0024] Analyzing the monitoring data of the intrusion event to determine the intrusion level, event level and event weight of the intrusion event, wherein the intrusion level represents the intrusion degree of the intrusion event;

[0025] The calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight includes:

[0026] The third risk level of the IP address is calculated based on the asset importance level, the intrusion level of the intrusion event, the event level and the event weight. In another possible implementation, the risk level includes a risk score, and the risk level of the asset device is calculated according to the risk level of each IP address, including:

[0027] The risk scores of each IP address are added together and used as the risk score of the asset device.

[0028] In yet another possible implementation, the method further includes:

[0029] Output the risk score of the asset equipment.

[0030] In another aspect, the present application further provides a security risk management device, the device comprising:

[0031] A first data acquisition module, used to acquire basic configuration data of an asset device, wherein the basic configuration data at least includes at least one IP address associated with the asset device;

[0032] A second data acquisition module, used to acquire alarm log data of each of the IP addresses, wherein the alarm log data includes monitoring data of at least one security event;

[0033] A first risk calculation module, configured to calculate, for each of the IP addresses, a risk level of the IP address based on monitoring data of at least one security event of the IP address, wherein the risk level represents a degree of security risk;

[0034] The second risk calculation module is used to calculate the risk level of the asset device according to the risk level of each IP address.

[0035] On the other hand, the present application also provides a server, including: at least one memory and at least one processor; the memory stores a program, the processor calls the program stored in the memory, and the program is used to implement the security risk management method.

[0036] On the other hand, the present application also provides a storage medium, in which computer executable instructions are stored, and the computer executable instructions are used to execute the security risk management method.

[0037] The present application provides a security risk supervision method, supervision device, server and storage medium, the method includes obtaining basic configuration data of asset equipment, the basic configuration data includes at least one IP address associated with the asset equipment; obtaining alarm log data of each IP address, the alarm log data includes monitoring data of at least one security event; for each IP address, based on the monitoring data of at least one security event of the IP, calculating the risk level of the IP address, the risk level represents the degree of security risk; calculating the risk level of the asset equipment according to the risk level of each IP address. The present application takes the asset equipment as the dimension, associates the basic configuration data and alarm log data related to the asset equipment to comprehensively supervise the risk situation of the asset equipment, and is used to guide security defense. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0039] Figure 1 A hardware structure block diagram of a server provided in an embodiment of the present application;

[0040] Figure 2 A method flow chart of a security risk management method provided in an embodiment of the present application;

[0041] Figure 3 An application scenario diagram of a security risk supervision method provided in an embodiment of the present application;

[0042] Figure 4 A signaling flow chart of a security risk supervision method provided in an embodiment of the present application;

[0043] Figure 5 A schematic diagram of the structure of a security risk monitoring device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0045] At present, in order to supervise the safety risks of assets and equipment, most of them are evaluated through only one or several safety indicators of the same type, which often leads to blind spots in risk supervision and makes it impossible to control the overall risk situation of assets and equipment.

[0046] Of course, increasing the number of safety indicators in the assessment will certainly reduce the blind spots of risk management. However, given the limited physical resources of asset equipment such as memory and bandwidth, how to balance the comprehensiveness of risk management and determine effective safety indicators requires in-depth research by technical personnel in this field.

[0047] The applicant of this application has discovered through numerous experiments that, taking asset equipment as a dimension and associating basic configuration data and alarm log data related to the asset equipment can comprehensively monitor the risk situation of the asset equipment and be used to guide security defense.

[0048] A security risk management method provided in an embodiment of the present application can be applied to a server (such as a security risk management server or other specially configured server).

[0049] Figure 1 A hardware structure diagram of a server provided in an embodiment of the present application is shown in FIG. Figure 1 , the hardware structure of the server may include: at least one memory 11, at least one communication interface 12, at least one storage 13 and at least one communication bus 14;

[0050] In the embodiment of the present invention, the number of the processor 11, the communication interface 12, the memory 13, and the communication bus 14 is at least one, and the processor 11, the communication interface 12, and the memory 13 communicate with each other through the communication bus 14;

[0051] The processor 11 may be a central processing unit (CPU), a graphics processing unit (GPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention;

[0052] The memory 13 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory;

[0053] The memory stores a program, and the processor can call the program stored in the memory, and the program is used to:

[0054] Obtaining basic configuration data of the asset device, the basic configuration data at least including at least one IP address associated with the asset device;

[0055] Obtaining alarm log data for each IP address, where the alarm log data includes monitoring data of at least one security event;

[0056] For each IP address, the risk level of the IP address is calculated based on the monitoring data of at least one security event of the IP address, and the risk level represents the degree of security risk;

[0057] The risk level of the asset device is calculated based on the risk level of each IP address.

[0058] Optionally, the detailed and extended functions of the program can be referred to the description below.

[0059] Figure 2 A method flow chart of a security risk management method provided in an embodiment of the present application. Figure 2 , the method comprises the following steps:

[0060] Step S101: Acquire basic configuration data of an asset device, where the basic configuration data at least includes at least one IP address associated with the asset device.

[0061] In the embodiment of the present application, the asset device is defined by the machine ID, that is, one asset device is one machine. Since the IP address of an asset device may change, that is, an asset device may have multiple IP addresses, a comprehensive analysis of the security risks of all IP addresses associated with the asset device can fully monitor the security risks of the asset device.

[0062] Specifically, the basic configuration data of the asset device can be obtained from the resource management pool of the asset device. Of course, in addition to at least one IP address associated with the asset device, other attribute information of the asset device can also be obtained from the basic configuration data, such as the organization to which it belongs, the owner of the device, etc., which is not limited in the embodiments of the present application.

[0063] Step S102: Acquire alarm log data of each IP address, where the alarm log data includes monitoring data of at least one security event.

[0064] In an embodiment of the present application, for each IP address, alarm log data for a certain period of time can be captured from the operation log of the IP address, and the alarm log data can be specifically divided into asset attack data of attack events, asset vulnerability data of vulnerability events, and asset intrusion data of intrusion events according to the type of security events.

[0065] Specifically, asset attack data refers to the attack attempt data of external threats on asset devices at the web application level; asset vulnerability data includes web application vulnerability data, host software vulnerability data, configuration defect data and vulnerability data caused by human illegal operations on asset devices on the one hand, and external threat intelligence data (real-time and latest vulnerability information exposed on the Internet, which can be determined by matching software versions and vulnerability analysis) on the other hand; asset intrusion data refers to external threats successfully exploiting the vulnerabilities of asset devices to invade, and open backdoors on asset devices, place Trojans, viruses, and drag sensitive data.

[0066] Among them, for asset attack data, this is when no backdoors or vulnerabilities are found, and the asset equipment is not in danger of being successfully attacked by hackers or potentially being attacked by hackers. At this time, the asset equipment is facing some hacker detection behaviors, and the attack situation can be discovered through attack interception equipment.

[0067] For asset vulnerable data, this is a situation where no backdoor is found but a vulnerability is found. The asset is not in danger of being successfully attacked by hackers, but there is a potential risk of being attacked by hackers. At this time, the vulnerability of the asset equipment can be discovered through vulnerability detection software and external threat intelligence.

[0068] For asset intrusion data, this is when a backdoor is discovered, the asset device has been successfully attacked by hackers, and there are risks such as data leakage, website paralysis, and page tampering. At this time, the intrusion of the asset device can be discovered by detecting inbound and outbound traffic, attack chains, etc.

[0069] Step S103: For each IP address, the risk level of the IP address is calculated based on the monitoring data of at least one security event of the IP address, where the risk level represents the degree of security risk.

[0070] In the embodiment of the present application, the monitoring data of different types of security events for an IP address (i.e., the above-mentioned asset attack data, asset vulnerability data, and asset intrusion data) can be calculated using different computing systems because they represent different levels of risk.

[0071] Specifically, asset attack data can enter the daily calculation system to calculate the risk level of attack events, asset vulnerability data can enter the vulnerability calculation system to calculate the risk level of vulnerability events, and asset intrusion data can enter the event calculation system to calculate the risk level of intrusion events.

[0072] Finally, the risk level of an IP address is determined by comprehensively analyzing the risk levels of different security events of the IP address.

[0073] It should be noted that the calculation indicators of the security events involved in the above-mentioned daily calculation system, vulnerability calculation system and intrusion calculation system are not limited in this embodiment. The risk level can be a stepped level, such as level 1, level 2 and level 3, or a risk score, which is not limited in this embodiment.

[0074] Taking the risk level as a step-by-step level as an example, the process of determining the risk level of an IP address is explained as follows:

[0075] If the security event detected by the IP address is any one of an attack event, a vulnerability event, and an intrusion event, the risk level of the security event can be determined as the risk level of the IP address;

[0076] If the security events monitored for the IP address are multiple types of attack events, vulnerability events, and intrusion events, the highest level of the risk levels of the multiple security events may be used as the risk level of the IP address.

[0077] Taking the risk level as a risk score as an example, the process of determining the risk level of an IP address is further explained:

[0078] If the security event detected for the IP address is any one of an attack event, a vulnerability event, and an intrusion event, the risk score of the security event may be determined as the risk score of the IP address;

[0079] If the security events detected for the IP address are multiple attacks, vulnerability events, and intrusion events, the risk scores of the multiple security events can be added together as the risk score of the IP address. For ease of understanding, the following uses the risk score as an example to illustrate the process of calculating the risk level of an IP address.

[0080] In some other embodiments, in order to accurately assess the risk level of an IP address, the basic configuration data also includes the organization to which the asset device belongs. In step S103, "calculating the risk level of the IP address based on monitoring data of at least one security event of the IP address" may adopt the following steps:

[0081] Determine the asset importance level that matches the organization. The asset importance level represents the importance of the asset equipment. For each security event of the IP address, analyze the monitoring data of the security event to at least determine the event level and event weight of the security event. The event level represents the impact of the security event on the asset equipment after it occurs. Calculate the risk level of the IP address based on the asset importance level, the event level and event weight of each security event.

[0082] In the embodiment of the present application, since different organizations deploy different businesses and data on asset devices, asset devices can be graded according to the importance of the business and data, and the severity of the loss caused by the business and data, and specifically can include three levels: core, key, and ordinary. Of course, the grade classification rules for asset devices in this embodiment are not limited and can be set according to actual needs.

[0083] In addition, for any security event among attack events, vulnerability events and intrusion events, the monitoring data of the security event can be analyzed to determine the impact of the security event on the asset equipment after the event occurs. Specifically, by analyzing the type, means and impact of the security event on the asset equipment after the event occurs, the corresponding event level is matched for the security event. Of course, the event level matching rules in this embodiment are not limited and can be set according to time requirements.

[0084] Finally, for any security event among attack events, vulnerability events and intrusion events, the risk level of the IP address under the security event can be calculated based on the asset importance level, the event level of the security event and the event weight of the security event, and then the risk level of the IP address is calculated by comprehensively considering the risk level of all security events.

[0085] Continuing with the example of risk level as risk score, the process of determining the risk level of an IP address is described as follows:

[0086] The three levels of asset importance, core, key and ordinary, correspond to grade scores a1, a2 and a3 respectively;

[0087] The high, medium and low levels of the attack event correspond to the level scores b1, b2 and b3 respectively, and their event weight is e1;

[0088] The three levels of vulnerability events, high, medium and low, correspond to level scores c1, c2 and c3 respectively, and their event weight is e2;

[0089] The three levels of intrusion events, high, medium and low, correspond to level scores d1, d2 and d3 respectively, and their event weight is e3.

[0090] Assuming that the security events monitored for an IP address include attack events, vulnerability events, and intrusion events, the risk score of the IP address at this time = asset importance level (core: a1, key: a2, ordinary: a3) * event level of attack events (high: b1, medium: b2, low: b3) * event weight of attack events e1 + asset importance level (core: a1, key: a2, ordinary: a3) * event level of vulnerability events (high: c1, medium: c2, low: c3) * event weight of vulnerability events e2 + asset importance level (core: a1, key: a2, ordinary: a3) * event level of intrusion events (high: d1, medium: d2, low: d3) * event weight of intrusion events e3.

[0091] In some other embodiments, in accurately calculating the risk level of the IP address under the attack event, "analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event" includes the following steps:

[0092] Determine the attack frequency of the attack event against the IP address; when the attack frequency meets the preset attack conditions, analyze the monitoring data of the attack event to determine the event level and event weight of the attack event;

[0093] At this time, "calculating the risk level of the IP address based on the asset importance level, the event level of each security event, and the event weight" includes the following steps:

[0094] The first risk level of the IP address is calculated based on the asset importance level, the attack frequency, the event level of the attack event, and the event weight.

[0095] In the embodiment of the present application, in order to determine the attack frequency, the number of attacks on the IP address by the web attack event within a certain period of time can be counted. If the attack frequency is greater than the preset frequency threshold, the event level and event weight of the attack event are determined by matching. At this time, the risk score of the IP address under the attack event (i.e., the first risk score) = asset importance level (core: a1, key: a2, ordinary: a3) * attack frequency f * event level of the attack event (high: b1, medium: b2, low: b3) * event weight e1 of the attack event.

[0096] Of course, if the attack frequency is not greater than the preset frequency threshold, the risk score of the IP address under the attack event (ie, the first risk score) is considered to be 0. Of course, corresponding first risk scores can also be set for different attack frequencies, which is not limited in this embodiment.

[0097] In some other embodiments, in order to accurately calculate the risk level of the IP address under the vulnerability event, "analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event" includes the following steps:

[0098] Determine the network location of the IP address and analyze the monitoring data of the vulnerability event to determine the propagation level, event level and event weight of the vulnerability event. The propagation level represents the degree of propagation of the vulnerability event.

[0099] At this time, "calculating the risk level of the IP address based on the asset importance level, the event level of each security event, and the event weight" includes the following steps:

[0100] The second risk level of the IP address is calculated based on the asset importance level, network location, propagation level of the vulnerability event, event level and event weight.

[0101] In the embodiment of the present application, the network location is divided into an intranet and an extranet. The corresponding extranet vulnerabilities refer to vulnerabilities that can be detected through the external network, such as 0day / 1day vulnerabilities that can be detected by the external network, web application vulnerabilities, host software vulnerabilities, and vulnerabilities caused by human illegal operations; intranet vulnerabilities refer to vulnerabilities that cannot be detected by the external network, such as 0day / 1day vulnerabilities, host software vulnerabilities, etc.

[0102] In addition, when determining the propagation level of a vulnerability event, the propagation scope of the vulnerability event can be obtained by performing an internal scan of all asset devices in the management area. For example, if more than 50% of the asset devices have the vulnerability event, it is considered to be widely spread, otherwise it is considered to be a small-scale spread.

[0103] In the network location, the internal network and the external network correspond to the level scores g1 and g2 respectively;

[0104] In the communication level, wide-range communication and small-range communication correspond to level scores h1 and h2 respectively;

[0105] At this time, the risk score of the IP address under the vulnerability event (i.e. the second risk score) = asset importance level (core: a1, key: a2, ordinary: a3) * network location (intranet: g1, extranet: g2) * propagation level of the vulnerability event (wide-range propagation: h1, small-range propagation: h2) * event level of the vulnerability event (high: c1, medium: c2, low: c3) * event weight of the vulnerability event e2.

[0106] In some other embodiments, in order to accurately calculate the risk level of the IP address under the intrusion event, "analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event" includes the following steps:

[0107] Analyze the monitoring data of the intrusion event to determine the intrusion level, event level and event weight of the intrusion event, where the intrusion level represents the degree of intrusion of the intrusion event;

[0108] At this time, "calculating the risk level of the IP address based on the asset importance level, the event level of each security event, and the event weight" includes the following steps:

[0109] The third risk level of the IP address is calculated based on the asset importance level, the intrusion level of the intrusion event, the event level and the event weight.

[0110] In the embodiment of the present application, the intrusion level of the intrusion event is divided into confirmed loss (such as data leakage, website paralysis, page tampering) and successful intrusion but no loss (such as hacker intrusion, DDoS, CC).

[0111] In the invasion level, the damage caused and the no damage caused correspond to the level scores i1 and i2 respectively;

[0112] At this time, the risk score of the IP address under the intrusion event (i.e. the third risk score) = asset importance level (core: a1, key: a2, ordinary: a3) * intrusion level of the intrusion event (caused loss: i1, no loss caused i2) * event level of the intrusion event (high: d1, medium: d2, low: d3) * event weight of the intrusion event e3.

[0113] Step S104: Calculate the risk level of the asset device according to the risk level of each IP address.

[0114] In the embodiment of the present application, the risk level of the asset device is determined by comprehensively analyzing the risk levels of all IP addresses associated with the asset device.

[0115] Taking the risk level as a step-by-step level as an example, the process of determining the risk level of assets and equipment is explained:

[0116] If the asset device is associated with one IP address, the risk level of the IP address can be determined as the risk level of the asset device;

[0117] If an asset device is associated with multiple IP addresses, the highest risk level among the multiple IP addresses can be used as the risk level of the asset device, or the risk level that appears most frequently among the multiple IP addresses can be used as the risk level of the asset device. This embodiment does not limit this.

[0118] Taking the risk level as the risk score as an example, the process of determining the risk level of asset equipment is further explained:

[0119] If the asset device is associated with one IP address, the risk score of the IP address may be determined as the risk score of the asset device;

[0120] If an asset device is associated with multiple IP addresses, the sum of the risk scores of the multiple IP addresses may be used as the risk score of the asset device.

[0121] Furthermore, the risk score of the asset equipment can be output to the user end, so that the user can formulate a corresponding security defense strategy for the asset equipment based on the risk score.

[0122] Figure 3 The application scenario diagram provided for the embodiment of the present application, in which the server is connected to multiple asset devices in communication, and for each asset device, the server monitors the security risk of the asset device by monitoring the security events of the asset device. Figure 3 The application scenario diagram of the present application is further described by the following scenario example of supervising an asset device. The signaling flow chart of the scenario example is as follows Figure 4 As shown, the following steps are included:

[0123] Step S201: The server obtains at least one IP address associated with the asset device and the organization to which the asset device belongs.

[0124] Step S202: The server obtains alarm log data of the IP address, where the alarm log data includes monitoring data of at least one security event.

[0125] Step S203: The server determines the asset importance level that matches the organization.

[0126] Step S204: The server determines the attack frequency of the attack event against the IP address; when the attack frequency meets the preset attack condition, the monitoring data of the attack event is analyzed to determine the event level and event weight of the attack event; and the first risk score of the IP address is calculated based on the asset importance level, attack frequency, event level and event weight of the attack event.

[0127] Step S205: The server determines the network location of the IP address and analyzes the monitoring data of the vulnerability event to determine the propagation level, event level and event weight of the vulnerability event, where the propagation level characterizes the degree of propagation of the vulnerability event; and calculates the second risk score of the IP address based on the asset importance level, network location, propagation level, event level and event weight of the vulnerability event.

[0128] Step S206: The server analyzes the monitoring data of the intrusion event to determine the intrusion level, event level and event weight of the intrusion event, where the intrusion level represents the degree of intrusion of the intrusion event; and calculates the third risk score of the IP address based on the asset importance level, the intrusion level, event level and event weight of the intrusion event.

[0129] Step S207: The server uses the sum of the first risk score, the second risk score, and the third risk score of the IP address as the risk score of the IP address.

[0130] Step S208: The server adds up the risk scores of each IP address and uses the sum as the risk score of the asset device.

[0131] Step S209: The server outputs the risk score of the asset equipment to the user end.

[0132] Step S210: The user terminal displays the risk score of the asset equipment so that the user can formulate a corresponding security defense strategy for the asset equipment based on the risk score.

[0133] The following is an introduction to the security risk management device provided in the embodiment of the present application. The security risk management device described below can be considered as a program module required for the server to implement the security risk management method provided in the embodiment of the present application. The content of the security risk management device described below can be cross-referenced with the content of the security risk management method described above.

[0134] Figure 5 This is a schematic diagram of the structure of the security risk monitoring device provided in the embodiment of the present application. Figure 5 , the device comprises:

[0135] A first data acquisition module 101 is used to acquire basic configuration data of an asset device, where the basic configuration data at least includes at least one IP address associated with the asset device;

[0136] A second data acquisition module 102 is used to acquire alarm log data of each IP address, where the alarm log data includes monitoring data of at least one security event;

[0137] A first risk calculation module 103 is used to calculate the risk level of each IP address based on monitoring data of at least one security event of the IP address, where the risk level represents the degree of security risk;

[0138] The second risk calculation module 104 is used to calculate the risk level of the asset device according to the risk level of each IP address.

[0139] In a security risk management device provided in an embodiment of the present application, preferably, the basic configuration data also includes an organization to which the asset equipment belongs, and the first risk calculation module 103 for calculating the risk level of the IP address based on the monitoring data of at least one security event of the IP is specifically used to:

[0140] Determine the asset importance level that matches the organization. The asset importance level represents the importance of the asset equipment. For each security event of the IP address, analyze the monitoring data of the security event to at least determine the event level and event weight of the security event. The event level represents the impact of the security event on the asset equipment after it occurs. Calculate the risk level of the IP address based on the asset importance level, the event level and event weight of each security event.

[0141] In a security risk supervision device provided in an embodiment of the present application, preferably, at least one security event includes an attack event, and the first risk calculation module 103 for analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event is specifically used to:

[0142] Determine the attack frequency of the attack event against the IP address; when the attack frequency meets the preset attack conditions, analyze the monitoring data of the attack event to determine the event level and event weight of the attack event;

[0143] The first risk calculation module 103 for calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight is specifically used to:

[0144] The first risk level of the IP address is calculated based on the asset importance level, the attack frequency, the event level of the attack event, and the event weight.

[0145] In a security risk supervision device provided in an embodiment of the present application, preferably, at least one security event includes a vulnerability event, and the first risk calculation module 103 for analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event is specifically used to:

[0146] Determine the network location of the IP address and analyze the monitoring data of the vulnerability event to determine the propagation level, event level and event weight of the vulnerability event. The propagation level represents the degree of propagation of the vulnerability event.

[0147] The first risk calculation module 103 for calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight is specifically used to:

[0148] The second risk level of the IP address is calculated based on the asset importance level, network location, propagation level of the vulnerability event, event level and event weight.

[0149] In a security risk supervision device provided in an embodiment of the present application, preferably, at least one security event includes an intrusion event, and the first risk calculation module 103 for analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event is specifically used to:

[0150] Analyze the monitoring data of the intrusion event to determine the intrusion level, event level and event weight of the intrusion event, where the intrusion level represents the degree of intrusion of the intrusion event;

[0151] The first risk calculation module 103 for calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight is specifically used to:

[0152] The third risk level of the IP address is calculated based on the asset importance level, the intrusion level of the intrusion event, the event level and the event weight.

[0153] In a security risk management device provided in an embodiment of the present application, preferably, the risk level includes a risk score, and the second risk calculation module 104 is specifically used to:

[0154] The risk score of each IP address is added together as the risk score of the asset device.

[0155] In a security risk management device provided in an embodiment of the present application, preferably, the second risk calculation module 104 is further used to:

[0156] Output the risk score of the asset equipment.

[0157] An embodiment of the present invention further provides a storage medium, in which computer executable instructions are stored, and the computer executable instructions are used to execute the security risk management method.

[0158] Optionally, the detailed and extended functions of the instruction may refer to the above description.

[0159] The embodiments of the present application provide a security risk supervision method, supervision device, server and storage medium, the method comprising obtaining basic configuration data of asset equipment, the basic configuration data at least including at least one IP address associated with the asset equipment; obtaining alarm log data of each IP address, the alarm log data including monitoring data of at least one security event; for each IP address, calculating the risk level of the IP address based on the monitoring data of at least one security event of the IP, the risk level characterizing the degree of security risk; calculating the risk level of the asset equipment according to the risk level of each IP address. The present application takes the asset equipment as the dimension, associates the basic configuration data and alarm log data related to the asset equipment to comprehensively supervise the risk situation of the asset equipment, and is used to guide security defense.

[0160] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0161] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0162] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0163] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the core concept or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A safety risk supervision method, characterized in that: The method comprises: Acquire basic configuration data of an asset device, wherein the basic configuration data includes at least one IP address associated with the asset device and an organization to which the asset device belongs; Acquire alarm log data of each of the IP addresses, the alarm log data including monitoring data of at least one security event, the monitoring data being asset attack data, asset vulnerability data or asset intrusion data, the asset attack data referring to attack attempt data of external threats on asset devices at the web application level, the asset vulnerability data including web application vulnerability data, host software vulnerability data, configuration defect data, vulnerability data caused by human illegal operations and external threat intelligence data on asset devices, the asset intrusion data referring to external threats successfully invading by exploiting the vulnerability of asset devices, and opening backdoors, placing Trojans, viruses and extracting sensitive data on asset devices; For each of the IP addresses, determine an asset importance level that matches the organization, where the asset importance level represents the importance of the asset device; For each security event of the IP address, analyze the monitoring data of the security event to at least determine the event level and event weight of the security event, wherein the event level represents the degree of impact of the security event on the asset device after the occurrence of the security event; Calculate the risk level of the IP address based on the asset importance level, the event level of each security event, and the event weight, wherein the risk level represents the degree of security risk; Calculate the risk level of the asset device according to the risk level of each IP address; Wherein, the at least one security event includes an attack event, and the analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event includes: Determine the attack frequency of the attack event against the IP address; When the attack frequency satisfies a preset attack condition, analyzing the monitoring data of the attack event to determine the event level and event weight of the attack event; The calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight includes: Calculate a first risk level of the IP address based on the asset importance level, the attack frequency, the event level of the attack event, and the event weight; Wherein, the at least one security event includes a vulnerability event, and the analyzing the monitoring data of the security event at least determines the event level and event weight of the security event, including: Determine the network location of the IP address, and analyze the monitoring data of the vulnerability event to determine the propagation level, event level and event weight of the vulnerability event, wherein the propagation level represents the degree of propagation of the vulnerability event; The calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight includes: Calculate a second risk level of the IP address based on the asset importance level, the network location, the propagation level of the vulnerability event, the event level, and the event weight; Wherein, the at least one security event includes an intrusion event, and the analyzing the monitoring data of the security event to at least determine the event level and event weight of the security event includes: Analyzing the monitoring data of the intrusion event to determine the intrusion level, event level and event weight of the intrusion event, wherein the intrusion level represents the intrusion degree of the intrusion event; The calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight includes: A third risk level of the IP address is calculated based on the asset importance level, the intrusion level of the intrusion event, the event level and the event weight.

2. The method according to claim 1, characterized in that: The risk level includes a risk score, and the step of calculating the risk level of the asset device according to the risk level of each IP address includes: The risk scores of each IP address are added together and used as the risk score of the asset device.

3. The method according to claim 2, characterized in that The method further comprises: Output the risk score of the asset equipment.

4. A safety risk monitoring device, characterized in that: The device comprises: A first data acquisition module is used to acquire basic configuration data of an asset device, wherein the basic configuration data at least includes at least one IP address associated with the asset device and an organization to which the asset device belongs; A second data acquisition module is used to acquire alarm log data of each of the IP addresses, wherein the alarm log data includes monitoring data of at least one security event, wherein the monitoring data is asset attack data, asset vulnerability data or asset intrusion data, wherein the asset attack data refers to attack attempt data of external threats on asset devices at the web application level, wherein the asset vulnerability data includes web application vulnerability data, host software vulnerability data, configuration defect data, vulnerability data caused by human illegal operations and external threat intelligence data on asset devices, and wherein the asset intrusion data refers to external threats successfully invading by exploiting the vulnerability of asset devices, and opening backdoors, placing Trojans, viruses and extracting sensitive data on asset devices; A first risk calculation module is used to determine, for each of the IP addresses, an asset importance level that matches the organization, the asset importance level representing the importance of the asset equipment; for each security event of the IP address, analyze the monitoring data of the security event to at least determine the event level and event weight of the security event, the event level representing the degree of impact of the security event on the asset equipment after it occurs; calculate the risk level of the IP address based on the asset importance level, the event level and event weight of each security event, the risk level representing the degree of security risk; A second risk calculation module, configured to calculate the risk level of the asset device according to the risk level of each IP address; Wherein, the at least one security event includes an attack event, and the first risk calculation module analyzes the monitoring data of the security event to at least determine the event level and event weight of the security event, specifically for: Determine the attack frequency of the attack event against the IP address; When the attack frequency satisfies a preset attack condition, analyzing the monitoring data of the attack event to determine the event level and event weight of the attack event; The calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight includes: Calculate a first risk level of the IP address based on the asset importance level, the attack frequency, the event level of the attack event, and the event weight; Wherein, the at least one security event includes a vulnerability event, and the first risk calculation module analyzes the monitoring data of the security event to at least determine the event level and event weight of the security event, specifically for: Determine the network location of the IP address, and analyze the monitoring data of the vulnerability event to determine the propagation level, event level and event weight of the vulnerability event, wherein the propagation level represents the degree of propagation of the vulnerability event; The calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight includes: Calculate a second risk level of the IP address based on the asset importance level, the network location, the propagation level of the vulnerability event, the event level, and the event weight; Wherein, the at least one security event includes an intrusion event, and the first risk calculation module analyzes the monitoring data of the security event to at least determine the event level and event weight of the security event, specifically for: Analyzing the monitoring data of the intrusion event to determine the intrusion level, event level and event weight of the intrusion event, wherein the intrusion level represents the intrusion degree of the intrusion event; The calculating the risk level of the IP address based on the asset importance level, the event level of each security event and the event weight includes: A third risk level of the IP address is calculated based on the asset importance level, the intrusion level of the intrusion event, the event level and the event weight.

5. The device according to claim 4, characterized in that The risk level includes a risk score, and the second risk calculation module is specifically used for: The risk scores of each IP address are added together and used as the risk score of the asset device.

6. The device according to claim 5, characterized in that The second risk calculation module is also used for: Output the risk score of the asset equipment.

7. A server, characterized in that: include: at least one memory and at least one processor; The memory stores a program, and the processor calls the program stored in the memory, and the program is used to implement the security risk management method as described in any one of claims 1-3.

8. A storage medium, characterized in that: The storage medium stores computer-executable instructions, and the computer-executable instructions are used to execute the security risk management method as described in any one of claims 1-3.

Citation Information

Patent Citations

  • Key IP address safety alarm association analysis method based on fuzzy scene

    CN105471623A

  • Risk control method, device and storage medium

    CN108667828A