DATA INTEGRITY PROTECTION METHOD AND DEVICE
FIG9 shows a flow diagram of verifying an integrity protection summary according to an embodiment  FIG10 shows a schematic diagram of a data integrity protection device according to an embodiment 
In another embodiment, the central node may also be used for determining whether the data in the industrial control system changes or not by verifying the second integrity protection summary of the industrial control system. As shown in FIG9, step S901, the central node extracts data features and identity features including data to be protected in all control components of the industrial control system. Step S902, the central node recalculates the second integrity protection summary of the system, e.g., the root hash value 300. Step S903, the central node judges whether the recalculated second integrity protection summary coincides with the stored second integrity protection summary or not; if coinciding, it indicates that each control component in the system and the firmware or configuration file thereof are normal and are not damaged or modified, then a signal about that the system is normal is output to the user in step S906; and if not coinciding, it indicates that the data of one or more control components in the industrial control system changes, the central node may further determine the data in which control component changes. Thus, the central node further recalculates the first integrity protection summary of each control component in step S904, and then executes matching in step S905, i.e., matching the recalculated first integrity protection summary with the stored first integrity protection summary of the corresponding control component, if matching, it indicates that the control component is normal; if not matching, it indicates that the data in the control component changes, and the central node can determine the control component having the data change according to the extracted identity feature information, and then notifies the user of the control component having data abnormality.  The preferred embodiments of the present invention are described above in combination with examples. Understandably, the method or the central node disclosed herein may be implemented by software, hardware or a combination of hardware and software. FIG10 shows a data integrity protection device implemented by program modules or hardware modules according to an embodiment of the present invention. As shown in FIG10, the data integrity protection device includes a correlation establishment module 101 and a summary generation module 102. The correlation establishment module 101 is configured to establish a correlation among a plurality of control components in an industrial control system, e.g., to rank the n control components, so that the data integrity summary generated for each control component is only correlated to one or all of the control components previous to the control component. The summary generation module 102 is configured to determine a summary indicating the integrity of data to be protected in the kth control component based on identity features and data features of other control components correlated to any control component (e.g., the kth control component among the n control components) among the n control components.
flow diagram, schematic diagram
101
correlation establishment module
102
summary generation module
10
andFIG.
['10. A data integrity protection device, comprising: a correlation establishment module (101), configured to establish a correlation among a plurality of control components in an industrial control system; and a summary generation module (102), configured to determine a summary indicating the integrity of data to be protected in a first control component based on identity features and data features of other control components correlated to the first control component among the plurality of control components, wherein the data features are used for identifying the data to be protected in the control components, and the first control component is any one of the plurality of control components, wherein the summary generation module is further configured to: determine a first integrity protection summary specific to the first control component, the first integrity protection summary being only used for indicating the integrity of the data to be protected in the first control component, and determine a second integrity protection summary shared by the plurality of control components including the first control component, the second integrity protection summary being used for indicating the integrity of the data to be protected in the plurality of control components, wherein the summary generation module is further configured to determine the second integrity protection summary based on the identity feature and the data feature of each of the plurality of control components, and to distribute the second integrity protection summary to each of the plurality of control components.']