Threat event sourcing method and related device

By carrying the device identifier of the SDP client in the service message, the accurate traceability of threat events is achieved to specific users, the problem of difficulty in tracing security risks in NAT scenarios is solved, and the traceability accuracy and competitiveness of solutions are improved.

WO2024234861A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD

Patent Information

Application Number
PCT/CN2024/086045
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-16
Filing Date
2024-04-03
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In the NAT scenario, it is difficult for the existing technology to accurately trace network threat events to specific users, resulting in the firewall or gateway being blocked based on IP addresses, resulting in large-scale users being unable to access the network.

Method used

By carrying the device identifier of the SDP client in the service message, the data analysis device can obtain the corresponding user identifier from the user information table of the SDP controller, thereby achieving accurate traceability of threat events to specific users.

Benefits of technology

Improve the traceability accuracy of threat incidents, solve the problem of inability to trace security risks in NAT scenarios, reduce the workload of data analysis equipment, and improve the competitiveness and stickiness of solutions without increasing customer budget costs. .

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024086045_21112024_PF_FP_ABST
    Figure CN2024086045_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the field of network security, and in particular to a threat event sourcing method and a related device. The method comprises: when determining that there is a security risk in a service packet generated by an SDP client accessing an application server, a data analysis device generates, according to sourcing data of the service packet, a threat event carrying a device identifier of the SDP client; and the data analysis device obtains, according to the device identifier of the SDP client, a user identifier corresponding to the device identifier of the SDP client, wherein the user identifier is used for indicating a user corresponding to the threat event. By using the solution of the present application, the sourcing of a threat event can be achieved, and the sourcing can be done to a specific user.
Need to check novelty before this filing date? Find Prior Art

Description

Threat event tracing methods and related equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 16, 2023, with application number 202310553333.6 and invention name “Threat Event Tracing Method and Related Equipment”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of network security, and in particular to a threat event tracing method and related equipment. Background Art

[0003] The security big data analysis platform is centered on information security incidents. Through real-time collection, monitoring and analysis of network traffic, security device logs, threat information and other data information, it can achieve network risk identification, threat discovery, real-time alerts and visual display of security incidents. When a security threat is detected or a notification or warning of a related network security incident is received, the system can quickly notify the threat source and conduct closed-loop disposal to avoid major impacts and losses.

[0004] After a terminal device connects to the network, its Internet Protocol (IP) address may undergo one or more levels of Network Address Translation (NAT). When a security big data analysis platform detects a threat, it can only report the NATed IP address. This widespread notification cannot be linked to a specific computer or individual. If the threat requires action, firewalls or gateways can only directly block it based on the IP address, preventing a large number of users from accessing the network.

[0005] The current source tracing solution for NAT scenarios involves analyzing logs from network devices performing NAT (such as firewall and router NAT translation logs) to ultimately trace the source. Customers deploy log servers to collect NAT translation logs, which include information such as time, source IP address, source port, and post-NAT source IP and port. The log server queries the NAT translation logs based on the time and IP address of the reported threat event for source tracing analysis.

[0006] Accurately tracing the source of an incident based on NAT translation logs requires complete NAT logs, consistent clocks across all levels of network equipment performing NAT translation, and consistent timing for threat event analysis and security big data. Because existing networks often employ multiple levels of NAT, from home routers to gateways, standardizing NAT translation log formats is difficult, and some home routers may not even be able to store and upload NAT translation logs. Tracing the source of a threat incident requires combining logs from every session access to the pre-translation IP address. If logs are incomplete or timelines are inconsistent, tracing the source to a specific user is difficult.

[0007] Summary of the Invention

[0008] The embodiments of the present application provide a threat event tracing method and related equipment. By using the embodiments of the present application, the threat event can be traced back to a specific user.

[0009] In the first aspect, an embodiment of the present application provides a threat event tracing method. The method is applied to a data analysis device. The data analysis device obtains the traceability data of the business message, which is the message generated when the software defined perimeter (SDP) client accesses the application server. Among them, the traceability data of the business message includes the device identifier of the SDP client. When there is a security risk in the business message, the data analysis device generates a threat event carrying the device identifier of the SDP client based on the traceability data of the business message. The data analysis device obtains the user identifier corresponding to the device identifier of the SDP client from the user information table of the SDP controller based on the device identifier of the SDP client, and the user identifier is used to indicate the user corresponding to the threat event. The user information table includes the correspondence between the device identifier of the SDP client and the user identifier.

[0010] By carrying the device identification of the SDP client in the traceability data of the business message, the data analysis device can obtain the user identification corresponding to the device identification of the SDP client from the user information table of the SDP controller based on the device identification of the SDP client when there is a security risk in the business message. The user identification indicates the user corresponding to the threat event. In other words, the generation of the threat event is related to the user indicated by the user identification, which realizes the tracing of the threat event and traces it to a specific user, thereby improving the accuracy of tracing.

[0011] In conjunction with the first aspect, in one possible implementation, the traceability data of the service message is metadata of the service message, the metadata of the service message is generated by a network device based on the service message, and the data analysis device analyzes the metadata of the service message according to a first security detection rule to determine whether the service message presents a first security risk. The security risk includes the first security risk.

[0012] Optionally, the first security risk is a risk identified by the data analysis device based on metadata of business messages, such as a zero-day threat or other security risk. By analyzing metadata from a large number of probes, the data analysis device may be able to discover new risks that cannot be identified by existing rules based on message features.

[0013] In conjunction with the first aspect, in one possible implementation, the traceability data of the service message is threat log data, which is generated by the network device when determining that the service message has a second security risk.

[0014] Optionally, the second security risk is a security risk detected by network devices such as firewalls and security gateways through intrusion prevention systems (IPS), deep packet inspection (DPI), file scanning, etc., for example, business messages carry virus files or other security risks.

[0015] In this implementation, by performing security checks on business messages through network equipment, it is possible to determine whether the business messages pose a second security risk; there is no need for data analysis equipment to perform security checks on business messages to determine whether the business messages pose a second security risk, thereby reducing the workload of the data analysis equipment.

[0016] In conjunction with the first aspect, in one possible implementation, the data analysis device obtains the user identifier corresponding to the device identifier of the SDP client in the following manner:

[0017] The data analysis device sends a query request to the SDP controller, which carries the device identifier of the SDP client. The query request is used by the SDP controller to query the user information table to obtain the first user identifier corresponding to the device identifier of the SDP client; the data analysis device receives a response message fed back by the SDP controller in response to the query request, which carries the first user identifier corresponding to the device identifier of the SDP client.

[0018] In combination with the first aspect, in a possible implementation, the user information table also includes a correspondence between the first user identifier and the authentication timestamp. The authentication timestamp is the moment when the user indicated by the first user identifier passes the authentication. When the response message includes multiple first user identifiers, the response message also includes the authentication timestamps corresponding to the multiple first user identifiers. The data analysis device also obtains the second user identifier from the multiple first user identifiers based on the sending time period of the business message and the authentication timestamps corresponding to the multiple first user identifiers.

[0019] Among them, the second user identifier is the first user identifier among the multiple first user identifiers whose authentication timestamp belongs to the sending period; the sending period is determined according to the moment when the data analysis device receives the traceability data.

[0020] By introducing the sending period and the authentication timestamp corresponding to the first user identifier, the data analysis device can select the second user identifier from multiple first user identifiers, narrowing the tracing scope and thus improving the accuracy of the tracing result.

[0021] In a second aspect, an embodiment of the present application provides another threat event tracing method. This method is applied to a network device. The network device receives a service message, which is generated when an SDP client accesses an application server. The service message carries the device identifier of the SDP client. The network device performs a security check on the service message according to a second security rule to determine whether the service message poses a second security risk. If it is determined that the service message poses a second security risk, the network device generates threat log data that carries the device identifier of the SDP client. The network device sends the threat log data to a data analysis device.

