An information security defense method, device, electronic device, and storage medium

By monitoring the operating environment and processing results of heterogeneous executors, a consistency analysis result is generated, which solves the problem of abnormal executor location deviation in the DHR architecture and achieves higher adjudication accuracy and security.

CN123122984APending Publication Date: 2026-11-17PURPLE MOUNTAIN LAB
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611485954.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-22
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The existing DHR proactive defense architecture cannot accurately locate abnormal executors when the output results of heterogeneous executors differ, resulting in insufficient adjudication compatibility and accuracy, and failing to effectively resist complex network threats.

Method used

By monitoring the operating environment information and processing results within the heterogeneous execution entity resource pool, processing consistency analysis results are generated. Combined with the operating environment information, abnormal execution entity situations are determined, and execution entity safety scheduling strategies are generated.

Benefits of technology

It improves the accuracy of identifying abnormal executors, accurately locates abnormal executors, enhances the compatibility and accuracy of adjudication, and improves the level of information security protection.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123122984A_ABST
    Figure CN123122984A_ABST
Patent Text Reader

Abstract

This invention provides an information security defense method, apparatus, electronic device, and storage medium. The method includes: monitoring the operating environment information of each heterogeneous execution entity within a heterogeneous execution entity resource pool and obtaining the processing results of each heterogeneous execution entity; generating a processing consistency analysis result based on the processing results of each heterogeneous execution entity; determining the abnormal execution entity status within each heterogeneous execution entity based on the operating environment information; and generating an execution entity security scheduling strategy based on the processing consistency analysis result and the abnormal execution entity status. This invention can combine processing results and operating environment information to perform multi-dimensional monitoring of execution entity abnormalities, improving the accuracy of abnormal execution entity identification, accurately locating abnormal execution entities, and addressing the problem of insufficient adjudication compatibility and accuracy caused by abnormal execution entity location deviations, thereby enhancing the level of information security protection.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of information security technology, and in particular to an information security defense method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the rapid iteration and widespread adoption of network information technology, and the deepening of informatization across industries, cybersecurity issues have become increasingly prominent, posing a core bottleneck to the high-quality development of informatization. Currently, mainstream network security protection systems primarily rely on traditional passive defense architectures, employing fixed security policies to protect against network risks. However, as network attack methods continue to evolve towards greater complexity, concealment, and sophistication, various new threats are emerging, thoroughly exposing the inherent limitations of traditional passive defense systems. To address the numerous shortcomings of traditional passive defense, the Dynamic Heterogeneous Redundancy (DHR) proactive defense architecture has been widely researched and applied. The DHR architecture breaks through the limitations of traditional passive boundary protection, relying on three core mechanisms—heterogeneous redundancy execution, consistent adjudication, and dynamic scheduling—to achieve proactive defense, thus compensating for the shortcomings of traditional passive defense in resisting zero-day attacks and unknown internal network threats.

[0003] However, existing DHR proactive defense architectures still have significant technical flaws, hindering further improvements in network security protection. Current DHR architectures often employ a single majority voting logic for consensus decisions. When multiple executors produce different outputs or experience abnormal disturbances, they cannot accurately pinpoint the malfunctioning executor, resulting in insufficient fault tolerance and accuracy in the decision-making process, making them prone to bias. Therefore, how to collect comprehensive information based on multi-dimensional status monitoring data from heterogeneous executors and construct a high-security information security defense system has become an urgent problem to be solved. Summary of the Invention

[0004] This invention provides an information security defense method, device, electronic device, and storage medium to solve the problem that when there are differences in the output results of the executor, it is impossible to accurately locate the abnormal executor, resulting in insufficient adjudication compatibility and accuracy, so as to reduce adjudication bias and improve the degree of security defense.

[0005] According to one aspect of the present invention, an information security defense method is provided, wherein the method includes: Monitor the operating environment information of each heterogeneous execution entity in the heterogeneous execution entity resource pool and obtain the processing results of each heterogeneous execution entity; Based on the processing results of each heterogeneous executor, a processing consistency analysis result is generated, and based on the runtime environment information, the abnormal executor status within each heterogeneous executor is determined; Based on the consistency analysis results and the abnormal execution entity situation, an execution entity safety scheduling strategy is generated.

[0006] According to another aspect of the present invention, an information security defense device is provided, wherein the device comprises: The execution entity monitoring module is used to monitor the operating environment information of each heterogeneous execution entity in the heterogeneous execution entity resource pool and to obtain the processing results of each heterogeneous execution entity. The information analysis module is used to generate a processing consistency analysis result based on the processing results of each heterogeneous execution entity, and to determine the abnormal execution entity situation in each heterogeneous execution entity based on the operating environment information. The security policy determination module is used to generate an execution security scheduling policy based on the processing consistency analysis results and the abnormal execution entity situation.

[0007] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the information security defense method according to any embodiment of the present invention.

[0008] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions, the computer instructions being configured to cause a processor to execute and implement the information security defense method described in any embodiment of the present invention.

[0009] The technical solution of this invention monitors the operating environment information and processing results of each heterogeneous execution entity within a heterogeneous execution entity resource pool. It compares the processing results of each heterogeneous execution entity to obtain a processing consistency analysis result. By analyzing the operating environment information of each heterogeneous execution entity, it identifies abnormal execution entities. Based on the abnormal execution entity situation and the processing consistency analysis result, it generates an execution entity safety scheduling strategy. This invention, by combining processing results and operating environment information to perform multi-dimensional monitoring of execution entity anomalies, can improve the accuracy of abnormal execution entity identification, accurately locate abnormal execution entities, and address the problem of insufficient adjudication compatibility and accuracy caused by abnormal execution entity location deviations, thereby improving the level of information security protection.

[0010] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a flowchart of an information security defense method provided in Embodiment 1 of the present invention; Figure 2 This is a flowchart of another information security defense method provided in Embodiment 2 of the present invention; Figure 3 This is a flowchart of another information security defense method provided in Embodiment 3 of the present invention; Figure 4 This is a schematic diagram of the architecture of an information security defense system provided in Embodiment 4 of the present invention; Figure 5 This is a flowchart illustrating an information security defense method according to Embodiment 4 of the present invention; Figure 6 This is a schematic diagram of the data structure of a sliding window according to Embodiment 4 of the present invention; Figure 7 This is a schematic diagram of the structure of an information security defense device according to Embodiment 5 of the present invention; Figure 8 This is a schematic diagram of the structure of an electronic device that implements the information security defense method of this invention. Detailed Implementation

