Traffic monitoring methods, devices, equipment, and media based on cyberspace ranges
By acquiring characteristic data of cybersecurity events and querying traffic data in a cyberspace test range, the problem of incomplete traffic data in existing technologies is solved, enabling accurate monitoring of the status of traffic acquisition and storage devices, and ensuring data integrity and accurate judgment.
Patent Information
- Application Number
- CN202311052106.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-18
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2043-08-18
AI Technical Summary
Existing technologies cannot accurately monitor the status of traffic acquisition and storage devices in cyberspace ranges, resulting in incomplete traffic data that cannot reflect the true state of the entire cyberspace range.
By obtaining characteristic data of cybersecurity events from the security event database of the cyberspace range and querying the corresponding traffic data in the traffic database, traffic probes are used to capture and mirror the full traffic data to ensure data integrity.
It enables accurate monitoring of the status of traffic acquisition and storage devices, ensuring that the monitored traffic data is complete and improving the accuracy of judging device status.
Smart Images

Figure CN116980221B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of cybersecurity, and in particular to methods, apparatuses, devices, and media for traffic monitoring based on cyberspace ranges. Background Technology
[0002] Traffic data is a crucial component for analyzing cybersecurity incidents occurring in cyberspace test ranges. To ensure that traffic is collected accurately and completely, it is necessary to monitor the traffic collection and storage devices to guarantee their proper functioning.
[0003] In existing technologies, network traffic data is typically monitored by tracking the configuration status of traffic acquisition and mirroring devices within a cyberspace range. However, due to the large number of nodes and complex topology in a cyberspace range, even if some acquisition nodes fail or some uplink / downlink networks are blocked, the traffic acquisition devices can still collect traffic data through the remaining nodes and unblocked network connections. Therefore, the traffic data monitored in this way may be incomplete and cannot represent the overall normal status of traffic acquisition and storage devices in the cyberspace range. Consequently, existing traffic monitoring methods cannot accurately reflect whether there are any anomalies in the traffic acquisition and storage devices within a cyberspace range. Summary of the Invention
[0004] This disclosure provides a method, apparatus, device, and medium for traffic monitoring based on a cyberspace range, which can ensure that the monitored data traffic is complete, thereby improving the accuracy of using data traffic to determine the status of traffic acquisition and storage devices.
[0005] According to one aspect of this disclosure, a traffic monitoring method based on a cyberspace range is provided, comprising:
[0006] Retrieve cybersecurity events from the security event database of the cyberspace test range;
[0007] Obtain the characteristic data of the network security incident;
[0008] Based on the feature data, the traffic data corresponding to the network security event is queried in the traffic database of the cyberspace range, wherein the traffic database stores full traffic mirror data of the network security event occurring in the cyberspace range.
[0009] According to one aspect of this disclosure, a traffic monitoring device based on a cyberspace range is provided, comprising:
[0010] The first acquisition unit is used to acquire network security events from the security event database of the cyberspace range.
[0011] The second acquisition unit is used to acquire feature data of the network security event;
[0012] The first query unit is used to query the traffic data corresponding to the network security event in the traffic database of the cyberspace range based on the feature data, wherein the traffic database stores full traffic mirror data of the network security event occurring in the cyberspace range.
[0013] Optionally, the first acquisition unit is specifically used for:
[0014] Determine the monitoring cycle and monitoring duration;
[0015] According to the monitoring cycle, the monitoring time interval is determined based on the monitoring duration;
[0016] A predetermined number of cybersecurity events occurring within the monitoring time interval are randomly selected from the security event database of the cyberspace range.
[0017] Optionally, the feature data includes the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp of the network security event.
[0018] Optionally, the traffic database includes multiple traffic interfaces, each traffic interface corresponding to a network security event; each traffic interface includes a traffic start time, a traffic end time, and a traffic parameter group, the traffic parameter group including a traffic virtual LAN identifier, a traffic source address, a traffic source port, a traffic destination address, and a traffic destination port;
[0019] The first query unit is specifically used for:
[0020] Based on the traffic start time, traffic end time, and timestamp, candidate traffic ports are determined in the traffic database;
[0021] Based on the matching relationship between the source address and the traffic source address, the matching relationship between the source port and the traffic source port, the matching relationship between the destination address and the traffic destination address, the matching relationship between the destination port and the traffic destination port, and the matching relationship between the virtual LAN identifier and the traffic virtual LAN identifier, the target traffic port corresponding to the network security event is determined from the candidate traffic ports;
[0022] The traffic data of the network security event is returned by the target traffic interface.
[0023] Optionally, the network security event includes an event identifier;
[0024] The feature data includes positive feature data and negative feature data;
[0025] The second acquisition unit is specifically used for:
[0026] Based on the event identifier, retrieve the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp of the network security event from the security event database;
[0027] The source address, source port, destination address, destination port, virtual LAN identifier, and timestamp are combined to form the positive feature data;
[0028] Use the target address as the reverse source address, the target port as the reverse source port, the source address as the reverse target address, and the source port as the reverse target port.
[0029] The reverse source address, the reverse source port, the reverse target address, the reverse target port, the virtual LAN identifier, and the timestamp are combined to form the reverse feature data.
[0030] Optionally, the traffic data includes forward traffic data and reverse traffic data;
[0031] The first query unit is specifically used for:
[0032] Based on the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp in the positive feature data, the positive traffic data corresponding to the network security event is determined in the traffic database;
[0033] Based on the reverse source address, reverse source port, reverse target address, reverse target port, virtual LAN identifier, and timestamp in the reverse feature data, the reverse traffic data corresponding to the network security event is determined in the traffic database.
[0034] Optionally, the second acquisition unit is specifically used for:
[0035] The feature data of the network security event is obtained from the fused security event index library in the security event database; the fused security event index library is generated based on multiple network security events in the security event database.
[0036] Optionally, the traffic database obtains the full traffic mirror data of the network security incident through the following process:
[0037] Insert traffic probes at each node of the cyberspace test range;
[0038] When the network security incident occurs, the traffic probe is used to capture the traffic data;
[0039] If the traffic probe captures the traffic data at each node where the network security incident occurs, the traffic data is mirrored and stored in the traffic database to obtain the full traffic mirror data.
[0040] Optionally, the flow monitoring device further includes:
[0041] An alarm initiation unit is used to initiate an alarm event if no traffic data corresponding to the network security event is found.
[0042] The second query unit is used to query the traffic data corresponding to the network security event again in the traffic database after a preset time interval based on the alarm event.
[0043] According to one aspect of this disclosure, an electronic device is provided, including a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the traffic monitoring method as described above.
[0044] According to one aspect of this disclosure, a computer-readable storage medium is provided, the storage medium storing a computer program that, when executed by a processor, implements the traffic monitoring method as described above.
[0045] According to one aspect of this disclosure, a computer program product is provided, comprising a computer program that is read and executed by a processor of a computer device, causing the computer device to perform the traffic monitoring method as described above.
[0046] In this embodiment, network security events are obtained from the security event database of a cyberspace range, and then feature data of these events is acquired. Based on this feature data, traffic data generated during the network security event is queried from the traffic database of the cyberspace range. The traffic database stores fully mirrored traffic data at the time of the network security event. If some nodes in the traffic acquisition device are abnormal, the traffic data cannot be completely acquired and therefore cannot be mirrored and stored in the traffic database. Therefore, the traffic data retrieved from the traffic database based on the data features of the network security event must be the complete traffic data corresponding to the event. If the traffic data generated during the network security event cannot be found in the traffic database based on the feature data, it indicates that some nodes in the traffic acquisition and storage device of the cyberspace range are malfunctioning or a network connection is blocked, requiring immediate inspection and repair. If the traffic data can be retrieved, it indicates that the traffic acquisition and storage device is functioning normally. Therefore, this embodiment ensures that the monitored traffic data is complete, thereby improving the accuracy of using data traffic to determine the status of the traffic acquisition and storage device.
[0047] Other features and advantages of this disclosure will be set forth in the following description and will be apparent in part from the description or may be learned by practicing the disclosure. The objectives and other advantages of this disclosure may be realized and obtained by means of the structures particularly pointed out in the description, claims and drawings. Attached Figure Description
[0048] The accompanying drawings are provided to further understand the technical solutions of this disclosure and constitute a part of the specification. They are used together with the embodiments of this disclosure to explain the technical solutions of this disclosure and do not constitute a limitation on the technical solutions of this disclosure.
[0049] Figure 1 This is an architecture diagram of a traffic monitoring method based on a cyberspace range provided in this embodiment of the present disclosure;
[0050] Figure 2 This is a flowchart of a traffic monitoring method based on a cyberspace range according to an embodiment of this disclosure;
[0051] Figure 3 yes Figure 2 A detailed flowchart of step 210;
[0052] Figure 4 This is an example diagram for determining the monitoring event interval;
[0053] Figure 5 yes Figure 2 A detailed flowchart of step 230;
[0054] Figure 6 yes Figure 2 A detailed flowchart of step 220;
[0055] Figure 7 yes Figure 6 A schematic diagram of positive and negative feature data in a diagram;
[0056] Figure 8 yes Figure 2 A detailed flowchart of step 230;
[0057] Figure 9 This is a flowchart illustrating the process of obtaining full traffic mirror data from a traffic database.
[0058] Figure 10 Is Figure 2 If a specific flowchart of traffic data is not found afterward;
[0059] Figure 11 This is an overall flowchart of an embodiment of this disclosure;
[0060] Figure 12 This is a structural block diagram of the flow monitoring device according to an embodiment of the present disclosure;
[0061] Figure 13 According to embodiments of this disclosure Figure 2 The diagram shows the control terminal structure of the flow monitoring method.
[0062] Figure 14 According to embodiments of this disclosure Figure 2 The server architecture diagram for the traffic monitoring method is shown. Detailed Implementation
[0063] To make the objectives, technical solutions, and advantages of this disclosure clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of this disclosure.
[0064] Before providing a further detailed description of the embodiments of this disclosure, the terms and concepts used in these embodiments are explained, and they are subject to the following interpretations:
[0065] Cyberspace Range: A cyberspace range is a technology or product based on virtualization that simulates and reproduces the operational status and environment of network architecture, system equipment, and business traffic in real open cyberspace. This allows for more effective learning and research related to cybersecurity, thereby improving personnel's cybersecurity adversarial skills and system defense capabilities. By analyzing cybersecurity incidents in the cyberspace range, protection strategies are determined to improve the stability and security of networks in real-world environments.
[0066] Traffic mirroring: Traffic mirroring is a network technology used to replicate network communication in real time to another interface (or multiple interfaces) for analysis and monitoring. Traffic mirroring helps operations and security personnel monitor the stability and security of network devices and applications in real time, and to troubleshoot problems and protect against attacks by analyzing traffic. Furthermore, traffic mirroring does not affect network bandwidth and does not interfere with normal network operation.
[0067] Data acquisition probe: A data acquisition probe is a device used to capture and analyze specified network traffic during network communication. During the capture phase, the probe captures the network traffic passing through it and stores the captured data in memory or on hard drive. During the analysis phase, the probe decodes, reassembles, and filters the captured data to extract useful information.
[0068] Figure 1 This is a system architecture diagram of the traffic monitoring method applied according to embodiments of the present disclosure. It includes: a control terminal and a cyberspace range, wherein the cyberspace range includes a security event database, a traffic database, and traffic acquisition devices.
[0069] A control terminal is a device used to initiate monitoring of cyberspace targets, view monitoring results, and handle abnormal results when they occur. It can take various forms, including desktop computers, laptops, PDAs (personal digital assistants), mobile phones, and dedicated terminals. Furthermore, it can be a single device or a collection of multiple devices. For example, multiple devices connected via a local area network (LAN) can collaborate using a single display device to form a control terminal.
[0070] A cyberspace range is a computer system used by users to conduct cybersecurity attack and defense drills. A cyberspace range can be a single high-performance computer, or a combination of portions of multiple high-performance computers. The security event database within the cyberspace range stores all cybersecurity events that occur within the range. Traffic acquisition devices are used to collect traffic data when cybersecurity events occur, and then mirror the collected traffic data and store it in the traffic database.
[0071] When using a control terminal to monitor traffic in a cyberspace range, it is necessary to use the Network Time Protocol (NTP) to synchronize the time of each computer in the network in order to accurately locate traffic data of cybersecurity incidents.
[0072] According to one embodiment of this disclosure, a traffic monitoring method based on a cyberspace range is provided.
[0073] Traffic monitoring is used to monitor traffic data in cyberspace test ranges. When abnormal traffic data is detected, relevant personnel can promptly identify and rectify the issue, ensuring that the cyberspace test range can accurately collect traffic data and analyze network security incidents. In existing technologies, network traffic data is typically monitored by tracking the configuration status of traffic acquisition and mirroring devices within the cyberspace test range. However, this method cannot guarantee the completeness of the collected traffic data, nor can it guarantee the normal operation of all nodes and connections in the traffic acquisition and storage devices.
[0074] The traffic data collected by the traffic monitoring method according to the embodiments of this disclosure is complete, and therefore can accurately reflect the status of each node and connection in the traffic acquisition and storage device.
[0075] like Figure 2 As shown, the traffic monitoring method of this disclosure includes:
[0076] Step 210: Obtain network security events from the security event database of the cyberspace range;
[0077] Step 220: Obtain characteristic data of network security incidents;
[0078] Step 230: Based on the feature data, query the traffic data corresponding to the network security event in the traffic database of the cyberspace range. The traffic database stores the full traffic mirror data of the network security event occurring in the cyberspace range.
[0079] In step 210, the security event database stores cybersecurity events that occurred in the cyberspace range. After identifying simulated attack and defense events occurring in the cyberspace range using security devices (such as firewalls / intrusion prevention systems / intrusion detection systems), cybersecurity event data is generated through big data computation and stored in the security event database. When a cybersecurity event occurs, corresponding traffic data is generated. Therefore, the status of traffic collection and storage devices in the cyberspace range can be determined using the traffic data at the time of the cybersecurity event.
[0080] In one embodiment, cybersecurity events are obtained from the cyberspace range's security event database in real time.
[0081] Cybersecurity incidents occurring in cyberspace test ranges are often continuous. Therefore, real-time monitoring of traffic data in cyberspace test ranges can be implemented to ensure the continued operation of the system despite these continuous cybersecurity incidents.
[0082] When a cybersecurity incident occurs in the cyberspace test range, the incident is stored in the security incident database, and the traffic data is mirrored and stored in the traffic database. After storage, the cybersecurity incident is retrieved, and steps 220-230 are executed to achieve real-time monitoring of the traffic data.
[0083] Because cyberspace ranges can provide cybersecurity attack and defense training scenarios for multiple targets simultaneously, multiple cybersecurity events may occur within the range at the same time. However, anomalies in traffic acquisition and storage devices can often be detected using only a single cybersecurity event. Monitoring the traffic data for every single cybersecurity event would be wasteful. Therefore, a predetermined number of cybersecurity events can be retrieved from the security event database. This predetermined number is often one, but to avoid inaccuracies from a single monitoring result, it can be set to two or three. Retrieving a predetermined number of cybersecurity events improves the efficiency of real-time monitoring, allowing the real-time status of data acquisition and storage devices to be reflected using fewer cybersecurity events.
[0084] The advantage of using real-time acquisition for data monitoring is that it allows for timely monitoring of the status of traffic data collection and storage, enabling prompt handling of abnormal situations and improving the timeliness of abnormal situation processing.
[0085] Since cyberspace ranges also need to provide computing resources for cybersecurity drills, if traffic monitoring and cybersecurity drills occur simultaneously, it may increase the load on the cyberspace range, thereby affecting the efficiency of the cybersecurity drills. Therefore, in one embodiment, such as Figure 3 As shown, step 210 includes:
[0086] Step 310: Determine the monitoring cycle and monitoring duration;
[0087] Step 320: Determine the monitoring time interval according to the monitoring cycle and monitoring duration;
[0088] Step 330: Randomly select a predetermined number of cybersecurity events that occurred within the monitoring time interval from the cyberspace test range's security event database.
[0089] In this embodiment, traffic is monitored according to a predetermined monitoring cycle, for example, once every hour. The presence of abnormalities in traffic collection and storage devices is determined by analyzing network security events that occur within the monitoring cycle. The monitoring cycle can be preset to a fixed duration, such as 1 hour or 2 hours; alternatively, it can be dynamically adjusted based on the number of network security events occurring in the cyberspace test range. For example, a surge in the number of network security events during a certain period can easily lead to abnormal traffic data collection; therefore, the monitoring cycle can be appropriately shortened to improve the accuracy of traffic monitoring.
[0090] If anomalies exist within the monitoring period, they will persist without human intervention. Therefore, it is unnecessary to acquire cybersecurity events for the entire monitoring period. Instead, the monitoring duration should be determined to capture cybersecurity events within that duration. The monitoring duration can be set to 1 minute, 5 minutes, 10 minutes, 15 minutes, etc., depending on the number of cybersecurity events occurring within the monitoring period. If the number of cybersecurity events occurring within the monitoring period is large, the monitoring duration can be set shorter.
[0091] A monitoring time interval is a period within a monitoring cycle used for traffic monitoring. The traffic monitoring results within this interval reflect the overall traffic monitoring results for the entire monitoring period. The starting point of the monitoring time interval is the time point at which traffic monitoring was performed minus the monitoring duration, and the ending point is the original time point at which traffic monitoring was performed. For example... Figure 4 As shown, the monitoring period is 1 hour, so traffic monitoring needs to be performed at 10:00, 11:00, and 12:00. The monitoring duration is 15 minutes, so at 11:00, the monitoring time interval is from 10:45 to 11:00, and at 12:00, the monitoring time interval is from 11:45 to 12:00. If a data anomaly occurs between 10:00 and 10:45, then the anomaly will still exist during the monitoring time interval from 10:45 to 11:00. Therefore, by monitoring traffic within a small timeframe, the traffic status of the entire monitoring period can be reflected.
[0092] After determining the monitoring time interval, a predetermined number of cybersecurity events occurring within that time interval are randomly selected from the security event database. The predetermined number of random selections depends on the load of the cyberspace testbed. A larger predetermined number results in more accurate monitoring results, but also places a greater load on the system. The predetermined number can be set as a fixed value, such as 10, based on the load of the cyberspace testbed; alternatively, it can be dynamically adjusted based on the number of cybersecurity events currently running in the cyberspace testbed. For example, if there are a large number of cybersecurity events currently running in the cyberspace testbed, the predetermined number should be reduced to ensure that traffic monitoring does not affect the normal operation of cybersecurity events.
[0093] The advantage of this embodiment is that traffic monitoring is performed according to a predetermined cycle, which avoids traffic monitoring from occupying the computing resources required for network security exercises in the cyberspace range and affecting the normal conduct of the exercises.
[0094] In step 220, characteristic data of the network security incident is obtained.
[0095] In one embodiment, obtaining feature data of a cybersecurity event includes: obtaining feature data of the cybersecurity event from a fused security event index library in a security event database.
[0096] The Unified Security Event Index is generated based on multiple cybersecurity events from a security event database. Its role in the cyberspace testbed is to integrate cybersecurity events from different security devices for comprehensive analysis. Therefore, the Unified Security Event Index standardizes the format of multiple fields from different cybersecurity events for fusion. For example, the time formats of cybersecurity events from different security devices may differ; the Unified Security Event Index standardizes these formats and sorts them accordingly. The Unified Security Event Index also performs deduplication and cleanup of cybersecurity events, for example, by using cybersecurity event identifiers or virtual LAN identifiers to determine whether a cybersecurity event is valid. Thus, the data characteristics obtained through the Unified Security Event Index are more accurate and easier to search.
[0097] The main fields of network security events included in the integrated security event index are shown in Table 1:
[0098]
[0099]
[0100] Table 1
[0101] Since each network security event has multiple characteristic data, event identifiers can be used to obtain characteristic data related to traffic data. In one embodiment, the characteristic data includes the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp of the network security event.
[0102] The source address is the IP address of the initiator of the network security incident; the source port is the port number of the initiator of the network security incident; the destination address is the IP address of the recipient of the network security incident; the destination port is the port number of the recipient of the network security incident; the virtual LAN identifier is the identifier of the virtual network isolated in the cyberspace test range; and the timestamp is the time when the network security incident occurred.
[0103] The advantage of obtaining the above feature data from multiple feature data is that the purpose of querying traffic data can be achieved using a small amount of feature data, thus improving query efficiency.
[0104] Based on this embodiment, the traffic database in step 230 contains multiple traffic interfaces, each corresponding to a network security event. Traffic data for the network security event can be obtained through these traffic interfaces. Each traffic interface contains a traffic start time, a traffic end time, and a traffic parameter group. The traffic parameter group includes a traffic virtual LAN identifier, a traffic source address, a traffic source port, a traffic destination address, and a traffic destination port. Therefore, as... Figure 5 As shown, step 230 includes:
[0105] Step 510: Based on the traffic start time, traffic end time, and timestamp, determine the candidate traffic ports in the traffic database;
[0106] Step 520: Based on the matching relationship between source address and traffic source address, source port and traffic source port, destination address and traffic destination address, destination port and traffic destination port, and virtual LAN identifier and traffic virtual LAN identifier, determine the target traffic port corresponding to the network security event from the candidate traffic ports;
[0107] Step 530: The target traffic interface returns traffic data of the network security event.
[0108] In this embodiment, the target traffic interface corresponding to the network security event is determined in the traffic database based on the acquired feature data of the network security event. The type of traffic interface can be a RESTful API. The data content of the request header of the traffic interface is shown in Table 2:
[0109]
[0110] The data content of the request body of the traffic interface in Table 2 is shown in Table 3:
[0111]
[0112]
[0113] Table 3
[0114] The request header of the traffic interface contains the data information of the traffic interface and cannot be used to query traffic data that can be retrieved through the traffic interface. The request body contains the traffic data that can be retrieved through the traffic interface; therefore, the traffic interface is queried through the request body.
[0115] First, candidate traffic ports are determined by comparing the traffic start time and end time in the request body data with the timestamp in the network security event's characteristic data. If the network security event occurs between the traffic start time and end time, it means that the traffic data that the traffic interface can retrieve matches the time of the network security event. Then, the target traffic interface is selected from the time-matching candidate traffic interfaces. It is important to note that the time formats of the traffic start time, traffic end time, and timestamp must be consistent for comparison.
[0116] In the request body of Table 2, “filterTupleArray” is the traffic parameter group, where “vlanId” is the traffic virtual LAN identifier; “sourceIp” is the traffic source address; “destIp” is the traffic destination address; “sourcePort” is the traffic source port; and “destPort” is the traffic destination port.
[0117] Only when the VLAN ID and traffic VLAN ID are the same, the source address and traffic source address are the same, the destination address and traffic destination address are the same, the source port and traffic source port are the same, and the destination port and traffic destination port are equal in the characteristic data of a network security event, can it be said that the traffic data corresponding to this traffic interface is the traffic data of a network security event, and the traffic interface is the target traffic port corresponding to the network security event.
[0118] After locating the target traffic interface, the target traffic interface returns the traffic data of the network security event. The returned results are shown in Table 4:
[0119] Serial Number Parameter name type illustrate 1 Code Integer Check the task status; 0 indicates success, 1 indicates failure. 2 Msg String If the task fails, a failure message will be returned. 3 totalBytes String Total bytes of query traffic data 4 totalPackets Integer Query the total number of data packets in the traffic data.
[0120] Table 4
[0121] In Table 4, the parameter "Code" indicates whether the target traffic interface was found. It is 0 if successful and 1 if unsuccessful, and the failure information is returned via the parameter "Msg". "totalBytes" and "totalPackets" represent the total number of bytes and total number of packets of traffic data found. If these two parameters are not 0, it means that the traffic acquisition and storage device of the network space range is in normal status; otherwise, if either of these two parameters is 0, it means that the traffic acquisition and storage device of the network space range is in abnormal status.
[0122] The advantage of using the traffic interface to query traffic data in this embodiment is that it reduces the server load caused by directly querying traffic data, improves the search efficiency, and improves data security and accuracy by not directly manipulating the traffic data.
[0123] Network security incidents occur using unidirectional traffic transmission from sender to receiver. In practical applications, it's possible that traffic collection from sender to receiver is normal, but traffic collection from receiver to sender is blocked. Using another network security incident to verify the receiver-to-sender traffic collection status would unnecessarily increase the load on the cyberspace testbed. Therefore, in one embodiment, the network security incident includes an event identifier, and the feature data in step 220 includes forward feature data and reverse feature data. Forward feature data is the sender-to-receiver feature data of the network security incident; reverse feature data is the receiver-to-sender feature data of the network security incident. Based on this, as... Figure 6 As shown, step 220 includes:
[0124] Step 610: Retrieve the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp of the network security event from the security event database based on the event identifier;
[0125] Step 620: Combine the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp into positive feature data;
[0126] Step 630: Use the target address as the reverse source address, the target port as the reverse source port, the source address as the reverse target address, and the source port as the reverse target port.
[0127] Step 640: Combine the reverse source address, reverse source port, reverse target address, reverse target port, virtual LAN identifier, and timestamp into reverse feature data.
[0128] Referring to Table 1, the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp of a network security event can be obtained through the event identifier. These are positive characteristic data from the sender to the receiver.
[0129] Use the target address as the source address for reverse engineering, the target port as the source port for reverse engineering, and the source address as the target address for reverse engineering, and the source port as the target port for reverse engineering. For example... Figure 7 As shown, in this process, the forward sender is treated as the reverse receiver, and the forward receiver is treated as the reverse sender. The converted feature data is combined with the virtual LAN identifier and timestamp to obtain the reverse feature data.
[0130] The advantage of this embodiment is that it uses a network security event to obtain bidirectional feature data to obtain bidirectional traffic characteristics, ensuring the integrity of traffic data query and improving monitoring efficiency.
[0131] Based on this embodiment, the traffic data includes forward traffic data and reverse traffic data; therefore, as Figure 8As shown, step 230 includes:
[0132] Step 810: Based on the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp in the positive feature data, determine the positive traffic data corresponding to the network security event in the traffic database;
[0133] Step 820: Based on the reverse source address, reverse source port, reverse target address, reverse target port, virtual LAN identifier, and timestamp in the reverse feature data, determine the reverse traffic data corresponding to the network security event in the traffic database.
[0134] In this embodiment, based on positive feature data, traffic data from the forward sender to the forward receiver can be obtained from the traffic database, and based on negative feature data, traffic data from the reverse sender to the reverse receiver can be obtained.
[0135] The process of determining forward traffic data in the traffic database based on the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp is the same as in the previous embodiment, and will not be repeated here.
[0136] The advantages of this embodiment are the same as those of obtaining bidirectional feature data in the previous embodiments, and will not be repeated here.
[0137] Because the traffic database stores full traffic mirror data of cybersecurity incidents occurring in the cyberspace test range, it can ensure that the traffic data retrieved from the traffic database is the complete traffic of the cybersecurity incident.
[0138] In one embodiment, such as Figure 9 As shown, the traffic database obtains full traffic mirror data of network security incidents through the following process:
[0139] Step 910: Insert traffic probes at each node of the cyberspace test range;
[0140] Step 920: When a network security incident occurs, use traffic probes to capture traffic data;
[0141] Step 930: If the traffic probe captures traffic data at each node where the network security incident occurs, mirror the traffic data and store it in the traffic database to obtain full traffic mirror data.
[0142] In this embodiment, traffic probes are inserted into each node of the cyberspace range to capture traffic data. When a cybersecurity incident occurs, the traffic probes of all nodes through which the incident occurs are treated as a whole. Only when all these traffic probes capture traffic data can the traffic data be mirrored and stored in the traffic database to obtain full traffic mirror data. If even one traffic probe fails to capture traffic data, full traffic mirror data cannot be formed in the traffic database.
[0143] This is precisely why it can be ensured that the traffic data retrieved from the traffic database represents the complete traffic of a cybersecurity incident. Therefore, this implementation ensures the integrity of the traffic data stored in the traffic database.
[0144] If traffic data for a cybersecurity incident is found in the traffic database, it indicates that the traffic collection and storage devices are functioning normally, and traffic monitoring for the next cybersecurity incident can proceed.
[0145] If no network security event traffic data is found in the traffic database, it indicates that the traffic collection and storage device is in an abnormal state and needs to be processed.
[0146] In one embodiment, such as Figure 10 As shown, after step 230, the flow monitoring method further includes:
[0147] Step 1010: If no traffic data corresponding to the network security incident is found, initiate an alarm event;
[0148] Step 1020: Based on the alarm event, query the traffic data corresponding to the network security event again in the traffic database after a preset time interval.
[0149] If no traffic data is found, the abnormal traffic characteristics are sent to the automatic abnormal handling platform through the abnormal handling interface for further processing.
[0150] Upon receiving an alarm event, the automated anomaly handling platform queries the traffic database for the corresponding network security event's traffic data after a preset time interval. This is to prevent a storage time lag between the traffic database and the security event database—that is, the security event database may already contain the network security event, but the traffic database may not yet contain the corresponding traffic data. Therefore, after the preset time, a second query will retrieve the traffic data. If the data is found, it indicates that the traffic collection and storage devices are functioning normally; if the data is still not found, it indicates an anomaly requiring repair.
[0151] The advantage of this embodiment is that it avoids the problem of not being able to find traffic data due to storage time difference, thus improving the accuracy of traffic monitoring.
[0152] Handling abnormal states requires obtaining information about the network security events that generated the alarms, the simulated network areas, and the traffic collection and storage devices. By checking this information, anomalies are identified, and specific problems are repaired according to predetermined methods, with logs recorded. If the anomaly cannot be repaired or no anomaly is found, the alarm should be notified to the relevant personnel via SMS or email, allowing for manual intervention to check the information, determine the cause of the anomaly, and resolve the problem.
[0153] The overall flow of the traffic monitoring method in this embodiment is as follows: Figure 11 As shown, the process involves: retrieving network security events from the security event database; obtaining the characteristic data of the network security events; querying the traffic data of the network security events in the traffic database based on the characteristic data; determining whether traffic data is found; if so, retrieving the next network security event for traffic monitoring; if not, initiating an alarm event, with the automatic anomaly handling platform and relevant personnel investigating the cause of the alarm and fixing the anomaly; and retrieving network security events for traffic monitoring again after the anomaly is fixed.
[0154] The apparatus and device according to embodiments of this disclosure will now be described.
[0155] It is understood that although the steps in the above flowcharts are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated in this embodiment, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the above flowcharts may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps.
[0156] It should be noted that in various specific embodiments of this application, when processing is required based on data related to the characteristics of the target virtual machine, such as target virtual machine attribute information or attribute information sets, the permission or consent of the target virtual machine will be obtained first. Furthermore, the collection, use, and processing of this data will comply with the relevant laws, regulations, and standards of the relevant countries and regions. In addition, when embodiments of this application need to obtain target virtual machine attribute information, separate permission or consent from the target virtual machine will be obtained through pop-up windows or redirection to a confirmation page. Only after obtaining the separate permission or consent of the target virtual machine will the necessary target virtual machine-related data for the normal operation of the embodiments of this application be obtained.
[0157] Figure 12 A structural diagram of a flow monitoring device 1200 provided in an embodiment of this disclosure. The flow monitoring device 1200 includes:
[0158] The first acquisition unit 1210 is used to acquire network security events from the security event database of the cyberspace range.
[0159] The second acquisition unit 1220 is used to acquire feature data of network security events;
[0160] The first query unit 1230 is used to query the traffic data corresponding to the network security event in the traffic database of the cyberspace range based on the feature data. The traffic database stores the full traffic mirror data of the network security event occurring in the cyberspace range.
[0161] Optionally, the first acquisition unit 1210 is specifically used for:
[0162] Determine the monitoring cycle and monitoring duration;
[0163] The monitoring time interval is determined according to the monitoring cycle and the monitoring duration;
[0164] A predetermined number of cybersecurity events that occurred within a monitoring time period are randomly selected from the cyberspace test range's security event database.
[0165] Optionally, the feature data includes the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp of the network security incident.
[0166] Optionally, the traffic database contains multiple traffic interfaces, each corresponding to a network security event; each traffic interface contains a traffic start time, a traffic end time, and a traffic parameter group, which contains a traffic virtual LAN identifier, a traffic source address, a traffic source port, a traffic destination address, and a traffic destination port.
[0167] The first query unit 1230 is specifically used for:
[0168] Candidate traffic ports are determined based on the traffic start time, traffic end time, and timestamp;
[0169] Based on the matching relationships between source address and traffic source address, source port and traffic source port, destination address and traffic destination address, destination port and traffic destination port, and virtual LAN identifier and traffic virtual LAN identifier, the target traffic port corresponding to the network security event is determined from the candidate traffic ports.
[0170] Traffic data of network security events is returned from the target traffic interface.
[0171] Optionally, a cybersecurity incident may include an event identifier;
[0172] Feature data includes positive feature data and negative feature data;
[0173] The second acquisition unit 1220 is specifically used for:
[0174] Based on the event identifier, retrieve the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp of the network security event from the security event database;
[0175] The source address, source port, destination address, destination port, virtual LAN identifier, and timestamp are combined to form positive feature data;
[0176] Use the target address as the reverse source address, the target port as the reverse source port, the source address as the reverse target address, and the source port as the reverse target port.
[0177] The reverse source address, reverse source port, reverse target address, reverse target port, virtual LAN identifier, and timestamp are combined to form reverse feature data.
[0178] Optionally, the traffic data includes both forward traffic data and reverse traffic data;
[0179] The first query unit 1230 is specifically used for:
[0180] Based on the source address, source port, destination address, destination port, virtual LAN identifier, and timestamp in the positive feature data, the positive traffic data corresponding to the network security event is determined in the traffic database;
[0181] Based on the reverse source address, reverse source port, reverse target address, reverse target port, virtual LAN identifier, and timestamp in the reverse feature data, the reverse traffic data corresponding to the network security event is determined in the traffic database.
[0182] Optionally, the second acquisition unit 1220 is specifically used for:
[0183] Feature data of cybersecurity events are obtained from the fused security event index in the security event database; the fused security event index is generated based on multiple cybersecurity events in the security event database.
[0184] Optionally, the traffic database obtains full traffic mirror data of network security incidents through the following process:
[0185] Insert traffic probes at various nodes in the cyberspace test range;
[0186] Traffic probes are used to capture traffic data when a cybersecurity incident occurs.
[0187] If traffic probes capture traffic data at each node where a cybersecurity incident occurs, the traffic data can be mirrored and stored in a traffic database to obtain full traffic mirror data.
[0188] Optionally, the flow monitoring device 1200 also includes:
[0189] An alarm initiation unit (not shown) is used to initiate an alarm event if no traffic data corresponding to a network security event is found.
[0190] The second query unit (not shown) is used to query the traffic data corresponding to the network security event again in the traffic database after a preset time interval based on the alarm event.
[0191] Reference Figure 13 , Figure 13 To implement the structural block diagram of the control terminal in this embodiment of the present disclosure, the control terminal includes: a radio frequency (RF) circuit 1310, a memory 1315, an input unit 1330, a display unit 1340, a sensor 1350, an audio circuit 1360, a wireless fidelity (WiFi) module 1370, a processor 1380, and a power supply 1390, etc. Those skilled in the art will understand that... Figure 13 The terminal structure shown does not constitute a limitation on mobile phones or computers and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0192] The RF circuit 1310 can be used to receive and transmit signals during information transmission or calls. In particular, it receives downlink information from the base station and processes it with the processor 1380; in addition, it transmits uplink data to the base station.
[0193] The memory 1315 can be used to store software programs and modules. The processor 1380 executes various terminal functions and data processing by running the software programs and modules stored in the memory 1315.
[0194] The input unit 1330 can be used to receive input numeric or character information, and to generate key signal inputs related to the terminal's settings and function control. Specifically, the input unit 1330 may include a touch panel 1331 and other input devices 1332.
[0195] Display unit 1340 can be used to display input or provided information, as well as various menus of the terminal. Display unit 1340 may include display panel 1341.
[0196] Audio circuitry 1360, speaker 1361, and microphone 1362 provide an audio interface.
[0197] In this embodiment, the processor 1380 included in the terminal can execute the traffic monitoring method of the previous embodiment.
[0198] The control terminals disclosed in this embodiment include, but are not limited to, mobile phones, computers, intelligent voice interaction devices, and aircraft. The embodiments of this invention can be applied to various scenarios, including but not limited to network security and communication security.
[0199] Figure 14 This is a partial structural block diagram of a server for a cyberspace range implementing embodiments of the present disclosure. The server can vary significantly due to different configurations or performance, and may include one or more Central Processing Units (CPUs) 1422 (e.g., one or more processors) and memory 1432, and one or more storage media 1430 (e.g., one or more mass storage devices) for storing application programs 1442 or data 1444. The memory 1432 and storage media 1430 may be temporary or persistent storage. The program stored in the storage media 1430 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the server. Furthermore, the CPU 1422 may be configured to communicate with the storage media 1430 and execute the series of instruction operations in the storage media 1430 on the server.
[0200] The server may also include one or more power supplies 1426, one or more wired or wireless network interfaces 1450, one or more input / output interfaces 1458, and / or one or more operating systems 1441, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.
[0201] The central processing unit 1422 in the server can be used to execute the traffic monitoring method of the present disclosure embodiments.
[0202] This disclosure also provides a computer-readable storage medium for storing program code for executing the traffic monitoring methods of the foregoing embodiments.
[0203] This disclosure also provides a computer program product comprising a computer program. A processor of a computer device reads and executes the computer program, causing the computer device to perform the traffic monitoring method described above.
[0204] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in this disclosure and the foregoing drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “including,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatuses.
[0205] It should be understood that in this disclosure, "at least one item" means one or more, and "more than one" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0206] It should be understood that in the description of the embodiments disclosed herein, "multiple" means two or more, "greater than", "less than", "exceeding" etc. are understood to exclude the number itself, and "above", "below", "within" etc. are understood to include the number itself.
[0207] In the several embodiments provided in this disclosure, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.
[0208] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0209] Furthermore, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0210] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0211] It should also be understood that the various implementation methods provided in this disclosure can be combined arbitrarily to achieve different technical effects.
[0212] The above is a detailed description of the embodiments of this disclosure. However, this disclosure is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this disclosure. All such equivalent modifications or substitutions are included within the scope defined by the claims of this disclosure.
Claims
1. A traffic monitoring method based on a cyberspace range, characterized in that, include: Retrieve cybersecurity events from the security event database of the cyberspace range, wherein the cybersecurity events include event identifiers; Obtain feature data of the network security event, the feature data including positive feature data and negative feature data; Based on the feature data, the traffic data corresponding to the network security event is queried in the traffic database of the cyberspace range. The traffic database stores full traffic mirror data of the network security event occurring in the cyberspace range, and the traffic data includes forward traffic data and reverse traffic data. The step of obtaining the feature data of the network security event includes: retrieving the source address, source port, target address, target port, virtual LAN identifier, and timestamp of the network security event from the security event database based on the event identifier; combining the source address, source port, target address, target port, virtual LAN identifier, and timestamp to form the forward feature data; using the target address as the reverse source address, the target port as the reverse source port, the source address as the reverse target address, and the source port as the reverse target port; and combining the reverse source address, reverse source port, reverse target address, reverse target port, virtual LAN identifier, and timestamp to form the reverse feature data. The step of querying the traffic data corresponding to the network security event in the traffic database of the cyberspace range based on the feature data includes: determining the forward traffic data corresponding to the network security event in the traffic database based on the source address, source port, target address, target port, virtual LAN identifier, and timestamp in the forward feature data; and determining the reverse traffic data corresponding to the network security event in the traffic database based on the reverse source address, reverse source port, reverse target address, reverse target port, virtual LAN identifier, and timestamp in the reverse feature data. The traffic database obtains the full traffic mirror data of the network security event through the following process: inserting traffic probes at each node of the cyberspace range; capturing the traffic data using the traffic probes when the network security event occurs; if the traffic probes capture the traffic data at each node where the network security event occurs, mirroring the traffic data and storing it in the traffic database to obtain the full traffic mirror data.
2. The flow monitoring method according to claim 1, characterized in that, The step of obtaining cybersecurity events from the security event database of the cyberspace range includes: Determine the monitoring cycle and monitoring duration; According to the monitoring cycle, the monitoring time interval is determined based on the monitoring duration; A predetermined number of cybersecurity events occurring within the monitoring time interval are randomly selected from the security event database of the cyberspace range.
3. The flow monitoring method according to claim 1, characterized in that, The traffic database contains multiple traffic interfaces, each of which corresponds to a network security event; each traffic interface contains a traffic start time, a traffic end time, and a traffic parameter group, the traffic parameter group containing a traffic virtual LAN identifier, a traffic source address, a traffic source port, a traffic destination address, and a traffic destination port; The step of querying the traffic data corresponding to the network security event in the traffic database of the cyberspace range based on the feature data includes: Based on the traffic start time, traffic end time, and timestamp, candidate traffic interfaces are determined in the traffic database; Based on the matching relationship between the source address and the traffic source address, the matching relationship between the source port and the traffic source port, the matching relationship between the destination address and the traffic destination address, the matching relationship between the destination port and the traffic destination port, and the matching relationship between the virtual LAN identifier and the traffic virtual LAN identifier, the target traffic interface corresponding to the network security event is determined from the candidate traffic interfaces. The traffic data of the network security event is returned by the target traffic interface.
4. The flow monitoring method according to claim 1, characterized in that, The acquisition of the feature data of the network security event includes: The feature data of the network security event is obtained from the fused security event index library in the security event database; the fused security event index library is generated based on multiple network security events in the security event database.
5. The flow monitoring method according to claim 1, characterized in that, After querying the traffic data corresponding to the network security event in the traffic database of the cyberspace range based on the feature data, the traffic monitoring method further includes: If no traffic data corresponding to the network security incident is found, an alarm event is initiated. Based on the alarm event, the traffic data corresponding to the network security event is queried again in the traffic database after a preset time interval.
6. A traffic monitoring device based on a cyberspace range, characterized in that, include: The first acquisition unit is configured to acquire cybersecurity events from the security event database of the cyberspace range, wherein the cybersecurity events include event identifiers; The second acquisition unit is used to acquire feature data of the network security event, the feature data including forward feature data and reverse feature data; wherein, acquiring the feature data of the network security event includes: retrieving the source address, source port, target address, target port, virtual LAN identifier, and timestamp of the network security event from the security event database according to the event identifier; combining the source address, source port, target address, target port, virtual LAN identifier, and timestamp to form the forward feature data; using the target address as the reverse source address, the target port as the reverse source port, the source address as the reverse target address, and the source port as the reverse target port; combining the reverse source address, reverse source port, reverse target address, reverse target port, virtual LAN identifier, and timestamp to form the reverse feature data; The first query unit is used to query the traffic data corresponding to the network security event in the traffic database of the network space range based on the feature data. The traffic database stores the full traffic mirror data of the network security event occurring in the network space range, and the traffic data includes forward traffic data and reverse traffic data. The step of querying the traffic data corresponding to the network security event in the traffic database of the cyberspace range based on the feature data includes: determining the forward traffic data corresponding to the network security event in the traffic database based on the source address, source port, target address, target port, virtual LAN identifier, and timestamp in the forward feature data; and determining the reverse traffic data corresponding to the network security event in the traffic database based on the reverse source address, reverse source port, reverse target address, reverse target port, virtual LAN identifier, and timestamp in the reverse feature data. The traffic database obtains the full traffic mirror data of the network security event through the following process: inserting traffic probes at each node of the cyberspace range; capturing the traffic data using the traffic probes when the network security event occurs; if the traffic probes capture the traffic data at each node where the network security event occurs, mirroring the traffic data and storing it in the traffic database to obtain the full traffic mirror data.
7. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the traffic monitoring method according to any one of claims 1 to 5.
8. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the traffic monitoring method according to any one of claims 1 to 5.
9. A computer program product comprising a computer program that is read and executed by a processor of a computer device, causing the computer device to perform the traffic monitoring method according to any one of claims 1 to 5.
Citation Information
Patent Citations
Network system event tracing method and system based on log and flow collection
CN110392039A