[0022] The network device sends threat log data to the data analysis device, enabling the data analysis device to determine, based on the threat log data, that a service message sent by the SDP client presents the second security risk and generate a threat event that includes the device identifier of the SDP client. Furthermore, the data analysis device can determine the user information corresponding to the threat event based on the device identifier of the SDP client in the threat log data, thereby tracing the threat event. Furthermore, the data analysis device does not need to perform security checks on the service message to determine whether the service message presents the second security risk, reducing the workload of the data analysis device.

[0023] Optionally, the network device is an SDP proxy gateway or a probe device.

[0024] In combination with the first aspect, in a possible implementation, the service message is a transmission control protocol (TCP) message or a tunnel message.

[0025] In a third aspect, an embodiment of the present application provides a data analysis device, which includes an acquisition unit, a generation unit, and a transceiver unit.

[0026] An acquisition unit is used to acquire traceability data of a service message, where the service message is a message generated when the SDP client accesses the application server. The traceability data of the service message includes a device identifier of the SDP client;

[0027] A generating unit, configured to generate a threat event carrying a device identifier of the SDP client based on the traceability data of the service message when a security risk exists in the service message;

[0028] The transceiver unit is configured to obtain a first user identifier corresponding to the device identifier of the SDP client from a user information table of the SDP controller according to the device identifier of the SDP client, wherein the first user identifier is used to indicate a user corresponding to the threat event, and the user information table includes a correspondence between the device identifier of the SDP client and the first user identifier.

[0029] In conjunction with the third aspect, in one possible implementation, the security risk includes a first security risk, the traceability data of the service message is metadata of the service message, the metadata of the service message is generated by the probe device based on the service message, and the data analysis device further includes:

[0030] The analyzing unit is configured to analyze metadata of the service message according to a first security detection rule to determine whether the service message has a first security risk.

[0031] In combination with the third aspect, in one possible implementation, the security risk includes a second security risk, and the traceability data of the business message is threat log data, which is generated by the network device when it determines that the business message has a second security risk.

[0032] In conjunction with the third aspect, in one possible implementation, the transceiver unit is specifically configured to:

[0033] A query request is sent to the SDP controller, the query request carries the device identifier of the SDP client, and the query request is used by the SDP controller to query the user information table to obtain the first user identifier corresponding to the device identifier of the SDP client; and a response message in response to the query request is received from the SDP controller, the response message carries the first user identifier corresponding to the device identifier of the SDP client.

[0034] In conjunction with the third aspect, in one possible implementation, the user information table further includes a correspondence between the first user identifier and the authentication timestamp, where the authentication timestamp is the moment when the user indicated by the first user identifier passes authentication. When the response message includes multiple first user identifiers, the response message further includes the authentication timestamps corresponding to the multiple first user identifiers, respectively. The acquiring unit is further configured to:

[0035] A second user identifier is obtained from multiple first user identifiers according to the sending period of the business message and the authentication timestamps corresponding to the multiple first user identifiers; wherein, the second user identifier is the first user identifier among the multiple first user identifiers whose authentication timestamp belongs to the sending period; the sending period is determined according to the moment when the data analysis device receives the traceability data of the business message.

[0036] In a fourth aspect, an embodiment of the present application provides a network device, comprising a transceiver unit, a detection unit, and a generation unit.

[0037] The transceiver unit is used to receive service messages. The service messages are messages generated when the SDP client accesses the application server. The service messages carry the device identifier of the SDP client.

[0038] a detection unit, configured to perform a security detection on the service message according to the second security rule to determine whether the service message has a second security risk;

[0039] a generating unit, configured to generate threat log data carrying a device identifier of the SDP client if it is determined that the service message has a second security risk;

[0040] The transceiver unit is also used to send threat log data to the data analysis device.

[0041] Optionally, the network device is an SDP proxy gateway or a probe device.

[0042] In conjunction with the third aspect, in a possible implementation, the service message is a TCP message or a tunnel message.

[0043] In a fifth aspect, embodiments of the present application provide a data analysis device comprising a processor and a memory. The memory is configured to store program code. The processor is configured to invoke the program code stored in the memory to execute the method provided in the first aspect or any possible implementation of the first aspect.

[0044] In a sixth aspect, an embodiment of the present application provides a network device comprising a processor and a memory. The memory is configured to store program code. The processor is configured to invoke the program code stored in the memory to execute the method provided in the second aspect or any possible implementation of the second aspect.

[0045] In the seventh aspect, an embodiment of the present application provides a computer storage medium, including computer instructions. When the computer instructions are run on an electronic device, the electronic device executes the method provided in any possible implementation of the first aspect, or the method provided in any possible implementation of the second aspect.

[0046] In an eighth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a computer, it enables the computer to execute the method provided in any possible implementation of the first aspect, or the method provided in any possible implementation of the second aspect.

[0047] In a ninth aspect, an embodiment of the present application provides a threat event tracing system, including a data analysis device, a network device, an SDP client, and an SDP controller;

[0048] The data analysis device is used to perform the method according to any one of the first aspects;

[0049] The network device is used to execute the method according to any one of the second aspects;

[0050] The SDP controller is used to receive a query request sent by a data analysis device, the query request carrying the device identifier of the SDP client; query the user information table according to the device identifier of the SDP client to obtain a first user identifier corresponding to the device identifier of the SDP client; send a response message in response to the query request to the data analysis device, the response message carrying the first user identifier corresponding to the device identifier of the SDP client; the user information table includes a correspondence between the device identifier of the SDP client and the first user identifier.

[0051] By introducing the user information table, the SDP controller determines the user ID corresponding to the SDP client's device ID based on the SDP client's device ID, thereby tracing the threat event to a specific user, thereby improving the accuracy of tracing.

[0052] In conjunction with the ninth aspect, in one possible implementation, the user information table further includes a correspondence between the first user identifier and an authentication timestamp, where the authentication timestamp is the time when the user indicated by the first user identifier passes authentication; and the SDP controller is further configured to:

[0053] When there are multiple first user identifiers, the user information table is queried according to the multiple first user identifiers to obtain the authentication timestamps corresponding to the multiple first user identifiers respectively; the response message also includes the authentication timestamps corresponding to the multiple first user identifiers respectively.

[0054] By introducing the authentication timestamp corresponding to the first user identifier, the data analysis device can select the second user identifier from the multiple first user identifiers based on the authentication timestamp corresponding to the first user identifier when obtaining multiple first user identifiers, thereby narrowing the traceability scope and improving the accuracy of the traceability results.

[0055] It can be understood that the data analysis device described in the third aspect or the fifth aspect provided above is used to execute any of the methods provided in the first aspect, the SDP proxy gateway described in the fourth aspect or the sixth aspect is used to execute any of the methods provided in the second aspect, and the computer storage medium described in the fourth aspect and the computer program product described in the fifth aspect are both used to implement any of the methods provided in the first aspect or any of the methods provided in the second aspect. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] FIG1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

[0057] FIG2 is a flow chart of a threat event tracing method provided in an embodiment of the present application;

[0058] FIG3 is a flow chart of another threat event tracing method provided in an embodiment of the present application;

[0059] FIG3a is a schematic diagram of the structure of a first TCP message;

[0060] FIG4 is a schematic diagram of an interactive process of a threat event tracing method provided in an embodiment of the present application;

[0061] FIG5 is a schematic diagram of an interactive process of another threat event tracing method provided in an embodiment of the present application;

[0062] FIG6 is a schematic diagram of the structure of a data analysis device provided in an embodiment of the present application;