[0013] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0014] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0015] Example 1 Figure 1 This is a flowchart of an information security defense method according to Embodiment 1 of the present invention. This embodiment is applicable to situations where abnormal execution entities are monitored based on multi-dimensional information. The method can be executed by an information security defense device, which can be implemented in hardware and / or software and can be configured in a server or security control unit. Figure 1 As shown, the method includes: Step 110: Monitor the operating environment information of each heterogeneous execution entity in the heterogeneous execution entity resource pool and obtain the processing results of each heterogeneous execution entity.

[0016] The heterogeneous execution entity resource pool can store multiple functionally equivalent but heterogeneously implemented execution entities. The number of execution entities in the resource pool can be at least two. Heterogeneous execution entities in the resource pool that are online can execute commands sent by the business processing unit. Specifically, the heterogeneous execution entity in this embodiment can be an execution entity in the heterogeneous execution entity resource pool that is online. The runtime environment information can include various state information within the container environment required for each heterogeneous execution entity to run. This runtime environment information may include, but is not limited to, container running status, system resource usage, network behavior, process running characteristics, and container isolation environment parameters, such as CPU utilization, memory utilization, key process status events, key target file change events, network port traffic data, number of user logins, and high-risk behavior data. The processing result can be the task execution result generated by each heterogeneous execution entity in response to the commands sent by the business processing unit.

[0017] In this embodiment of the invention, heterogeneous executors that are online within the heterogeneous executor resource pool can be identified. The environmental operation information of the heterogeneous executors can be monitored from multiple dimensions, such as container running status, system resource usage, network behavior, process running characteristics, and container isolation environment parameters, to comprehensively collect the operating environment information. In addition, the processing results of each heterogeneous executor for the same task can also be monitored.

[0018] In one exemplary implementation, monitoring events can be configured for heterogeneous executors. These monitoring events can be used to collect security event data generated by the heterogeneous executors, thereby obtaining environmental operation information. For example, log records in a specified directory of the virtual file system can be read based on cgroup technology to obtain core resource indicators such as CPU utilization, memory usage, disk read / write speed, and storage space usage, while simultaneously monitoring environmental operation information such as resource overruns, sudden load increases, memory overflows, and I / O blocking.

[0019] Step 120: Generate processing consistency analysis results based on the processing results of each heterogeneous executor, and determine the abnormal executor status within each heterogeneous executor based on the information of each operating environment.

[0020] The consistency analysis results indicate the consistency of different processing outcomes. These results are obtained by comparing the processing results of different heterogeneous executors for the same task. For example, for the processing results of three heterogeneous executors, the consistency analysis results could include: the processing results of the three heterogeneous executors are completely consistent; the processing results of the three heterogeneous executors are mostly consistent; or the processing results of the three heterogeneous executors are completely inconsistent. The abnormal executor situation refers to situations where each heterogeneous executor is disturbed and produces anomalies. The abnormal executor situation can include the abnormal executor, the number of abnormal executors, and the validity of the processing results of the abnormal executors.

[0021] In this embodiment of the invention, the processing results of each heterogeneous executor can be compared to determine whether the processing results of different heterogeneous executors are consistent, and the number of consistent processing results. A processing consistency analysis result can be generated based on the comparison of the above processing results, which can indicate the consistency status of each heterogeneous executor. As for the operating environment information obtained by monitoring different heterogeneous executors, their operating environment information can be analyzed. Through comprehensive analysis and evaluation of environmental operating information from multiple dimensions such as container running status, system resource usage, network behavior, process running characteristics, and container isolation environment parameters, it can be determined whether there are abnormal executors in each heterogeneous executor and the number of abnormal executors. The situation where there are abnormal executors in the above heterogeneous executors can be regarded as an abnormal executor situation.

[0022] For example, in some embodiments, a neural network model can be pre-trained, and the runtime environment information of each heterogeneous executor can be input into the neural network model. The neural network model can then determine whether the heterogeneous executor is an abnormal executor. Alternatively, the runtime environment information of each heterogeneous executor can be judged according to specified rules to determine whether the heterogeneous executor is an abnormal executor.

[0023] Step 130: Generate an execution body safety scheduling strategy based on the processing consistency analysis results and the abnormal execution body situation.

[0024] Among them, the execution entity safety scheduling strategy can be information for scheduling and controlling each heterogeneous execution entity in the heterogeneous execution entity resource pool. The execution entity safety scheduling strategy can be used to schedule and control the processing results and / or heterogeneous execution entities, for example, to truncate the output result of a heterogeneous execution entity or to clean a heterogeneous execution entity.

[0025] In this embodiment of the invention, the state of each heterogeneous execution entity in the heterogeneous execution entity resource pool can be determined according to the processing consistency analysis results and the abnormal execution entity request, and an execution entity security scheduling policy can be generated based on the state of the heterogeneous execution entities. The execution entity security scheduling policy can be obtained by processing the processing consistency analysis results and the abnormal execution entity situation based on specified rules, or the execution entity security scheduling policy corresponding to the processing consistency analysis results and the abnormal execution entity request can be determined based on the configured configuration table or configuration information.

[0026] For example, various configuration information can be pre-configured. This configuration information may include different execution security scheduling strategies corresponding to different processing consistency analysis results and abnormal execution entity situations. For instance, if the processing consistency analysis result is completely consistent and there are no abnormal execution entities, the corresponding execution security scheduling strategy is to directly output the processing result. Alternatively, if the processing consistency analysis result is majority consistent, there is one abnormal execution entity, and the processing result of the abnormal execution entity is in the minority, it can be judged that the disturbance assessment of the abnormal execution entity is valid. In this case, the corresponding execution security scheduling strategy is to output the majority of the processing results and clean up the abnormal execution entity. It is understood that in some other embodiments, if the disturbance assessment is determined to be invalid based on the abnormal execution entity situation, a traditional consistency adjudication strategy can be adopted, that is, the output is truncated and the scheduling strategy corresponding to the traditional consistency adjudication is executed. In this embodiment of the invention, the corresponding execution security scheduling strategy can be queried in the configuration information according to the obtained processing consistency analysis result and abnormal execution entity situation.

[0027] This invention, in its embodiments, monitors the operating environment information and processing results of each heterogeneous execution entity within a heterogeneous execution entity resource pool. It compares the processing results of each heterogeneous execution entity to obtain processing consistency analysis results. By analyzing the operating environment information of each heterogeneous execution entity, it identifies abnormal execution entities. Based on the abnormal execution entity conditions and the processing consistency analysis results, it generates an execution entity safety scheduling strategy. This invention, by combining processing results and operating environment information to perform multi-dimensional monitoring of execution entity anomalies, can improve the accuracy of abnormal execution entity identification, accurately locate abnormal execution entities, and address the problem of insufficient adjudication compatibility and accuracy caused by abnormal execution entity location deviations, thereby enhancing information security protection levels.

[0028] Example 2 Figure 2 This is a flowchart of another information security defense method provided in Embodiment 2 of the present invention. This embodiment of the present invention describes the monitoring process of heterogeneous execution entities. (See also...) Figure 2 The method provided in this embodiment of the invention specifically includes the following steps: Step 210: Collect the processing results of the corresponding identical processing requests from each heterogeneous executor.

[0029] The processing request can be a business processing request received by a heterogeneous executor. Each heterogeneous executor responds to the processing request and obtains the corresponding processing result.

[0030] In this embodiment of the invention, a business request can be obtained and copied into a number of business requests corresponding to each heterogeneous execution entity. Each business request can be transmitted to each heterogeneous execution entity. Each heterogeneous execution entity can receive the business request independently and generate a corresponding processing result based on the business request. The processing results generated by each of the heterogeneous execution entities for the same processing request can be received.

[0031] Step 220: Monitor the resource layer, process layer, file layer, network layer, access layer, and behavior layer of the heterogeneous execution entity to obtain runtime environment information.

[0032] In this embodiment of the invention, runtime environment information can be collected from six dimensions, namely, resource layer, process layer, file layer, network layer, access layer, and behavior layer, for each heterogeneous executor. The runtime environment information of each heterogeneous executor can be obtained through lightweight monitoring components deployed in the resource layer, process layer, file layer, network layer, access layer, and behavior layer of each heterogeneous executor.

[0033] For example, metrics such as CPU utilization, memory utilization, disk utilization, and hardware status can be collected at the resource layer of the heterogeneous executor as runtime environment information; or, metrics such as basic process information, process resources, executable files, and process behavior can be collected at the process layer of the heterogeneous executor as runtime environment information; or, metrics such as a list of key files, file attributes, and file events can be collected at the file layer of the heterogeneous executor as runtime environment information; or, metrics such as network ports, network connections, traffic metrics, and network events can be collected at the network layer of the heterogeneous executor as runtime environment information; or, information such as interface status, access identity, access requests, and link status can be collected at the access layer of the heterogeneous executor as runtime environment information; or, behavioral information such as sensitive file access behavior, privilege escalation behavior, process injection and operation behavior, covert communication, and resource escape behavior at the behavior layer of the heterogeneous executor can be used as runtime environment information.

[0034] Step 230: Generate processing consistency analysis results based on the processing results of each heterogeneous execution entity, and determine the abnormal execution entity status within each heterogeneous execution entity based on the information of each operating environment.

[0035] Step 240: Generate an execution body safety scheduling strategy based on the processing consistency analysis results and the abnormal execution body situation.

[0036] This invention collects the processing results output by each heterogeneous executor in a heterogeneous executor resource pool for the same processing request. Simultaneously, it collects runtime environment information covering the resource layer, process layer, file layer, network layer, access layer, and behavior layer of each heterogeneous executor. By comparing the processing results of each heterogeneous executor, a request processing consistency analysis result is obtained. Based on the multi-dimensional runtime environment information of each heterogeneous executor, anomaly executor judgment is completed. Combining the anomaly executor judgment result with the processing consistency analysis result, a corresponding heterogeneous executor security scheduling strategy is generated. This invention combines business output consistency judgment with executor runtime environment monitoring to conduct multi-dimensional anomaly monitoring of heterogeneous executors, improving the accuracy of anomaly executor identification, achieving precise anomaly executor location, and improving the defects of insufficient adjudication compatibility and inaccurate adjudication results caused by anomaly executor location deviation, thereby enhancing the system's information security protection level.

[0037] Furthermore, based on the above embodiments of the invention, the resource layer, process layer, file layer, network layer, access layer, and behavior layer of the heterogeneous execution entity are monitored to obtain runtime environment information, including: Preset events are triggered periodically for the resource layer, process layer, file layer, network layer, access layer, and behavior layer within the heterogeneous execution body; the information collected from the preset events is extracted as runtime environment information; the preset events include at least one of the following: system resource usage reading event, key process status reading event, key directory file change event, network traffic reading event, login detection event, and system call behavior sequence event.

[0038] Among them, the preset event can be a data acquisition event configured in the resource layer, process layer, file layer, network layer, access layer and behavior layer of the heterogeneous execution entity. The preset event can be triggered in a timed manner. For example, the preset event in the resource layer, process layer, file layer, network layer, access layer and behavior layer of the heterogeneous execution entity can be triggered at regular intervals to obtain runtime environment information.

[0039] In this embodiment of the invention, a system resource usage read event can be configured within the resource layer of the heterogeneous execution entity. This system resource usage read event can read parameters recorded in a specified directory of the virtual file system based on cgroup technology. These parameters may include container utilization and container memory utilization. A key process status read event can be configured within the process layer of the heterogeneous execution entity. This key process status read event can traverse the process directory under the PROC directory based on PROC virtual file system technology to read key parameters recorded therein, such as key process lists, process creation information, process destruction information, and process resource usage. A key directory file change event can be configured within the file layer of the heterogeneous execution entity. This key target file change event can collect file event information of key directories within the container of the heterogeneous execution entity based on the inotify mechanism provided by the Linux kernel. This file event information may include file addition information, file deletion information, or file modification information. The network layer of the execution entity is configured with network traffic read events. These events can read network port traffic data under the network directory based on virtual file system technology. This network port traffic data can include network packet reception statistics from the replication and distribution module and network packet sending statistics from the adjudication module. Login detection events can be configured at the access layer of the heterogeneous execution entity. These events can traverse system session records, match user status, and obtain real-time information on currently active logged-in users and their source IPs. System call behavior sequence events can be configured at the behavior layer of the heterogeneous execution entity. These events can detect unknown vulnerability exploits and complex attack behaviors. The monitoring module integrates eBPF monitoring probes (such as those based on Tracee or Falco) to monitor system calls of the execution entity container in real time. The behaviors monitored by the system call behavior sequence events can include sensitive file access behaviors, privilege escalation behaviors, process injection and manipulation behaviors, covert communication behaviors, and resource escape behaviors.

[0040] Example 3 Figure 3 This is a flowchart of another information security defense method provided in Embodiment 3 of the present invention. This embodiment of the present invention describes the abnormal execution entity situation and the process for determining the consistency analysis results. See [link to documentation]. Figure 3 The method provided in this embodiment of the invention specifically includes the following steps: Step 310: Monitor the operating environment information of each heterogeneous execution entity in the heterogeneous execution entity resource pool and obtain the processing results of each heterogeneous execution entity.

[0041] Step 320: Compare the processing results of each heterogeneous executor to obtain the processing consistency analysis results.