[0063] FIG7 is a schematic diagram of the structure of a network device provided in an embodiment of the present application;

[0064] FIG8 is a schematic structural diagram of another data analysis device provided in an embodiment of the present application;

[0065] FIG9 is a schematic diagram of the structure of another network device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0066] The terms "first", "second", "third" and "fourth" in the specification, claims and drawings of this application are used to distinguish different objects rather than to describe a specific order.

[0067] "Multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating the existence of three relationships. For example, "A and / or B" means: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0068] The embodiments of the present application are described below with reference to the accompanying drawings.

[0069] 1 , which is a schematic diagram of a system architecture provided by an embodiment of the present application, includes an SDP client 101 , an SDP controller 102 , an SDP proxy gateway 103 , a probe device 104 , a data analysis device 105 , and an application server 106 .

[0070] The SDP client 101 is used to implement functions such as access authentication, environment awareness, and data security isolation. The SDP client 101 is a terminal device, such as a desktop computer, laptop, tablet, or smartphone, or a software client installed on the terminal device. During authentication, the SDP client 101 sends an authentication request to the SDP controller 102. The authentication request includes, but is not limited to, the SDP client's device identifier and the SDP client's source IP address.

[0071] The SDP controller 102 is an SDP authentication server that is used to authenticate the SDP client 101, control the access of the SDP client 101, and send trusted asset information to the SDP proxy gateway 103. After the authentication is successful, the SDP controller 102 generates trusted asset information, which includes but is not limited to the source IP address of the SDP client 101, the device identifier of the SDP client 101, and a list of accessible ports.

[0072] The SDP proxy gateway 103 performs network access authentication for devices and proxy access to business applications based on the trusted asset information issued by the SDP controller 102. Optionally, the SDP proxy gateway 103 comprises a switch, router, firewall, or access point (AP) device. Optionally, the SDP proxy gateway 103 can also perform security checks on business messages sent by the SDP client 101. When the SDP proxy gateway 103 determines that a business message presents a security risk, it generates threat log data and sends the threat log data to the data analysis device 105.

[0073] The probe device 104 is a network traffic collection device that collects and processes traffic that needs to be tested for security threats, and sends the processed data to the data analysis device 105 for security testing.

[0074] Data analysis device 105, a security threat analysis and detection platform, performs security checks on data processed by probe device 104. It generates threat events when security risks exist, or generates threat events based on threat log data sent by SDP proxy gateway 103. It also obtains user identifiers from SDP controller 102 to trace the threat events. Data analysis device 105 displays threat events and user identifiers.

[0075] The application server 106 is a device that provides application services. Optionally, the application server 106 is a server, a server cluster, a cloud server, a cloud computing service center, or other forms of devices with computing capabilities.

[0076] SDP client 101 sends an SDP authentication message to SDP controller 102. This message is used to authenticate the identity of SDP client 101. SDP controller 102 authenticates SDP client 101. After successful authentication, SDP controller 102 generates a user information table. The user information table includes a correspondence between the device identifier of SDP client 101 and the user identifier. Here, the user refers to the user who uses SDP client 101 to access the application. SDP client 101 sends a service message to SDP proxy gateway 103. Optionally, the service message is a TCP message or a tunnel message. The service message carries the device identifier of SDP client 101.

[0077] In one example, the SDP proxy gateway 103 can forward the service message to the application server 106 through the routing device. When the service message passes through the routing device, the routing device can mirror the service message to the probe device 104. The probe device 104 analyzes the obtained service message, generates metadata of the service message carrying the device identifier of the SDP client 101, and transmits the metadata of the service message to the data analysis device 105. The metadata of the service message includes but is not limited to the source IP address, destination IP address, source port, destination port, protocol, and device identifier of the SDP client. The data analysis device 105 analyzes the service message metadata according to the first security detection rule to determine whether the service message has a first security risk. If it is determined that there is a security risk, the data analysis device 105 obtains the device identification of the SDP client 101 from the metadata and generates a threat event carrying the device identification of the SDP client 101; the data analysis device 105 obtains the user identification corresponding to the device identification of the SDP client 101 from the user information table of the SDP controller 102 based on the device identification of the SDP client 101, and the user identification is used to indicate the user corresponding to the threat event.

[0078] In another example, after receiving a service message, the network device detects the service message according to a second security detection rule to determine whether the service message presents a second security risk. If the service message presents the second security risk, the network device generates threat log data that carries the device identifier of SDP client 101. The network device sends the threat log data to data analysis device 105. Data analysis device 105 generates a threat event that carries the device identifier of SDP client 101 based on the threat log data. Based on the device identifier of SDP client 101, data analysis device 105 obtains a user identifier corresponding to the device identifier of SDP client 101 from the user information table of SDP controller 102. The user identifier is used to indicate the user corresponding to the threat event.

[0079] Optionally, the network device is an SDP proxy gateway 103 or a probe device 104. It should be understood that the security detection capabilities of the SDP proxy gateway 103 and the probe device 104 are the same, and the operation of detecting the service message according to the second security detection rule is performed by one of the SDP proxy gateway 103 and the probe device 104, and does not need to be performed by both the SDP proxy gateway 103 and the probe device 104.

[0080] In the solution of the embodiment of the present application, the SDP client carries the device identification of the SDP client in the business message sent, so that when the data analysis device determines that there is a security risk in the business message, it can trace the source based on the device identification of the SDP client, thereby tracing the source of the threat event, and tracing the source to the specific user, improving the accuracy of tracing the source, and solving the problem that security risks cannot be traced in the NAT scenario. The solution of the embodiment of the present application is a combination of a zero-trust solution and a data analysis device solution, which can solve customer pain points without increasing customer budget costs, thereby improving the competitiveness of the solution and increasing the stickiness of the solution.

[0081] The implementation process of this application is described in detail below.

[0082] See Figure 2, which is a flow chart of a threat event tracing method provided by an embodiment of the present application. The method is applied to the data analysis device 105 in Figure 1. As shown in Figure 2, the method includes:

[0083] S201. The data analysis device obtains traceability data of a service message. The service message is a message generated when the SDP client accesses the application server. The traceability data of the service message includes a device identifier of the SDP client.

[0084] Optionally, the service message traceability data is service message metadata or threat log data. Service message metadata is generated by a probe device based on the service message. Threat log data is generated by a network device when it determines that a service message presents a security risk. Optionally, the network device is an SDP proxy gateway or a probe device.

[0085] In one example, after a network device receives a service message from an SDP client, the SDP proxy gateway forwards the message to an application server via a routing device. The routing device then mirrors the message to a probe device. The probe device analyzes the message to obtain the SDP client's device identifier, the message's source IP address, destination IP address, source port, destination port, and protocol. Based on the SDP client's device identifier, the message's source IP address, destination IP address, source port, destination port, and protocol, the probe device generates metadata for the message. The metadata includes the SDP client's device identifier, the message's source IP address, destination IP address, source port, destination port, and protocol.

[0086] In one example, after receiving a message sent by an SDP client, the SDP proxy gateway performs a security check on the service message according to the second security check rule. If the service message presents the second security risk, the SDP proxy gateway generates threat log data that carries the device identifier of the SDP client. If the service message does not present the second security risk, the SDP proxy gateway does not generate threat log data.

[0087] Optionally, the second security detection rule is implemented based on an IPS detection algorithm, a DPI detection algorithm, or an anti-virus (AV) detection algorithm. Of course, the second security detection rule can also be implemented by other algorithms, which are not limited here.

[0088] Optionally, the second security risk is a security risk detected by network devices such as firewalls and security gateways through IPS, DPI, file scanning, etc., for example, a service message carries a virus file or other security risk.

[0089] S202: If there is a security risk in the service message, the data analysis device generates a threat event carrying the device identifier of the SDP client.