[0042] Step 330: Perform statistical analysis on the information of each operating environment at the individual and group dimensions to determine the abnormal execution status within each heterogeneous execution body.

[0043] Among them, the individual dimension can be a dimension for analyzing the operating environment information of a specific heterogeneous executor, while the group dimension can be a dimension for analyzing the operating environment of all heterogeneous executors as a whole.

[0044] In this embodiment of the invention, the operating environment information of each heterogeneous executor can be obtained, and the operating environment information of each heterogeneous executor can be analyzed independently to obtain individual statistical analysis indicators at the individual level. Group analysis can also be performed on all operating environment information of all heterogeneous executors to obtain group statistical analysis indicators at the group level. The abnormal executor situation in each heterogeneous executor can be determined by the individual statistical analysis indicators of each heterogeneous executor and the group statistical analysis indicators of all heterogeneous executors. For example, if the difference between the individual statistical analysis indicator of a certain heterogeneous executor and the group statistical analysis indicator of all heterogeneous executors is greater than a threshold, then the heterogeneous executor is determined to be an abnormal executor.

[0045] Step 340: Generate an execution body safety scheduling strategy based on the processing consistency analysis results and the abnormal execution body situation.

[0046] This invention monitors the operating environment information and processing results of heterogeneous executors within each heterogeneous executor resource pool, compares the processing results of each heterogeneous executor to generate processing consistency analysis results, and performs statistical analysis on the operating environment information at both the group and individual dimensions to determine abnormal executor situations. This generates processing consistency analysis results and corresponding execution security scheduling strategies for abnormal executors. This invention can combine business output consistency with the execution environment to conduct multi-dimensional anomaly monitoring of heterogeneous executors, achieving accurate identification of abnormal executors, improving the accuracy of abnormal executor location, mitigating insufficient adjudication compatibility caused by abnormal executor location deviations, and addressing inaccurate adjudication results, thereby enhancing information security protection levels.

[0047] Furthermore, based on the above embodiments of the invention, statistical analysis is performed on the information of each operating environment at both the individual and group dimensions to determine the abnormal execution status within each heterogeneous execution body, including: Step 3301: Generate the execution health sequence of the corresponding heterogeneous execution entity based on the running environment information of each heterogeneous execution entity at different times.

[0048] The health sequence of the execution body can be a health sequence generated according to the operating environment information at different times. Each health level in the health sequence can be determined by the operating environment information of the heterogeneous execution body at different times. Each heterogeneous execution body can have its own corresponding execution body health sequence.

[0049] In this embodiment of the invention, runtime environment data at different times can be extracted for each heterogeneous execution entity. Based on the runtime environment information, a health score for the corresponding time can be generated according to a specified health score evaluation rule. The health scores can be arranged in chronological order to form a health sequence for the corresponding heterogeneous execution entity. The specified health score evaluation rule can be a preset rule for quantifying runtime environment information. This rule can include a first rule for statistically analyzing positive indicators within the runtime environment information at each time point, and a second rule for statistically analyzing negative indicators. Specifically, the first rule can be applied to indicators within the runtime environment information such as CPU utilization, memory utilization, and the number of anomalies, where smaller values ​​are better. If the j-th indicator of heterogeneous execution entity i... Its preset health threshold is The danger threshold is The first rule can be expressed as follows: like Then the health of the j-th indicator of heterogeneous execution entity i ; like Then the health of the j-th indicator of heterogeneous execution entity i ; like Then the health of the j-th indicator of heterogeneous execution entity i 0.

[0050] The second rule can be specifically applied to indicators such as system call behavior scores within the runtime environment information, where higher values ​​indicate greater safety. For example, if the j-th indicator of heterogeneous execution entity i... Its preset health threshold is The danger threshold is The second rule can be expressed as follows: like Then the health of the j-th indicator of heterogeneous execution entity i ; like Then the health of the j-th indicator of heterogeneous execution entity i ; like Then the health of the j-th indicator of heterogeneous execution entity i 0.

[0051] Specifically, a weighted calculation can be performed based on the health of each indicator of the heterogeneous executor, and the weighted sum of the health of each indicator can be used as the health of the heterogeneous executor under the environmental operating information at a certain moment.

[0052] Step 3302: For each execution entity's health sequence, determine the first health mean and the first health standard deviation as individual historical longitudinal evolution indicators of the corresponding heterogeneous execution entity according to a preset sliding time window.

[0053] The preset sliding time window can be a sliding window configured based on a preset time length. This preset sliding time window can be used to perform statistical analysis on the health sequence of the execution body.

[0054] In this embodiment of the invention, health scores within a corresponding time range can be extracted from the health score sequence of the execution entity according to a preset sliding time window. A first health score mean and a first health score standard deviation can be generated based on one or more extracted health scores. Then, the preset sliding time window is used again to process the health score sequence of the execution entity. The above process can be repeated to determine all first health score means and first health score standard deviations corresponding to the health score sequence of the execution entity. The determined first health score mean and first health score standard deviation can be used as individual historical longitudinal evolution indicators of heterogeneous execution entities corresponding to the above-mentioned health score sequence of the execution entity.

[0055] Step 3303: For all execution entity health sequences, calculate the mean of the second health and the standard deviation of the second health of all heterogeneous execution entities at the same time as a group-wide horizontal comparison index for all heterogeneous execution entities.

[0056] In this embodiment of the invention, the health status sequences of all heterogeneous executors can be aligned according to time granularity. The corresponding health status of each heterogeneous executor can be extracted for each same moment, and the mean and standard deviation of the health status of all heterogeneous executors at the same moment can be determined as the mean and standard deviation of health status. The mean and standard deviation of health status at each moment can be determined repeatedly for the above process. The mean and standard deviation of health status at all moments can be used as a group-wide horizontal comparison index of all heterogeneous executors.

[0057] Step 3304: Determine the abnormal execution entities within each heterogeneous execution entity based on the historical longitudinal evolution indicators of each individual and the horizontal comparison indicators of the group.

[0058] In this embodiment of the invention, the health status sequence of each heterogeneous executor can be matched with its corresponding individual historical longitudinal evolution index to determine whether each health status within the executor health status sequence matches each individual historical longitudinal evolution index, and whether each health status within the executor health status sequence matches a group horizontal comparison index. If both of these indicators match, the heterogeneous executor is determined to be a normal executor; otherwise, it is determined to be an abnormal executor. Further, the method for determining whether each health status within the executor health status sequence matches the individual historical longitudinal evolution index and the group horizontal comparison index can include extracting the first health status mean and the first health status standard deviation from the individual historical longitudinal evolution index, and determining whether each health status is less than the first health status mean minus k times the first health status standard deviation. If so, the heterogeneous executor is determined to be an abnormal executor; otherwise, it is determined to be a normal executor. Similarly, the mean and standard deviation of the second health score can be extracted from the cross-sectional comparison indicators of the group. It can be determined whether each health score is less than the mean of the second health score minus m times the standard deviation of the second health score. If so, the heterogeneous executor is determined to be an abnormal executor. If not, the heterogeneous executor is determined to be a normal executor. It can be understood that the values ​​of m and k can be preset as coefficients.

[0059] Furthermore, the health scores of each heterogeneous executor within the health score sequence can be directly verified. If the health score within the health score sequence is less than the preset health score, the corresponding heterogeneous executor is determined to be an abnormal executor.

[0060] Step 3305: Determine the number of abnormal execution bodies and the validity judgment results of the processing results of the abnormal execution bodies, and use the number and validity judgment results as the status of abnormal execution bodies.

[0061] In this embodiment of the invention, the number of heterogeneous execution bodies identified as abnormal execution bodies can be counted, and it can be determined whether the processing result of each abnormal execution body is the same as the processing result of other heterogeneous execution bodies. If so, the validity determination result of the abnormal execution body is determined to be yes; otherwise, the validity determination result of the abnormal execution body is determined to be no. The number of each abnormal execution body and the validity determination result of each abnormal execution body can be used as the abnormal execution body status.

[0062] Based on the above embodiments of the invention, an execution safety scheduling strategy is generated according to the processing consistency analysis results and the abnormal execution entity situation, including: Obtain the pre-configured disturbance mode discrimination table; query the risk disturbance mode, result output method, and execution body scheduling action that match the disturbance mode discrimination table according to the processing consistency analysis results and the abnormal execution body situation as the execution body safety scheduling strategy.

[0063] Among them, the risk disturbance mode can be a disturbance mode that causes abnormal output of heterogeneous executors. The risk disturbance mode can include differential mode disturbance, common mode disturbance, N-1 mode disturbance, etc. Differential mode disturbance can be that a few executors are abnormal but the processing result is correct by chance; common mode disturbance can be that all executors are subjected to the same external interference, and the output of each executor simultaneously shows N identical abnormal results, and the system is directly destroyed; N-1 mode disturbance can refer to N-1 executors being abnormal but the output is correct by chance, where N is the number of online heterogeneous executors.

[0064] In this embodiment of the invention, a pre-configured disturbance mode discrimination table can be obtained. The disturbance mode discrimination table includes at least one risk disturbance mode, result output method, and execution body scheduling action corresponding to a combination of information on the processing consistency analysis results and abnormal execution body conditions. After obtaining the processing consistency analysis results and abnormal execution body conditions of each heterogeneous execution body, the corresponding risk disturbance mode, result output method, and execution body scheduling action can be queried in the disturbance mode discrimination table. The above-mentioned risk disturbance mode, result output method, and execution body scheduling action can be used as the execution body safety scheduling strategy.

[0065] Based on the above embodiments of the invention, the disturbance mode discrimination table is pre-generated based on the number of heterogeneous executors in the heterogeneous executor resource pool and the fault scenario type. The disturbance mode discrimination table includes at least the following fields: processing consistency analysis result field, abnormal executor status field, disturbance effective assessment field, risk disturbance mode field, result output method field, and executor scheduling action field.

[0066] Specifically, information such as the consistency analysis results of different abnormal executors under different fault scenario types, abnormal executor status, disturbance effectiveness, risk disturbance mode, result output method, and executor scheduling action can be determined in advance based on the number of heterogeneous executors in the heterogeneous executor resource pool and the fault scenario type. The above information can be associated and saved to the corresponding fields of the disturbance mode discrimination table to generate the disturbance mode discrimination table.

[0067] For example, consider a perturbation mode discrimination table with 3 heterogeneous executors: Table 1 Disturbance Mode Discrimination Table Example 4 Figure 4 This is a schematic diagram of the architecture of an information security defense system according to Embodiment 4 of the present invention. See also... Figure 4 The system provided in this embodiment of the invention can adopt a container microservice architecture, specifically including functional modules such as replication and distribution, heterogeneous execution resource pool, monitoring module, full-dimensional information adjudication and scheduling reconstruction; (1) Replication and distribution: responsible for receiving external requests and replicating and distributing them. An online execution entity.