[0090] Specifically, when the traceability data of a business message is the metadata of the business message, the data analysis device analyzes the metadata of the business message according to the first security detection rule to determine whether the business message has a first security risk. In one example, the data analysis device analyzes the traffic data received by the data analysis device according to the first security detection rule to determine whether the business message has a first security risk. The traffic data received by the data analysis device includes the metadata of the business message. When it is determined that the business message has a first security risk, the data analysis device generates a threat event carrying the device identifier of the SDP client.

[0091] Optionally, the first security risk is a risk identified by the data analysis device based on metadata of business messages, such as a zero-day threat or other security risk. By analyzing metadata from a large number of probes, the data analysis device may be able to discover new risks that cannot be identified by existing rules based on message features.

[0092] When the traceability data of the business message is threat log data, if the data analysis device receives the threat log data, the data analysis device determines that the business message has a security risk, and the data analysis device generates a threat event carrying the device identifier of the SDP client; if no threat day data is received, the data analysis device determines that the business message does not have a security risk.

[0093] S203: The data analysis device obtains a first user identifier corresponding to the device identifier of the SDP client from the user information table of the SDP controller according to the device identifier of the SDP client.

[0094] The first user identifier indicates a user corresponding to the threat event, and the user information table includes a correspondence between the device identifier of the SDP client and the first user identifier.

[0095] In one example, a data analysis device sends a query request to an SDP controller, the query request carrying the device identifier of the SDP client, and the query request is used to instruct the SDP controller to query the user information table to obtain a first user identifier corresponding to the device identifier of the SDP client. The SDP controller queries the user information table based on the device identifier of the SDP client to obtain a first user identifier corresponding to the device identifier of the SDP client, and the first user identifier indicates the user corresponding to the threat event. The SDP controller sends a response message to the data analysis device to respond to the query request, the response message carrying the first user identifier corresponding to the device identifier of the SDP client. The data analysis device displays the first user identifier and the threat event. By displaying the threat event and the first user identifier, the staff can know which user sent the message that poses a security risk, thereby determining the source of the threat event.

[0096] Optionally, the user information table also includes a correspondence between the first user identifier and the authentication timestamp, and the authentication timestamp is the moment when the user indicated by the corresponding first user identifier passes the authentication. When there are multiple first user identifiers carried in the response message, the response message also includes the authentication timestamps corresponding to the multiple first user identifiers. The data analysis device obtains the second user identifier based on the sending period of the business message and the authentication timestamps corresponding to the multiple first user identifiers. The second user identifier is the user identifier whose corresponding authentication timestamp among the multiple first user identifiers belongs to the sending period of the business message. The sending period of the business message is determined by the data analysis device based on the moment when the traceability data of the business message is received. When there are multiple first user identifiers, this method can be used to determine the second user identifier from the multiple first user identifiers, narrowing the traceability range and thereby improving the accuracy of the traceability results.

[0097] It should be understood that after a user passes authentication, they will send service messages through the SDP client. Therefore, the data analysis device uses the moment of user authentication as the moment the SDP client sent the service message. It takes some time for the SDP client to send the service message and for the data analysis device to receive the traceability data for the service message. The data analysis device can calculate the average value of this time by analyzing historical data for this time. The data analysis device then uses this average value and the moment the data analysis device receives the traceability data to determine the service message sending period.

[0098] In another example, a data analysis device sends a query request to an SDP controller. The query request carries the device identifier of the SDP client and the time period for sending a service message. The time period for sending a service message is determined by the data analysis device based on the time of receipt of traceability data for the service message. The query request instructs the SDP controller to query a user information table to obtain a second user identifier corresponding to the device identifier of the SDP client. The user information table includes a correspondence between the device identifier and user identifiers of the SDP client, and a correspondence between user identifiers and authentication timestamps. The SDP controller queries the user information table based on the device identifier of the SDP client to obtain a first user identifier corresponding to the device identifier of the SDP client. The SDP controller selects a second user identifier from the first user identifiers based on the authentication timestamp corresponding to the first user identifier and the time period for sending the service message. The second user identifier is a user identifier whose corresponding authentication timestamp in the first user identifier falls within the time period for sending the service message. The second user identifier indicates the user corresponding to the threat event. The SDP controller sends a response message to the data analysis device in response to the query request, the response message carrying the second user identifier. The data analysis device displays the second user identifier and the threat event.

[0099] By including the service message transmission period and the authentication timestamp corresponding to the user ID, the scope of traceability is narrowed, thereby improving the accuracy of the traceability results. Furthermore, the SDP controller is responsible for obtaining the second user ID from the first user ID based on the authentication timestamp corresponding to the first user ID and the service message transmission period, reducing the workload of the data analysis equipment.

[0100] In the solution of the embodiment of the present application, by carrying the device identification of the SDP client in the business message, the subsequent data analysis device can trace the source based on the device identification of the SDP client after there is a security risk in the business message, thereby tracing the source of the threat event, and tracing the source to a specific user, improving the accuracy of tracing the source, and solving the problem that the security risk cannot be traced in the NAT scenario. When there are multiple users to be traced, the scope of tracing is narrowed by introducing the sending period of the business message and the authentication timestamp corresponding to the user identification, thereby improving the accuracy of the tracing result. The solution of the embodiment of the present application is a combination of the zero-trust solution and the solution of the security big data analysis platform, which can solve the customer pain point problem without increasing the customer's budget cost, so as to enhance the competitiveness of the solution and increase the stickiness of the solution.

[0101] Referring to Figure 3, Figure 3 is a flow chart of a threat event tracing method provided by an embodiment of the present application. The method is applied to network devices.

[0102] Optionally, the network device is the SDP proxy gateway 103 or the probe device 104 in Figure 1. As shown in Figure 3, the method includes:

[0103] S301: A network device receives a service message. The service message is a message generated when an SDP client accesses an application server. The service message carries a device identifier of the SDP client.

[0104] Optionally, the service message is a TCP message or a tunnel message.

[0105] Optionally, the tunnel message is an SRv6 message or a multi-protocol label switching (MPLS) message. SRv6 is a segment routing technology under IPv6.

[0106] In one example, the SDP client establishes a TCP connection with the SDP proxy gateway, and then sends a first TCP message to the SDP proxy gateway, wherein the device identifier of the SDP client is carried in a newly added option field of the first TCP message.

[0107] Figure 3a shows a schematic diagram of the structure of the first TCP message. As shown in Figure 3a, the device identifier of the SDP client is carried in a newly added option field of the first TCP message.

[0108] In another example, the SDP client encapsulates a new header based on the second TCP or User Datagram Protocol (UDP) message, which carries the device identifier of the SDP client. The new header and the second TCP or UDP message form a tunnel message. It should be understood that the second TCP or UDP message does not carry the device identifier of the SDP client. The second TCP or UDP message is used by the SDP client to access the application server.

[0109] Optionally, the SDP client encrypts the device identifier of the SDP client and then carries the encrypted result in a newly added option field of the first TCP message or a new message header of the tunnel message.

[0110] S302. The network device detects the service message according to the second security detection rule; if the service message has a second security risk, the network device generates threat log data carrying the device identifier of the SDP client.

[0111] Specifically, the network device extracts threat signatures from the service message based on the second security detection rule. If a threat signature is extracted, the network device matches the threat signature with a pre-stored threat signature in the second security risk library. If a match is successful, the network device determines that the service message presents the second security risk, and the SDP proxy gateway generates threat log data containing the device identifier of the SDP client. If no threat signature is extracted or the extracted threat signature does not match any of the pre-stored threat signatures in the second security risk library, the service message is determined not to present the second security risk, and the SDP proxy gateway does not generate threat log data.