[0068] (2) Heterogeneous Execution Entity Resource Pool: Stores There are functionally equivalent but heterogeneously implemented execution entities, among which ( Each online executor acts as a business processing unit to process externally received commands and sends the results to the adjudication module.

[0069] (3) Monitoring module: Real-time monitoring of the multi-dimensional status information of the execution environment of each online executor, including basic environmental indicators such as resource usage, process status, abnormal login, network packet sending, addition, deletion and modification of important directories, as well as deep security events such as sensitive system call behavior, and periodically feeding back the above multi-dimensional status information to the adjudicator.

[0070] (4) Full-dimensional information adjudication: The execution body environment health score calculation standard is set, and the health sequence of each online execution body is statistically analyzed to realize the individual-group dual disturbance assessment based on the sliding window. Finally, the "execution body output result" and "execution body environment disturbance assessment result" are fused to make a decision, realize full-dimensional information adjudication, and realize the direct judgment of differential mode, N-1 mode and common mode disturbance.

[0071] (5) Scheduling Restructuring: Based on the full-dimensional information adjudication results, it is responsible for the dynamic scheduling and life cycle management of the execution entity.

[0072] Based on the above embodiments of the invention, the monitoring module can collect multi-dimensional status information of the execution container environment of the online executor. It can collect six types of security events, including five types of basic environment monitoring events and one type of deep security event. The information that can be collected for each type of event is as follows: (1) Execution container resource usage event: used to collect system resource usage information of the execution container, including but not limited to resource indicators such as CPU usage rate and memory usage rate.

[0073] (2) Critical process status events within the execution container: used to collect the running status information of critical processes within the execution container, including but not limited to whether the critical process is running, and the process creation or destruction status.

[0074] (3) File change events in critical directories within the execution container: used to collect file change information in critical directories within the execution container, including but not limited to file addition, file deletion, and file modification.

[0075] (4) Network traffic events within the execution container: used to collect network traffic information of the execution container, including but not limited to network packet reception statistics between the execution and the replication and distribution module, and network packet sending statistics between the execution and the adjudication module.

[0076] (5) Login detection event: used to collect login status information of the execution container, including but not limited to the number of logged-in users, login user information and source IP.

[0077] (6) System call behavior sequence events within the execution container: This is used to collect system call behavior sequence information within the execution container to detect unknown vulnerability exploits and complex attack behaviors. The high-risk behavior patterns monitored include, but are not limited to, sensitive file access, privilege escalation, process injection and manipulation, covert communication, and resource escape.

[0078] The six types of monitoring events mentioned above cover six dimensions of the execution container's operation: resource layer, process layer, file layer, network layer, access layer, and behavior layer, forming a multi-layered monitoring system from the basic environment to deep behavior. It should be noted that each type of monitoring event includes one or more specific monitoring metrics: for example, resource events include two metrics: CPU utilization and memory utilization; system call behavior events include five behavior patterns: sensitive file access, privilege escalation, process injection, covert communication, and resource escape. The first five basic events are used to detect explicit changes in the execution container's state (such as resource exhaustion, file tampering, and abnormal login), while the sixth type, system call behavior sequence events, is used to detect covert attack behaviors such as exploitation of unknown vulnerabilities. Through the comprehensive collection of these six types of monitoring events, the monitoring module can provide the adjudication module with comprehensive, multi-dimensional, and real-time execution container environment status data, laying a data foundation for subsequent health scoring and disturbance assessment.

[0079] It should be noted that the types and number of the above monitoring indicators can be expanded or reduced according to actual security needs, and this invention is not limited thereto.

[0080] Specifically, the data acquisition process for multi-dimensional status information by the monitoring module may include the following: (1) Step 1: Initialize the monitoring agent and register the collection callback functions for various events; (2) Step 2: Start the timed data collection task. The default collection period is 5 seconds. (3) Step 3: Read data sources such as / proc file system, cgroup interface, inotify events, and system call behavior; (4) Step 4: Preprocess the collected raw data, including data cleaning, format standardization, and outlier filtering; (5) Step 5: Encapsulate the preprocessed monitoring data (including resource indicators, process status, file events, network traffic, login information and system call behavior sequence) into a unified reporting format and send it to the adjudication module via Socket communication.

[0081] The all-dimensional information adjudication module provided in this embodiment of the invention can realize all-dimensional information adjudication. Its input sources can include the processing results of online executors for the same request, as well as multi-dimensional status information transmitted by the monitoring module. It can calculate the comprehensive health score of each executor based on monitoring data, and then perform a dual perturbation assessment through a sliding window, comparing the individual's historical longitudinal evolution with the peer group's horizontal comparison. Finally, it performs dual-channel cross-validation on the consistency analysis between the perturbation assessment results and the executor's output results, directly determining differential mode, N-1 mode, or common mode perturbation according to the rules in Table 1, and deciding on command output and scheduling actions. The adjudication process of the all-dimensional information adjudication module can be as follows: Figure 5 As shown: 1. Initiate the adjudication process: Receive the processing result from the online executor; 2. Comparison of parallel processing results and assessment of environmental disturbances: Branch A (Result Consistency Comparison): Collect the output results of each executor, compare them, and form a result set. R ; Branch B (Environmental Disturbance Assessment): Obtain multi-dimensional state information reported by the monitoring module; construct an execution entity environmental monitoring data matrix based on the multi-dimensional state information, where each state vector in the execution entity environmental monitoring data matrix corresponds to an execution entity; calculate the environmental monitoring data matrix for each execution entity. i Comprehensive monitoring score And based on the overall health score Generate disturbance assessment results.

[0082] 3. Full-Dimensional Decision: Input Result Set R Cross-validate with the disturbance assessment results, perform full-dimensional adjudication, directly determine the disturbance type (differential mode / N-1 mode / common mode), and send the abnormal execution information to the scheduling module for cleaning.

[0083] In the above embodiments of the invention, the execution body i Comprehensive monitoring score The calculation process may include the following steps: Step 1: Construct the original data vector Suppose the system currently has There are 1 online execution entity. The monitoring module collects six types of monitoring events, and each type of event contains one or more specific monitoring indicators. Let the total number of all specific monitoring indicators be... (For example, resource usage events include two metrics: CPU and memory; system call behavior events include five behavior patterns.) The specific value depends on the actual number of indicators configured, and For the first... individual execution entities The reported monitoring event data constitutes a raw data vector. ,in Representing the The first executor The raw values ​​of each monitoring metric. Monitoring metrics include, but are not limited to, CPU utilization, memory utilization, critical file changes, process status, abnormal logins, network traffic, and system call behavior scores; each metric may correspond to a single-dimensional or multi-dimensional value.

[0084] (2) Step 2: Indicator normalization and score calculation To address the issue of differing dimensions among the indicators, and to calculate a single health score for each indicator, for the [missing information]... Each monitoring indicator has a pre-set health threshold. (Upper limit of normal value) and danger threshold (Lower limit of severe outliers). For the first The first executor Each indicator has a single health score. Calculated according to the following rules: (2.1) Rule 1 (positive indicators, such as CPU utilization, memory utilization, number of exceptions, etc., the smaller the value, the better): like ,but ; like ,but ; like ,but 0.

[0085] (2.2) Rule 2 (negative indicators, such as system call behavior scores; the higher the value, the safer the system): like ,but ; like ,but ; like ,but 0.

[0086] (3) Step 3: Calculate the overall health score of the executive body Based on the importance of each indicator in the safety assessment, each indicator... Assign weights ,satisfy Then the first Overall health score of the individual entity The calculation formula is: Overall health score: in, The range of values ​​is , The closer the value is to 1, the healthier the operating environment of the executor, and the lower the possibility of being attacked or experiencing anomalies; The closer the value is to 0, the more likely the executor has deviated significantly from its healthy state and has been attacked or has suffered a serious malfunction.

[0087] In the above embodiments, the all-dimensional information adjudication module maintains a fixed-length sliding window to store the historical comprehensive health scores H of all online executors within the most recent L adjudication cycles. Through the sliding window, a dual perturbation assessment is performed, combining the longitudinal evolution of individual (within the executor's) history with the horizontal comparison of peer groups (between executors), jointly identifying differential mode, N-1 mode, and common mode perturbations. Specifically, based on the comprehensive health score... The process of generating disturbance assessment results may include the following steps: Step 1: Construct a sliding window for health rating The length of the sliding window is (default ), storing data from the current moment Back to Health rating of all executors at any given time The value. The window slides forward with each new adjudication cycle, discarding the oldest data and adding the latest data. For each executor... ( ), defining its historical health score sequence as ,like Figure 6 As shown.

[0088] (2) Step 2: Individual-Group Dual Perturbation Assessment Mechanism Dimension 1: Vertical Evolution of Individual History For each executor Utilizing historical data within its sliding window Calculate the average of their historical health scores. and standard deviation : Historical average health score: Historical health score standard deviation: Dimension 2: Horizontal comparison among peer groups Calculate the current time ,all Mean of health score of online executives and standard deviation : Group mean: Group standard deviation: (3) Step 3: Perform volume disturbance determination The adjudication module applies to each executor. The following three criteria are used. If any one of these criteria is met, the executor is marked as a "disturbing executor": Historical Sudden Landfall Determination: or When this condition is met, it indicates that the executor... Their health score was significantly lower than their historical normal level. Among them, This is a configurable historical deviation coefficient; the default value is [value missing]. The range of values ​​is To avoid special circumstances This prevents the historical sudden drop detection from ever being triggered, thus increasing the relative drop threshold. ,default value The range of values ​​is This means that the current health score is considered abnormal only if it has dropped by at least 20% from the historical average. Lateral outlier detection: or When this condition is met, it indicates that the executor... The current health score deviates significantly from the average level of all other agents. The configurable lateral outlier coefficient has a default value of [value missing]. The range of values ​​is To avoid special circumstances This prevents the lateral outlier detection from ever being triggered, thus increasing the relative descent threshold. ,default value The range of values ​​is This means that the current health score is considered abnormal only if it has dropped by at least 20% compared to the group average. Determination of an absolutely low health score: When the condition is met, it indicates that the executor... They are already in a severely unhealthy state. Among them, This is the preset absolute lower limit threshold for health score; the default value is [value missing]. The range of values ​​is .

[0089] In one exemplary implementation, the input result set R Cross-validation with the disturbance assessment results can be determined as follows: Assuming there are currently m online executors (m=3), the adjudication module accurately determines the disturbance type according to the rules shown in Table 1 based on the number of "abnormal executors" marked in step 3. Abnormal executors are those identified by the sliding window-based disturbance assessment mechanism. If the disturbance assessment mechanism fails, a single-mode executor result consistency adjudication strategy is adopted.

[0090] Based on the content of Table 1 above, the disturbance mode determination strategy is to cross-validate the "consistency analysis of execution entity processing results" and the "individual-group dual disturbance assessment". Only when the two determination results match (i.e. the disturbance assessment mechanism is effective) can the system directly determine the specific disturbance mode and the processing result of the trusted execution entity can be output to the downstream processing unit. When the two do not match, the system determines that the disturbance assessment mechanism is invalid and adopts a conservative strategy: cut off the output, fall back to the traditional single-mode output consistency decision, and only use the decision information for internal scheduling decisions.

[0091] In summary, this invention establishes a comprehensive information adjudication mechanism combining "individual-group dual perturbation assessment" and "execution entity result consistency analysis." On one hand, the invention introduces a sliding window-based dual perturbation assessment mechanism into the adjudication module. This mechanism tracks the changing trend of each execution entity's health status over time through longitudinal historical evolution assessment, while simultaneously comparing the relative health status differences among execution entities through horizontal comparison assessment within the same generation of the group, thus comprehensively perceiving environmental anomalies of the execution entities. On the other hand, this invention performs dual-channel cross-validation between the execution entity processing result consistency analysis and the aforementioned dual perturbation assessment results, directly and effectively determining the specific adjudication conclusion. Through the fusion mechanism of "dual assessment + dual-channel verification," this invention achieves accurate and real-time discrimination of differential-mode perturbations, N-1-mode perturbations, and common-mode perturbations, significantly improving adjudication credibility and system security.

[0092] Furthermore, the above scheduling actions can be implemented as shown in Table 2 below: Table 2 Scheduling Policy Mapping Table In summary, the core of the method provided by this invention lies in "dual evaluation + dual-channel verification": First, based on the multi-dimensional state information of the execution entity environment reported by the monitoring module, a sliding window dual perturbation evaluation mechanism combining the longitudinal evolution of individual history and the horizontal comparison of the same generation group is used to achieve a comprehensive perception of the execution entity's environmental state; second, by cross-validating the output consistency analysis and perturbation evaluation results, accurate and real-time discrimination of differential mode perturbation, N-1 mode perturbation, and common mode perturbation is achieved. This invention achieves significant progress in the following aspects: In terms of decision-making, it upgrades from single output comparison to full-dimensional information fusion, greatly improving decision accuracy; in terms of business continuity, it can retain most correct outputs in differential mode scenarios and adopt the correct outputs of a few healthy execution entities in N-1 mode scenarios, avoiding the problem of traditional solutions "cutting off" all commands; in terms of engineering implementation, it adopts a containerized microservice architecture, reducing the execution entity startup time from minutes to seconds, and significantly reducing resource consumption. This invention provides a feasible solution for the engineering application of mimicry defense technology, possessing significant theoretical value and broad application prospects.

[0093] Example 5 Figure 7 This is a schematic diagram of the structure of an information security defense device according to Embodiment 5 of the present invention. Figure 7 As shown, the device includes: The execution entity monitoring module 410 is used to monitor the operating environment information of each heterogeneous execution entity in the heterogeneous execution entity resource pool and to obtain the processing results of each heterogeneous execution entity.

[0094] The information analysis module 420 is used to generate a processing consistency analysis result based on the processing results of each heterogeneous execution entity, and to determine the abnormal execution entity status of each heterogeneous execution entity based on the operating environment information.

[0095] The security policy determination module 430 is used to generate an execution body security scheduling policy based on the processing consistency analysis results and the abnormal execution body situation.

[0096] In this embodiment of the invention, an execution entity monitoring module monitors the operating environment information and processing results of each heterogeneous execution entity within a heterogeneous execution entity resource pool. An information analysis module compares the processing results of each heterogeneous execution entity to obtain processing consistency analysis results. By analyzing the operating environment information of each heterogeneous execution entity, abnormal execution entity situations are identified. A security policy determination module generates an execution entity security scheduling policy based on the abnormal execution entity situations and the processing consistency analysis results. This embodiment of the invention, by combining processing results and operating environment information for multi-dimensional monitoring of execution entity anomalies, can improve the accuracy of abnormal execution entity identification, accurately locate abnormal execution entities, and address the problem of insufficient adjudication compatibility and accuracy caused by abnormal execution entity location deviations, thereby improving the level of information security protection.

[0097] In some embodiments of the invention, the execution monitoring module 410 includes: The processing result unit is used to collect the processing results of the corresponding processing requests of each of the heterogeneous executors.

[0098] The data monitoring unit is used to monitor the resource layer, process layer, file layer, network layer, access layer and behavior layer of the heterogeneous executor to obtain the runtime environment information.

[0099] Based on the above embodiments of the invention, the data monitoring unit monitors the resource layer, process layer, file layer, network layer, access layer, and behavior layer of the heterogeneous execution entity to obtain the runtime environment information, including: periodically triggering preset events of the resource layer, process layer, file layer, network layer, access layer, and behavior layer within the heterogeneous execution entity; extracting the information collected by the preset events as the runtime environment information; wherein, the preset events include at least one of the following: system resource occupancy reading event, key process status reading event, key directory file change event, network traffic reading event, login detection event, and system call behavior sequence event.

[0100] In some embodiments of the invention, the information analysis module 420 includes: The result comparison unit is used to compare the processing results of each heterogeneous executor to obtain the processing consistency analysis result.

[0101] An anomaly detection unit is used to perform statistical analysis on the runtime environment information at the individual and group dimensions to determine the anomaly status of each heterogeneous execution body.

[0102] Based on the above embodiments of the invention, the anomaly detection unit is specifically used to: generate an execution health sequence corresponding to the heterogeneous execution entity based on the operating environment information of each heterogeneous execution entity at different times; For each of the execution entity health sequences, the first health mean and the first health standard deviation are determined according to a preset sliding time window as individual historical longitudinal evolution indicators for the corresponding heterogeneous execution entity; For all the aforementioned execution entity health sequences, the mean of the second health and the standard deviation of the second health of all heterogeneous execution entities at the same time are statistically analyzed as a group-wide comparative indicator for all heterogeneous execution entities. The abnormal execution entities within each heterogeneous execution entity are determined based on the longitudinal evolution indicators of each individual and the horizontal comparison indicators of the group; The number of abnormal executors and the validity determination result of the processing result of the abnormal executors are determined, and the number and the validity determination result are used as the status of the abnormal executors.

[0103] In some embodiments of the invention, the security policy determination module 430 is specifically used to: obtain a pre-configured disturbance mode discrimination table; and query the risk disturbance mode, result output method, and execution body scheduling action matched in the disturbance mode discrimination table according to the processing consistency analysis results and the abnormal execution body situation as the execution body security scheduling strategy.

[0104] Based on the above embodiments of the invention, the disturbance mode discrimination table is pre-generated based on the number of heterogeneous executions in the heterogeneous execution resource pool and the fault scenario type. The disturbance mode discrimination table includes at least the following fields: processing consistency analysis result field, abnormal execution status field, disturbance effective assessment field, risk disturbance mode field, result output method field, and execution scheduling action field.

[0105] The information security defense device provided in the embodiments of the present invention can execute the information security defense method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0106] Example 6 Figure 8 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0107] like Figure 8 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0108] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0109] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as information security defense methods.