[0112] Optionally, the second security detection rule is implemented based on an IPS detection algorithm, a DPI detection algorithm, or an AV detection algorithm. Of course, the security detection rule can also be implemented by other algorithms, which are not limited here.

[0113] Optionally, the second security risk is a security risk detected by network devices such as firewalls and security gateways through IPS, DPI, file scanning, etc., for example, a business message carries a virus file or other security risk.

[0114] S303: The network device sends threat log data to the data analysis device.

[0115] In the solution of the embodiment of the present application, by carrying the device identification of the SDP client in the business message, the subsequent data analysis device can trace the source based on the device identification of the SDP client after determining that the business message has a security risk, thereby tracing the source of the threat event, and tracing the source to the specific user, solving the problem that the security risk cannot be traced in the NAT scenario. The network device detects whether the business message has a second security risk, and the data analysis device does not need to detect whether the business message has a second security risk, which reduces the workload of the data analysis device. In addition, the solution of the present application is a combination of the zero-trust solution and the security big data analysis platform solution, which can solve customer pain points without increasing customer budget costs, so as to enhance the competitiveness of the solution and increase the stickiness of the solution.

[0116] See Figure 4, which is a schematic diagram of an interactive process of a threat event tracing method provided by an embodiment of the present application. The method is applied to the system architecture shown in Figure 1. As shown in Figure 4, the method includes:

[0117] S401: The SDP client sends an authentication message to the SDP controller.

[0118] The authentication message carries the device identifier of the SDP client.

[0119] In one example, the authentication message carries trusted asset information, which includes but is not limited to the source IP of the SDP client, the device identifier of the SDP client, and a list of accessible ports.

[0120] In one example, the authentication message is sent via the TCP protocol, and the device identifier of the SDP client is carried in a newly added option field of the TCP SYN message.

[0121] S402: After the authentication is successful, the SDP controller generates a user information table.

[0122] After receiving the authentication message from the SDP controller, the SDP controller performs identity verification on the authentication system according to the device identification of the SDP client; after the identity verification passes, the SDP controller generates a user information table corresponding to the SDP client.

[0123] In one example, the user information table includes the SDP client's device identifier, user identifier, authentication timestamp, pre-NAT IP address, and post-NAT IP address. The user information table can also include other information about the SDP client, which is not limited here. In the user information table, there is a correspondence between the SDP client's device identifier and user identifier, and between the user identifier and authentication timestamp.

[0124] The device identifier of the SDP client is a unique identifier of the SDP client. In one example, the device identifier of the SDP client is generated based on a universally unique identifier (UUID) algorithm. Specifically, the device identifier of the SDP client is generated using the UUID algorithm based on the hardware information of the SDP client. The hardware information includes, but is not limited to, the physical address of the SDP client's network card, the SDP client's hard disk information, CPU information, counter information, etc.

[0125] The user ID refers to the ID of the user who uses the SDP client to perform SDP authentication.

[0126] The authentication timestamp is the time when the SDP client passes the authentication. This timestamp can be used to determine the time when the SDP client authenticates and goes online.

[0127] After authentication is successful, the SDP controller sends trusted asset information to the SDP proxy gateway. This trusted asset information includes, but is not limited to, the SDP client's source IP address, the SDP client's device identifier, and a list of accessible ports. The SDP controller also sends a resource list to the SDP client, which contains information about the resources accessible to the SDP client.

[0128] S403: The SDP client sends a service message to the SDP proxy gateway.

[0129] The application that the SDP client wants to access through the service message is the resource that the SDP client can access.

[0130] Optionally, the service message sent by the SDP client to the SDP proxy gateway is a TCP message or a tunnel message.

[0131] In one example, the SDP client establishes a TCP connection with the SDP proxy gateway, and then sends a first TCP message to the SDP proxy gateway, wherein the device identifier of the SDP client is carried in a newly added option field of the first TCP message.

[0132] In another example, the SDP client encapsulates a new header based on the second TCP or UDP packet. This header carries the SDP client's device identifier. The new header and the second TCP or UDP packet form a tunnel message. It should be understood that the second TCP or UDP packet does not carry the SDP client's device identifier. The second TCP or UDP packet is used by the SDP client to access the application server.

[0133] Optionally, the tunnel message is an SRv6 message or an MPLS message. SRv6 is a segment routing technology under IPv6.

[0134] Optionally, the SDP client first encrypts the device identifier of the SDP client, and then carries the encrypted information in a newly added option field of the first TCP message or in a new message header of the tunnel message.

[0135] S404: The SDP proxy gateway forwards the service message to the application server through the routing device.

[0136] After receiving a service message, the SDP proxy gateway verifies the legitimacy of the SDP client sending the message. If the device identifier and / or source IP address of the SDP client sending the message are trusted assets, the SDP proxy gateway forwards the message to the corresponding application server. The SDP proxy gateway forwards the message to the application server via a port in the accessible port list.

[0137] It should be understood that the SDP proxy gateway transmits the service message to the application server via the router. The SDP proxy gateway transmits the service message to the application server via the router according to a preset routing forwarding policy. Optionally, the preset routing forwarding policy is a shortest path first policy or a shortest delay policy. Of course, the SDP proxy gateway can also forward the service message to the application server using other forwarding policies, which are not limited here.

[0138] S405: The routing device mirrors the traffic to the probe device.

[0139] It's important to note that the traffic here refers to the traffic generated by the SDP proxy gateway forwarding service packets to the application server. As the traffic passes through the routing device, it copies the traffic and then transmits the copy to the probe device, mirroring the traffic to the probe device. It should be understood that when the routing device mirrors the traffic to the probe device, it essentially sends the service packets to the probe device.

[0140] S406: The probe device generates metadata of the service message carrying the device identifier of the SDP client according to the service message.

[0141] In one example, after the probe device obtains the service message, it analyzes the service message to obtain the device identification of the SDP client, the source IP, destination IP, source port, destination port and protocol of the service message; the probe device generates metadata of the service message based on the device identification of the SDP client, the source IP, destination IP, source port, destination port and protocol of the service message. The metadata of the service message includes the device identification of the SDP client, the source IP, destination IP, source port, destination port and protocol of the service message.

[0142] In one example, after a probe device obtains a service message, if the probe device has its security detection function enabled, the probe device extracts threat features from the service message according to the second security detection rule. If a threat feature is extracted, the probe device matches the threat feature with a pre-stored threat feature in a second security risk library. If the match is successful, the probe device determines that the service message presents a second security risk. The probe device generates threat log data containing the device identifier of the SDP client and sends the threat log data to a data analysis device. After receiving the threat log data, the data analysis device generates a threat event including the device identifier of the SDP client. At this point, S406-S408 do not need to be executed, and the data analysis device executes S409 and S410. If no threat feature is extracted or the extracted threat feature does not match any of the pre-stored threat features in the second security risk library, it is determined that the service message does not present a second security risk, and the SDP proxy gateway does not generate threat log data. At this point, it is necessary to further determine whether the service message presents a first security risk, and S407-S410 are executed.

[0143] S407: The probe device sends metadata of the service message to the data analysis device.

[0144] S408: The data analysis device performs security detection on the metadata of the service message.

[0145] Specifically, the data analysis device performs a security check on the metadata of the service message according to the first security detection rule to determine whether the service message presents a first security risk. In one example, the data analysis device analyzes the traffic data received by the data analysis device according to the first security detection rule to determine whether the service message presents a first security risk. The traffic data received by the data analysis device includes the metadata of the service message. If it is determined that the service message presents the first security risk, the data analysis device obtains the device identifier of the SDP client from the metadata of the service message and generates a threat event that carries the device identifier of the SDP controller.