[0110] In some embodiments, the information security defense method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the information security defense method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the information security defense method by any other suitable means (e.g., by means of firmware).

[0111] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0112] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0113] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0114] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0115] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0116] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0117] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0118] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. An information security defense method, characterized in that, The method includes: Monitor the operating environment information of each heterogeneous execution entity in the heterogeneous execution entity resource pool and obtain the processing results of each heterogeneous execution entity; Based on the processing results of each heterogeneous executor, a processing consistency analysis result is generated, and based on the runtime environment information, the abnormal executor status within each heterogeneous executor is determined; Based on the consistency analysis results and the abnormal execution entity situation, an execution entity safety scheduling strategy is generated.

2. The method according to claim 1, characterized in that, The monitoring of the operating environment information of each heterogeneous execution entity within the heterogeneous execution entity resource pool and the acquisition of the processing results of each heterogeneous execution entity include: Collect the processing results of the corresponding identical processing requests from each of the heterogeneous executors; The resource layer, process layer, file layer, network layer, access layer, and behavior layer of the heterogeneous executable are monitored to obtain the runtime environment information.

3. The method according to claim 2, characterized in that, The monitoring of the resource layer, process layer, file layer, network layer, access layer, and behavior layer of the heterogeneous execution entity to obtain the runtime environment information includes: Preset events in the resource layer, process layer, file layer, network layer, access layer, and behavior layer of the heterogeneous execution body are triggered periodically; Extract the information collected from the preset events as the operating environment information; The preset events include at least one of the following: system resource usage reading event, key process status reading event, key directory file change event, network traffic reading event, login detection event, and system call behavior sequence event.

4. The method according to claim 1, characterized in that, The step of generating a processing consistency analysis result based on the processing results of each heterogeneous execution entity, and determining the abnormal execution entity status within each heterogeneous execution entity based on the runtime environment information, includes: By comparing the processing results of each heterogeneous executor, the processing consistency analysis results are obtained. Statistical analysis is performed on the runtime environment information of each instance at both the individual and group levels to determine the abnormal execution status within each heterogeneous execution instance.

5. The method according to claim 4, characterized in that, The statistical analysis of the runtime environment information at both the individual and group dimensions to determine the abnormal execution status within each heterogeneous execution body includes: Generate an execution health sequence corresponding to each heterogeneous execution entity based on the operating environment information of each heterogeneous execution entity at different times; For each of the execution entity health sequences, the first health mean and the first health standard deviation are determined according to a preset sliding time window as individual historical longitudinal evolution indicators for the corresponding heterogeneous execution entity; For all the aforementioned execution entity health sequences, the mean of the second health and the standard deviation of the second health of all heterogeneous execution entities at the same time are statistically analyzed as a group-wide comparative indicator for all heterogeneous execution entities. The abnormal execution entities within each heterogeneous execution entity are determined based on the longitudinal evolution indicators of each individual and the horizontal comparison indicators of the group; The number of abnormal executors and the validity determination result of the processing result of the abnormal executors are determined, and the number and the validity determination result are used as the status of the abnormal executors.

6. The method according to claim 1, characterized in that, The step of generating an execution body safety scheduling strategy based on the processing consistency analysis results and the abnormal execution body situation includes: Obtain the pre-configured disturbance mode discrimination table; Based on the consistency analysis results and the abnormal executor status, query the risk disturbance mode, result output method, and executor scheduling action matched in the disturbance mode discrimination table as the executor safety scheduling strategy.

7. The method according to claim 6, characterized in that, The disturbance mode discrimination table is pre-generated based on the number of heterogeneous executors in the heterogeneous executor resource pool and the fault scenario type. The disturbance mode discrimination table includes at least the following fields: processing consistency analysis result field, abnormal executor status field, disturbance effective assessment field, risk disturbance mode field, result output method field, and executor scheduling action field.

8. An information security defense device, characterized in that, The device includes: The execution entity monitoring module is used to monitor the operating environment information of each heterogeneous execution entity in the heterogeneous execution entity resource pool and to obtain the processing results of each heterogeneous execution entity. The information analysis module is used to generate a processing consistency analysis result based on the processing results of each heterogeneous execution entity, and to determine the abnormal execution entity situation in each heterogeneous execution entity based on the operating environment information. The security policy determination module is used to generate an execution security scheduling policy based on the processing consistency analysis results and the abnormal execution entity situation.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform an information security defense method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are used to cause a processor to execute an information security defense method according to any one of claims 1-7.