[0146] Optionally, the first security risk is a risk analyzed by the data analysis device based on the metadata of the business message, such as a zero-day threat or other security risk. By analyzing the metadata from a large number of probes, the data analysis device may be able to discover some new risks that cannot be identified by existing rules based on message features. It should be understood that the first security risk is different from the second security risk, and the first security detection rule is different from the second security detection rule.

[0147] S409: The data analysis device sends a query request to the SDP controller.

[0148] S410: The SDP controller sends a response message to the data analysis device.

[0149] It should be noted that the specific implementation process of S409 and S410 refers to the relevant description of S203 and will not be described here. The beneficial effects of the solution of the embodiment shown in Figure 4 refer to the relevant description of S201-S203.

[0150] See Figure 5, which is an interactive flow diagram of another threat event tracing method provided by an embodiment of the present application. The method is applied to the system architecture shown in Figure 1. As shown in Figure 5, the method includes:

[0151] S501: The SDP client sends an authentication message to the SDP controller.

[0152] S502: After the authentication is successful, the SDP controller generates a user information table.

[0153] S503: The SDP client sends a service message to the SDP proxy gateway.

[0154] It should be pointed out here that the specific implementation process of S501-S503 can be found in the relevant description of S401-S403 and will not be described again here.

[0155] S504: The SDP proxy gateway performs a security check on the service message according to the second security check rule.

[0156] In one possible implementation, if the SDP proxy gateway has the security detection function enabled, the SDP proxy gateway extracts threat features from the service message according to the second security detection rule. If a threat feature is extracted, the SDP proxy gateway matches the threat feature with the threat features in the pre-stored second security risk library. If the match is successful, the SDP proxy gateway determines that the service message has a second security risk, and the SDP proxy gateway generates threat log data that carries the device identifier of the SDP client. If no threat feature is extracted or the extracted threat feature does not match any threat feature in the pre-stored second security risk library, it is determined that the service message does not have a second security risk, and the SDP proxy gateway does not generate threat log data. At this point, the service message will be mirrored to the probe device.

[0157] Optionally, the second security detection rule is implemented based on an IPS detection algorithm, a DPI detection algorithm, or an AV detection algorithm. Of course, the second security detection rule can also be implemented by other algorithms, which are not limited here.

[0158] Optionally, the second security risk is a security risk detected by network devices such as firewalls and security gateways through IPS, DPI, file scanning, etc., for example, a service message carries a virus file or other security risk.

[0159] S505: The SDP proxy gateway sends the threat log data to the data analysis device.

[0160] S506: The data analysis device generates a threat event based on the threat log data.

[0161] After receiving the threat log data, the data analysis device determines that the service message has a second security risk, obtains the device identifier of the SDP client from the threat log data, and generates a threat event carrying the device identifier of the SDP client.

[0162] S507: The data analysis device sends a query request to the SDP controller.

[0163] S508. The SDP controller sends a response message to the data analysis device.

[0164] It should be noted that the specific implementation process of S507 and S508 can be found in the relevant description of S203 and will not be described here. The beneficial effects of the solution of the embodiment shown in FIG5 can be found in the relevant description of S201-S203.

[0165] 6 is a schematic diagram of the structure of a data analysis device provided in an embodiment of the present application. The data analysis device is the data analysis device 105 in FIG1 . As shown in FIG6 , the data analysis device 105 includes an acquisition unit 1051 , a generation unit 1052 , and a transceiver unit 1053 .

[0166] The acquisition unit 1051 is used to obtain the traceability data of the service message. The service message is a message generated when the SDP client accesses the application server. The traceability data of the service message includes the device identifier of the SDP client;

[0167] The generating unit 1052 is configured to generate a threat event carrying the device identifier of the SDP client according to the traceability data of the service message when there is a security risk in the service message;

[0168] The transceiver unit 1053 is used to obtain a first user identifier corresponding to the device identifier of the SDP client from the user information table of the SDP controller according to the device identifier of the SDP client, wherein the first user identifier is used to indicate the user corresponding to the threat event, and the user information table includes a correspondence between the device identifier of the SDP client and the first user identifier.

[0169] In one possible implementation, the security risk includes a first security risk, the traceability data of the service message is metadata of the service message, and the metadata of the service message is generated by the probe device based on the service message. The data analysis device 105 further includes:

[0170] The analyzing unit 1054 is configured to analyze metadata of the service message according to the first security detection rule to determine whether the service message has a first security risk.

[0171] In a possible implementation, the security risk includes a second security risk, and the traceability data of the service message is threat log data, which is generated by the network device when determining that the service message has the second security risk.

[0172] In one possible implementation, the transceiver unit 1053 is specifically configured to:

[0173] A query request is sent to the SDP controller, the query request carries the device identifier of the SDP client, and the query request is used by the SDP controller to query the user information table to obtain the first user identifier corresponding to the device identifier of the SDP client; and a response message in response to the query request is received from the SDP controller, the response message carries the first user identifier corresponding to the device identifier of the SDP client.

[0174] In one possible implementation, the user information table further includes a correspondence between the first user identifier and the authentication timestamp. The authentication timestamp is the time when the user indicated by the first user identifier passes the authentication. When the response message includes multiple first user identifiers, the response message also includes the authentication timestamps corresponding to the multiple first user identifiers. The acquiring unit 1051 is further configured to:

[0175] A second user identifier is selected from multiple first user identifiers based on the sending period of the business message and the authentication timestamps corresponding to the multiple first user identifiers; wherein the second user identifier is the first user identifier among the multiple first user identifiers whose authentication timestamp belongs to the sending period; the sending period is determined based on the moment when the data analysis device receives the traceability data of the business message.

[0176] It is worth noting that, for the specific functional implementation of the data analysis device 105, please refer to the description of the above-mentioned threat event tracing method, such as the acquisition unit 1051, the transceiver unit 1053 and the analysis unit 1054 are used to execute the relevant contents of S201 and S203. The various units or modules in the data analysis device 105 can be individually or completely merged into one or several other units or modules to form a composition, or one (or some) of the units or modules can be further divided into multiple functionally smaller units or modules to form a composition, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0177] 7 is a schematic diagram of the structure of a network device provided in an embodiment of the present application. The network device is the SDP proxy gateway 103 or the probe device 104 in FIG1 . As shown in FIG7 , the network device 700 includes a transceiver unit 701 , a detection unit 702 , and a generation unit 703 .

[0178] The transceiver unit 701 is configured to receive a service message, where the service message is a message generated when the SDP client accesses the application server and carries the device identifier of the SDP client;

[0179] A detection unit 702 is configured to perform a security detection on the service message according to the second security detection rule to determine whether the service message has a second security risk;

[0180] The generating unit 703 is configured to generate threat log data carrying the device identifier of the SDP client if it is determined that the service message has a second security risk;

[0181] The transceiver unit 701 is further configured to send threat log data to the data analysis device 105 .

[0182] Optionally, the network device 700 is an SDP proxy gateway 103 or a probe device 104 .

[0183] In a possible implementation, the service message is a TCP message or a tunnel message.

[0184] It is worth noting that, for the specific functional implementation of the network device 700, please refer to the description of the above-mentioned threat event tracing method, for example, the transceiver unit 701 is used to execute the relevant content of S301 and S303, and the detection unit 702 and the generation unit 703 are used to execute the relevant content of S302. The various units or modules in the network device 700 can be individually or completely merged into one or several other units or modules to form a composition, or one (or some) of the units or modules can be further divided into multiple functionally smaller units or modules to form a composition, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0185] Based on the description of the above method embodiments and related device embodiments, please refer to Figure 8 . Another embodiment of the present invention provides a schematic structural diagram of a data analysis device 800. The data analysis device 800 shown in Figure 8 (specifically, a computer device) includes a memory 801, a processor 802, a communication interface 803, and a bus 804. The memory 801, processor 802, and communication interface 803 are interconnected via bus 804.

[0186] Optionally, the memory 801 is a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM).

[0187] The memory 801 can store programs. When the program stored in the memory 801 is executed by the processor 802, the processor 802 and the communication interface 803 are used to execute the various steps of the threat event tracing method of the embodiment shown in Figure 2.

[0188] The processor 802 uses a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a graphics processing unit (GPU) or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the data analysis device 105 of the embodiment of the present application, or to execute the threat event tracing method of the method embodiment of the present application.

[0189] Processor 802 can also be an integrated circuit chip with signal processing capabilities. During implementation, each step of the threat event tracing method of the present application can be completed by hardware integrated logic circuits or software instructions in processor 802. Optionally, processor 802 is a general-purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA), or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. Processor 802 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module is located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other storage media well-known in the art. The storage medium is located in the memory 801, and the processor 802 reads the information in the memory 801 and combines its hardware to complete the functions required to be performed by the units included in the data analysis device 105 of the embodiment of the present application, or executes the threat event tracing method of the embodiment shown in Figure 2.

[0190] The communication interface 803 uses a transceiver, such as but not limited to a transceiver, to enable communication between the data analysis device 800 and other devices (such as the SDP controller 102 and the SDP proxy gateway 103 shown in FIG1 ) or a communication network. For example, the data analysis device 800 can obtain threat log data from the SDP proxy gateway 103 through the communication interface 803.

[0191] The bus 804 may include a path for transmitting information between various components of the data analysis device 800 (eg, the memory 801 , the processor 802 , and the communication interface 803 ).

[0192] Optionally, the data analysis device 800 further includes a display 806 and an input device 805 . The display 806 and the input device 805 are connected to other devices in the data analysis device 800 via a bus 804 .

[0193] The display 806 is a liquid crystal display (LCD), an organic light-emitting diode (OLED) display, or other types of displays. The display 806 displays threat events and user identification.

[0194] The input device 805 is a keyboard, a mouse, a voice acquisition device or a video acquisition device. The staff can control the data analysis device 800 through the input device 805.

[0195] It should be noted that although the data analysis device 800 shown in FIG8 only shows a memory, a processor, and a communication interface, during the specific implementation process, those skilled in the art will understand that the data analysis device 800 also includes other components necessary for normal operation. At the same time, according to specific needs, those skilled in the art will understand that the data analysis device 800 may also include hardware components that implement other additional functions. In addition, those skilled in the art will understand that the data analysis device 800 may also include only the components necessary to implement the embodiments of the present application, and does not necessarily include all the components shown in FIG8.

[0196] Based on the description of the above method embodiments and related device embodiments, please refer to Figure 9 . This embodiment of the present invention further provides a schematic structural diagram of a network device 900. The network device 900 shown in Figure 9 includes a memory 901, a processor 902, a communication interface 903, and a bus 904. The memory 901, processor 902, and communication interface 903 are interconnected via bus 904.

[0197] Optionally, the memory 901 is a ROM, a static storage device, a dynamic storage device or a RAM.

[0198] The memory 901 can store programs. When the program stored in the memory 901 is executed by the processor 902, the processor 902 and the communication interface 903 are used to perform each step of the threat event tracing method of the embodiment shown in Figure 3.

[0199] The processor 902 uses a general-purpose CPU, a microprocessor, an application-specific integrated circuit ASIC, a GPU or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the SDP proxy gateway 103 of the embodiment shown in Figure 1, or to execute the threat event tracing method of the method embodiment of the present application.

[0200] Processor 902 can also be an integrated circuit chip with signal processing capabilities. During implementation, each step of the threat event tracing method of the present application can be completed by hardware integrated logic circuits or software instructions in processor 902. Optionally, processor 902 is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. The processor can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The optional software modules are located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other storage media well-known in the art. The storage medium is located in the memory 901, and the processor 902 reads the information in the memory 901, and combines its hardware to complete the functions required to be performed by the units included in the threat event tracing related equipment of the embodiment of the present application, or executes the threat event tracing method of the method embodiment of the present application.

[0201] Communication interface 903 uses, for example but not limited to, a transceiver or other transceiver-related device to enable communication between network device 900 and other devices (such as SDP client 101 and data analysis device 105 in the embodiment shown in FIG1 ) or a communication network. For example, the network device is SDP proxy gateway 103. SDP proxy gateway 103 can receive service messages sent by SDP client 101 through communication interface 903 and can also send threat log data related to the service messages to data analysis device 105.

[0202] The bus 904 may include a path for transmitting information between various components of the network device 900 (eg, the memory 901 , the processor 902 , and the communication interface 903 ).

[0203] Optionally, the network device 900 further includes a display 906 and an input device 905 . The display 906 and the input device 905 are connected to other devices in the network device 900 via the bus 904 .

[0204] The display 906 is an LCD, an OLED display, or other types of displays.

[0205] The input device 905 is a keyboard, a mouse, a voice acquisition device or a video acquisition device. The staff can control the network device 900 through the input device 905.

[0206] It should be noted that although the network device 900 shown in FIG9 only shows a memory, a processor, and a communication interface, in the specific implementation process, those skilled in the art will understand that the network device 900 also includes other components necessary for normal operation. At the same time, according to specific needs, those skilled in the art will understand that the network device 900 may also include hardware components that implement other additional functions. In addition, those skilled in the art will understand that the network device 900 may also include only the components necessary to implement the embodiments of the present application, and does not necessarily include all the components shown in FIG9.

[0207] An embodiment of the present application further provides a chip, which includes a processor and a data interface. The processor reads instructions stored in a memory through the data interface to implement the threat event tracing method of the embodiment of the present application.

[0208] Optionally, as an implementation method, the chip also includes a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the threat event tracing method.

[0209] An embodiment of the present application also provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is executed on a computer or a processor, the computer or processor executes one or more steps in any of the above methods.

[0210] The present application also provides a computer program product comprising instructions, which, when executed on a computer or processor, causes the computer or processor to execute one or more steps in any of the above methods.

[0211] Those skilled in the art will appreciate that the functions described in conjunction with the various illustrative logic blocks, modules, and algorithm steps disclosed herein can be implemented by hardware, software, firmware, or any combination thereof. If implemented in software, the functions described by the various illustrative logic blocks, modules, and steps may be stored or transmitted as one or more instructions or codes on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to tangible media, such as data storage media, or communication media including any media that facilitates the transfer of computer programs from one place to another (e.g., based on a communication protocol). In this manner, computer-readable media may generally correspond to (1) non-transitory tangible computer-readable storage media, or (2) communication media, such as signals or carrier waves. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in this application. A computer program product may include computer-readable media.

[0212] By way of example, and not limitation, such computer-readable storage media include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Furthermore, any connection is properly referred to as a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of media. However, it should be understood that the computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are actually directed to non-transitory tangible storage media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and Blu-ray disc. Disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also intended to be included within the scope of computer-readable media.

[0213] Instructions may be executed by one or more processors, such as one or more DSPs, general-purpose microprocessors, ASICs, FPGAs, or other equivalent integrated or discrete logic circuits. Thus, the term "processor," as used herein, may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. Additionally, in some aspects, the functionality described by the various illustrative logical blocks, modules, and steps described herein is provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated into a combined codec. Furthermore, the techniques may be fully implemented in one or more circuits or logic elements.

[0214] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the division of the unit is only a logical function division, and there are other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Optionally, the mutual coupling, direct coupling, or communication connection shown or discussed is an indirect coupling or communication connection through some interfaces, devices or units, such as electrical, mechanical or other forms.

[0215] Optionally, the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., located in one place, or distributed across multiple network units. Some or all of the units may be selected based on actual needs to achieve the purpose of the solution of this embodiment.

[0216] In the above embodiments, all or part of the embodiments can be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.

[0217] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A threat event tracing method, characterized in that: Applied to a data analysis device, the method comprises: Acquire the traceability data of the service message, where the service message is a message generated when the software-defined boundary SDP client accesses the application server, and the traceability data of the service message includes the device identifier of the SDP client; When there is a security risk in the service message, generating a threat event carrying the device identification of the SDP client according to the traceability data of the service message; According to the device identifier of the SDP client, a first user identifier corresponding to the device identifier of the SDP client is obtained from the user information table of the SDP controller, wherein the first user identifier is used to indicate a user corresponding to the threat event, and the user information table includes a correspondence between the device identifier of the SDP client and the first user identifier.

2. The method according to claim 1, characterized in that The security risk includes a first security risk, the traceability data of the service message is metadata of the service message, and the metadata of the service message is generated by a probe device based on the service message, and the method further includes: The metadata of the business message is analyzed according to the first security detection rule to determine whether the business message has the first security risk.

3. The method according to claim 1, characterized in that: The security risk includes a second security risk, and the traceability data of the business message is threat log data, which is generated by the network device when it is determined that the business message has the second security risk.

4. The method according to any one of claims 1 to 3, characterized in that: The obtaining, according to the device identifier of the SDP client, from the user information table of the SDP controller a first user identifier corresponding to the device identifier of the SDP client includes: Sending a query request to the SDP controller, the query request carrying the device identifier of the SDP client, the query request being used by the SDP controller to query the user information table to obtain a first user identifier corresponding to the device identifier of the SDP client; A response message fed back by the SDP controller in response to the query request is received, where the response message carries a first user identifier corresponding to the device identifier of the SDP client.

5. The method according to claim 4, characterized in that The user information table further includes a correspondence between the first user identifier and an authentication timestamp, the authentication timestamp being the time when the user indicated by the first user identifier passes the authentication, and when the response message includes multiple first user identifiers, the response message further includes authentication timestamps corresponding to the multiple first user identifiers respectively, and the method further includes: Selecting a second user identifier from the plurality of first user identifiers according to a sending period of the service message and authentication timestamps respectively corresponding to the plurality of first user identifiers; The second user identifier is the first user identifier among the multiple first user identifiers whose authentication timestamp belongs to the sending time period, and the sending time period is determined according to the moment when the data analysis device receives the traceability data.

6. A threat event tracing method, characterized in that: The method is applied to a network device, and the method comprises: Receive a service message, where the service message is a message generated when a software-defined boundary SDP client accesses an application server, and the service message carries a device identifier of the SDP client; Performing a security check on the service message according to the second security check rule to determine whether the service message has a second security risk; if it is determined that the service message has a second security risk, generating threat log data carrying a device identifier of the SDP client; The threat log data is sent to a data analysis device.

7. The method according to claim 6, characterized in that The network device is an SDP proxy gateway or a probe device.

8. A data analysis device, characterized in that: The data analysis device comprises: An acquisition unit, used to acquire traceability data of a service message, wherein the service message is a message generated when a software-defined boundary SDP client accesses an application server, and the traceability data of the service message includes a device identifier of the SDP client; A generating unit, configured to generate a threat event carrying a device identifier of the SDP client according to the traceability data of the service message when there is a security risk in the service message; A transceiver unit is used to obtain a first user identifier corresponding to the device identifier of the SDP client from a user information table of the SDP controller according to the device identifier of the SDP client, wherein the first user identifier is used to indicate a user corresponding to the threat event, and the user information table includes a correspondence between the device identifier of the SDP client and the first user identifier.

9. The data analysis device according to claim 8, characterized in that: The security risk includes a first security risk, the traceability data of the business message is metadata of the business message, the metadata of the business message is generated by a probe device based on the business message, and the data analysis device further includes: An analyzing unit is used to analyze the metadata of the business message according to a first security detection rule to determine whether the business message has the first security risk.

10. The data analysis device according to claim 8, characterized in that: The security risk includes a second security risk, and the traceability data of the business message is threat log data, which is generated by the network device when it is determined that the business message has the second security risk.

11. The data analysis device according to any one of claims 8 to 10, characterized in that: The transceiver unit is specifically used for: Sending a query request to the SDP controller, the query request carrying the device identifier of the SDP client, the query request being used by the SDP controller to query the user information table to obtain a first user identifier corresponding to the device identifier of the SDP client; A response message fed back by the SDP controller in response to the query request is received, where the response message carries a first user identifier corresponding to the device identifier of the SDP client.

12. The data analysis device according to claim 11, characterized in that: The user information table further includes a correspondence between the first user identifier and an authentication timestamp, where the authentication timestamp is the time when the user indicated by the first user identifier passes the authentication. When the response message includes multiple first user identifiers, the response message further includes authentication timestamps corresponding to the multiple first user identifiers respectively. The acquisition unit is specifically used to: Selecting a second user identifier from the plurality of first user identifiers according to a sending period of the service message and authentication timestamps respectively corresponding to the plurality of first user identifiers; The second user identifier is the first user identifier among the multiple first user identifiers whose authentication timestamp belongs to the sending time period, and the sending time period is determined according to the moment when the data analysis device receives the traceability data.

13. A network device, characterized in that: include: A transceiver unit, configured to receive a service message, wherein the service message is a message generated when a software defined boundary SDP client accesses an application server, and the service message carries a device identifier of the SDP client; A detection unit, configured to perform a security detection on the service message according to a second security detection rule to determine whether the service message has a second security risk; a generating unit, configured to generate threat log data carrying a device identifier of the SDP client if it is determined that the service message has the second security risk; The transceiver unit is also used to send the threat log data to the data analysis device.

14. The network device according to claim 13, characterized in that: The network device is an SDP proxy gateway or a probe device.

15. A threat event tracing system, characterized in that: The system includes a data analysis device, a network device, a software defined border SDP client and an SDP controller; The data analysis device is used to perform the method according to any one of claims 1 to 5; The network device is used to perform the method according to claim 6 or 7; The SDP controller is used to receive a query request sent by the data analysis device, where the query request carries a device identifier of the SDP client; Querying a user information table according to the device identifier of the SDP client to obtain a first user identifier corresponding to the device identifier of the SDP client; A response message in response to the query request is sent to the data analysis device, wherein the response message carries a first user identifier corresponding to the device identifier of the SDP client; and the user information table includes a correspondence between the device identifier of the SDP client and the first user identifier.

16. The system according to claim 15, characterized in that The user information table also includes a correspondence between the first user identifier and an authentication timestamp, where the authentication timestamp is the time when the user indicated by the first user identifier passes the authentication; the SDP controller is further used to: When there are multiple first user identifiers, query the user information table according to the multiple first user identifiers to obtain authentication timestamps corresponding to the multiple first user identifiers respectively; The response message also includes authentication timestamps corresponding to the multiple first user identifiers respectively.

17. A data analysis device, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 1 to 5.

18. A network device, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 6 to 7.

19. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Citation Information

Patent Citations

  • Early-warning method based on wireless network invasion and early-warning device based on wireless network invasion

    CN107465702A

  • Wireless network intrusion detection method and device

    CN107484173A

  • Equipment positioning method and device based on wireless network intrusion

    CN107509200A

  • Protection method and device of virtual environment

    CN107566401A

  • Wireless network invasion detection system

    CN107579997A

Cited By

  • Real-time traceability graph compression method and device capable of reserving causal association

    CN119853979A

  • Network defense method and device, equipment, program product and storage medium

    CN120785651A

  • Network security visualization system

    CN121356867A

  • Network security visualization system

    CN121356867B