Data synchronization method and system for heterogeneous system
By acquiring and updating the security level of data in heterogeneous systems and matching corresponding security measures, the problem of insufficient data synchronization security in heterogeneous systems is solved, and effective data supervision and synchronization security are achieved.
Patent Information
- Application Number
- CN202411228208.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-03
- Publication Date
- 2025-01-03
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
The prior art lacks effective data supervision and data synchronization security in heterogeneous systems, and fails to effectively limit data synchronization.
By obtaining the initial security level of data and updating records, the security level of data is automatically calculated and updated, and corresponding security measures are matched to limit data synchronization, achieving effective supervision and security improvement of data.
By characterizing the importance of data at the security level, data synchronization is improved and long-term supervision is achieved, ensuring effective supervision and synchronization security of data in heterogeneous systems.
Smart Images
Figure CN119248876A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to a data synchronization method and system for heterogeneous systems. Background Art
[0002] In actual production, there are often many different systems, such as financial systems, human resources systems, customer relationship management systems, etc. These systems may use different technologies and platforms and need to be integrated and consolidated to achieve information sharing and business process collaboration, thus forming a heterogeneous system. It can be understood that the study of heterogeneous systems can optimize information sharing and business process collaboration. Therefore, the study of the application of heterogeneous systems is necessary. Data synchronization, as a significant functional feature of heterogeneous systems, exposes the following problems in actual applications:
[0003] 1. Lack of effective supervision when data is stored in heterogeneous systems;
[0004] 2. The security of data synchronization is not considered when performing data synchronization, or data synchronization is limited only through simple and unchanging verification.
[0005] In summary, the existing technology urgently needs a technical solution that can be used in heterogeneous systems to achieve effective data supervision and improve data synchronization security. Summary of the invention
[0006] The purpose of this application is to provide a data synchronization method and system for heterogeneous systems to solve the technical problems raised in the above background technology.
[0007] To achieve the above objectives, this application discloses the following technical solutions:
[0008] In a first aspect, the present application discloses a data synchronization method for a heterogeneous system, the method comprising:
[0009] S1: Obtaining a first security level of data; the first security level is used to identify the importance of data;
[0010] S2: using the first security level to match security measures in a preset security measure library, obtaining a first security measure and applying it to the data; the security measure library stores security measures corresponding to different security levels, and the security measures are used to limit the execution of data synchronization;
[0011] S3: Preset a security verification cycle, obtain the update record of the data within the security verification cycle, and automatically calculate and update the second security level of the data based on the update record; the second security level is used to identify the importance of the updated data;
[0012] S4: using the second security level to match security measures in the security measures library, obtaining a second security measure and applying it to the data;
[0013] S5: Repeat steps S3 to S5, update the second security level and correspondingly update the second security measure and then apply it to the data until a stop-update constraint condition is met; the stop-update constraint condition is used to terminate the update of the security level of the data.
[0014] Preferably, a data security level table is set in the heterogeneous system and a corresponding security level identifier is set, and the corresponding security level identifier is set when the data is first stored in the heterogeneous system; the first security level of the acquired data specifically includes:
[0015] The security level identifier set when the data is first stored in the heterogeneous system is obtained to obtain the first security level.
[0016] Preferably, the method is characterized in that obtaining the first security measure and acting on the data specifically includes:
[0017] The first security measure is executed on the data when there is a data synchronization instruction.
[0018] Preferably, the security measures are used to limit the execution of data synchronization, and specifically include:
[0019] The first security measure and the second security measure are different security measures;
[0020] The security measure is based on a preset synchronization permission condition to determine whether the real-time synchronization condition satisfies the synchronization permission condition. If yes, the data synchronization instruction is allowed to be executed; otherwise, the data synchronization instruction is refused to be executed.
[0021] Preferably, the obtaining of update records of data within a security verification cycle specifically includes:
[0022] The number of times P that the statistical data is modified within a security verification cycle;
[0023] The number of devices Q corresponding to the modification of the statistical data within a security verification cycle in the heterogeneous system;
[0024] Calculate the operation score by calculating the number of operators R and the authority points S corresponding to the operators in the heterogeneous system when the statistical data is modified within a security verification cycle. The operation score is used to characterize the change in the importance of data after being operated by a human;
[0025] The number of modifications, the number of devices, and the operation score are packaged and defined as the update record.
[0026] Preferably, the second security level of the data automatically calculated and updated based on the update record specifically includes:
[0027] The upgrade index of the data is calculated using the security level upgrade judgment formula, wherein the security level upgrade judgment formula is specifically:
[0028] UpI=α1*RTUF+α2*DUF
[0029]
[0030] Among them, OS T-1 is the operational score of the T-1th security verification cycle, OS T is the operation score of the Tth security verification cycle, Q T-1 is the number of devices in the T-1th safety verification cycle, Q T is the number of devices in the Tth security verification cycle, P T-1 is the number of modifications in the T-1th security verification cycle, P T is the number of modifications in the Tth security verification cycle, | | is the absolute value operator, DUF is the deviation update factor, Dur is the duration corresponding to the security verification cycle, RTUF is the real-time update factor, α2 is the partial positive update factor correction parameter, α1 is the real-time update factor correction parameter, and UpI is the upgrade indicator;
[0031] An upgrade indicator threshold is preset, and when the upgrade indicator is greater than or equal to the upgrade indicator threshold, it is determined that the security level of the data is updated and upgraded, and the upgraded security level is defined as the second security level.
[0032] Preferably, obtaining the second security measure and acting on the data specifically includes:
[0033] The second security measure is executed on the data when the data synchronization instruction is present.
[0034] Preferably, the repeatedly executing steps S3 to S5 specifically includes:
[0035] Based on the time series and the security supervision cycle, the update record is repeatedly obtained, the second security level of the data is automatically calculated and updated, and the second security measure is obtained and applied to the data.
[0036] Preferably, the stop updating constraint condition is specifically:
[0037]
[0038] Where: SUS is the stop update signal score, when there is a stop update signal, SUS = 1, otherwise SUS = 0; DUF τ is the deviation update factor threshold; (a), (b) and (c) are the corresponding condition numbers;
[0039] When any one of (a), (b) and (c) is satisfied, the updating of the second security level is stopped.
[0040] In a second aspect, the present application discloses a data synchronization system for heterogeneous systems, the system is applicable to the data synchronization method for heterogeneous systems as described above, and the system includes:
[0041] A first security level acquisition module, wherein the first security level acquisition module is configured to: acquire a first security level of the data; the first security level is used to identify the importance of the data;
[0042] A first security measure module, wherein the first security measure module is configured to: use the first security level to match security measures in a preset security measure library, obtain a first security measure and apply it to data; the security measure library stores security measures corresponding to different security levels, and the security measures are used to limit the execution of data synchronization;
[0043] A second security level acquisition module, wherein the second security level acquisition module is configured to: preset a security verification cycle, acquire an update record of data within the security verification cycle, and automatically calculate and update the second security level of the data based on the update record; the second security level is used to identify the importance of the updated data;
[0044] A second security measure module, wherein the second security measure module is configured to: use the second security level to perform security measure matching in the security measure library, obtain a second security measure and act on the data;
[0045] A long-term supervision module, wherein the long-term supervision module is configured as follows: repeatedly running the second security level acquisition module and the second security measure module based on a time series, updating the second security level and correspondingly updating the second security measure and then acting on the data until a stop update constraint condition is met; the stop update constraint condition is used to terminate the update of the security level of the data.
[0046] Beneficial effects: The data synchronization method and system for heterogeneous systems of the present application characterize the importance of data through security levels, improve the security of data synchronization by matching security measures based on security levels, achieve effective data supervision and long-term security guarantees through updating records and the corresponding process of upgrading the first security level to the second security level and the process of continuous updating of the second security level, and realize the optimization of data synchronization technology for heterogeneous systems to achieve effective data supervision and improve data synchronization security. BRIEF DESCRIPTION OF THE DRAWINGS
[0047] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without paying any creative work.
[0048] Figure 1 A flowchart of a data synchronization method for heterogeneous systems provided in an embodiment of the present application;
[0049] Figure 2 A structural block diagram of a data synchronization system for heterogeneous systems provided in an embodiment of the present application. DETAILED DESCRIPTION
[0050] The technical solutions in the embodiments of the present application are described clearly and completely below. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application.
[0051] In this article, the term "comprising" is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of more restrictions, the elements defined by the sentence "comprising..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0052] In a first aspect, this embodiment discloses Figure 1 A data synchronization method for a heterogeneous system is shown, the method comprising:
[0053] S1: Obtain the first security level of the data. The first security level is used to identify the importance of the data.
[0054] S2: Using the first security level to match security measures in a preset security measure library, obtain the first security measure and apply it to the data. The security measure library stores security measures corresponding to different security levels, and the security measures are used to limit the execution of data synchronization.
[0055] S3: Preset a security verification cycle, obtain the update record of the data within a security verification cycle, and automatically calculate and update the second security level of the data based on the update record. The second security level is used to identify the importance of the updated data.
[0056] S4: Use the second security level to match security measures in the security measures library, obtain the second security measure and apply it to the data.
[0057] S5: Repeat steps S3 to S5, update the second security level and correspondingly update the second security measure and then apply it to the data until the stop updating constraint condition is met. The stop updating constraint condition is used to terminate the update of the security level of the data.
[0058] In this embodiment, the importance of data is characterized by security levels, and the security of data synchronization is improved by matching security measures based on security levels. Effective data supervision and long-term security guarantees are achieved through update records and the corresponding process of upgrading the first security level to the second security level and the process of continuous updating of the second security level, thereby optimizing data synchronization technology for heterogeneous systems to achieve effective data supervision and improve data synchronization security.
[0059] Specifically, a data security level table is set in the heterogeneous system and a corresponding security level identifier is set, and a corresponding security level identifier is set when data is first stored in the heterogeneous system. Obtaining the first security level of the data specifically includes:
[0060] The security level identifier set when the data is first stored in the heterogeneous system is obtained to obtain the first security level.
[0061] By obtaining the first security level, a data basis is provided for matching security measures, and a data basis is provided for updating and upgrading the second security level.
[0062] It should be noted that the first security level in this embodiment is used to represent the security level set by the operator when the data is first stored and is fixed, and the second security level is based on the update record and the calculation of the upgrade index to determine whether it has changed after the upgrade. The change of the second security level reflects the result of long-term supervision of data and serves as a data reference for long-term guarantee of data synchronization security.
[0063] Specifically, it is characterized in that obtaining the first security measure and acting on the data specifically includes:
[0064] When there is a data synchronization instruction, the first security measure is executed on the data. The data synchronization instruction in this embodiment is specifically an instruction to instruct the data to synchronize data in the heterogeneous system after the data is modified, and generating the data synchronization instruction and detecting the data synchronization instruction are any one of the technologies involving data synchronization instructions in the existing heterogeneous system.
[0065] Specifically, security measures are used to limit the execution of data synchronization, including:
[0066] The first safety measure and the second safety measure are different safety measures.
[0067] The security measures are based on the preset synchronization permission conditions to determine whether the real-time synchronization conditions meet the synchronization permission conditions. If yes, the data synchronization instruction is allowed to execute; otherwise, the data synchronization instruction is refused to execute.
[0068] It should be noted that the security measures in this embodiment correspond to different security levels and are stored in a preset security measures library. The security measures provide verification requirements for data synchronization, which are the preset synchronization permission conditions mentioned above. In a simple example, for example, the corresponding security measures for a high security level require verification of the operator's identity and the location information of the operating device, and the corresponding security measures for a low security level require verification of the location information of the operating device. And the verification technology used in this embodiment is any one of the existing verification technologies. The determination of whether the real-time synchronization conditions in the previous text meet the synchronization permission conditions is to verify whether the verification requirements are met. The execution of the second security measure in the following text is the same as here, so the execution of the second security measure in the following text will not be repeated.
[0069] Specifically, the update records of data within a security verification cycle are obtained, including:
[0070] The number of modifications P of the statistical data within a security verification cycle. A high number of modifications indicates that the data is more important in the heterogeneous system.
[0071] The modification of statistical data within a security verification cycle corresponds to the number of devices Q in the heterogeneous system. A high number of devices means that the data is widely distributed in the heterogeneous system.
[0072] The statistical data is modified within a security verification cycle. The corresponding number of operators R in the heterogeneous system and the corresponding authority points S of the operators. The higher the authority points, the more important the operator's modification and synchronization are. The operation score is calculated. The operation score is used to represent the change in the importance of data after being operated by a person. The higher the score, the greater the importance of the data.
[0073] The number of modifications, number of devices and operation scores are packaged and defined as an update record.
[0074] In this embodiment, scientific setting of data supervision is achieved by obtaining update records, and an accurate data basis is provided for obtaining the second security level.
[0075] Specifically, the second security level of the data is automatically calculated and updated based on the update record, including:
[0076] The security level upgrade judgment formula is used to calculate the upgrade index of the data, wherein the security level upgrade judgment formula is specifically:
[0077] UpI=α1*RTUF+α2*DUF
[0078]
[0079] Among them, OS T-1 is the operational score of the T-1th security verification cycle, OS T is the operation score of the Tth security verification cycle, Q T-1 is the number of devices in the T-1th safety verification cycle, Q T is the number of devices in the Tth security verification cycle, P T-1 is the number of modifications in the T-1th security verification cycle, P T is the number of modifications in the Tth security verification cycle, | | is the absolute value operator, DUF is the deviation update factor, Dur is the duration corresponding to the security verification cycle, RTUF is the real-time update factor, α2 is the partial positive update factor correction parameter, α1 is the real-time update factor correction parameter, and UpI is the upgrade index.
[0080] The deviation update factor realizes the quantification of the update changes of data between the previous and subsequent security verification cycles. As a factor used to measure the update changes of data, it has a direct impact on the upgrade indicators.
[0081] The real-time update factor realizes the quantification of data updates in the current security verification cycle. As a factor used to measure data updates, it has a direct impact on the upgrade index.
[0082] An upgrade indicator threshold is preset. When the upgrade indicator is greater than or equal to the upgrade indicator threshold, it is determined that the security level of the data is updated and upgraded, and the upgraded security level is defined as the second security level.
[0083] It should be noted that the updating and upgrading of the data security level here specifically refers to calling a preset data security level table and a corresponding security level identifier to improve the data security level, thereby upgrading the security measures adopted for the data and improving the security of data synchronization.
[0084] Specifically, the second security measure is obtained and applied to the data, including:
[0085] A second security measure is performed on the data when there is a data synchronization instruction.
[0086] It should be noted that the second security measure in this embodiment is updated along with the second security level, and the change of the second security measure reflects the result of long-term guarantee of data synchronization security.
[0087] Specifically, steps S3 to S5 are repeatedly performed, specifically including:
[0088] Based on the time series and security supervision cycle, the update records are repeatedly obtained, the second security level of the data is automatically calculated and updated, and the second security measures are obtained and acted on the data.
[0089] In this embodiment, by continuously acquiring update records based on time series, the calculation of indicators is continuously upgraded, and the second security level and the corresponding second security measures are further updated, thereby achieving limited supervision of data in heterogeneous systems and ensuring the security of data synchronization, and optimizing data synchronization technology.
[0090] Specifically, the stop update constraint conditions are as follows:
[0091]
[0092] Where: SUS is the stop update signal score, when there is a stop update signal, SUS = 1, otherwise SUS = 0. τ is the deviation update factor threshold. (a), (b) and (c) are the corresponding condition numbers.
[0093] When any one of (a), (b) and (c) is satisfied, the updating of the second security level is stopped.
[0094] It should be noted that in this embodiment, unnecessary security measures caused by unlimited security level upgrades are avoided by presetting stop update constraints, wherein the stop update signal comes from an operator with corresponding authority points, RTUF=0 means that data modification has been stopped in the current security verification cycle, DUF≤DUF τ It indicates that the modification degree of the data in the current security verification cycle is within the acceptable deviation update factor threshold. Further, when the data that has stopped updating is modified again, the operator sets the first security level to bring the data back into the range that needs security level update.
[0095] In a second aspect, this embodiment discloses Figure 2A data synchronization system for heterogeneous systems is shown, and the system is applicable to the data synchronization method for heterogeneous systems as described above. The system includes:
[0096] The first security level acquisition module is configured to: acquire the first security level of the data. The first security level is used to identify the importance of the data.
[0097] The first security measure module is configured to: use the first security level to match security measures in a preset security measure library, obtain the first security measure and apply it to the data. The security measure library stores security measures corresponding to different security levels, and the security measures are used to limit the execution of data synchronization.
[0098] The second security level acquisition module is configured to: preset a security verification cycle, obtain the update record of the data within a security verification cycle, and automatically calculate and update the second security level of the data based on the update record. The second security level is used to identify the importance of the updated data.
[0099] The second security measure module is configured to: use the second security level to match the security measures in the security measure library, obtain the second security measure and act on the data.
[0100] The long-term supervision module is configured to: repeatedly run the second security level acquisition module and the second security measure module based on the time series, update the second security level and the corresponding second security measure, and then act on the data until the stop update constraint condition is met. The stop update constraint condition is used to terminate the update of the security level of the data.
[0101] It should be noted that the data synchronization system for heterogeneous systems of the present embodiment corresponds to the data synchronization method for heterogeneous systems mentioned above. Therefore, the contents not specifically described in the data synchronization system for heterogeneous systems of the present embodiment may have, but are not limited to, the same functional definition, working principle and technical effect as the data synchronization method for heterogeneous systems mentioned above, and are not elaborated in this text.
[0102] In summary, the data synchronization method and system for heterogeneous systems of the present embodiment characterize the importance of data through security levels, improve the security of data synchronization by matching security measures based on security levels, achieve effective supervision of data and long-term security guarantees through updating records and the corresponding process of upgrading the first security level to the second security level and the process of continuous updating of the second security level, and realize the optimization of data synchronization technology for heterogeneous systems to achieve effective data supervision and improve data synchronization security.
[0103] In the embodiments provided in the present application, it should be understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, code or any appropriate combination thereof. For hardware implementation, the processor can be implemented in one or more of the following units: application specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing device (DSPD), programmable logic device (PLD), field programmable gate array (FPGA), processor, controller, microcontroller, microprocessor, other electronic units designed to implement the functions described herein or their combination. For software implementation, part or all of the flow of the embodiment can be completed by instructing the relevant hardware through a computer program. When implemented, the above program can be stored in a computer-readable storage medium or transmitted as one or more instructions or codes on a computer-readable storage medium. Computer-readable storage media include computer storage media and communication media, wherein the communication medium includes any medium that is convenient for transmitting a computer program from one place to another. The storage medium can be any available medium that a computer can access. The computer-readable storage medium can include but is not limited to RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer.
[0104] Finally, it should be noted that the above is only a preferred embodiment of the present application and is not intended to limit the present application. Although the present application has been described in detail with reference to the aforementioned embodiments, it is still possible for those skilled in the art to modify the technical solutions described in the aforementioned embodiments or to make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.
Claims
1. A data synchronization method for heterogeneous systems, characterized in that: The method includes: S1: Obtaining a first security level of data; the first security level is used to identify the importance of data; S2: using the first security level to match security measures in a preset security measure library, obtaining a first security measure and applying it to the data; the security measure library stores security measures corresponding to different security levels, and the security measures are used to limit the execution of data synchronization; S3: Preset a security verification cycle, obtain the update record of the data within the security verification cycle, and automatically calculate and update the second security level of the data based on the update record; the second security level is used to identify the importance of the updated data; S4: using the second security level to match security measures in the security measures library, obtaining a second security measure and applying it to the data; S5: Repeat steps S3 to S5, update the second security level and correspondingly update the second security measure and then apply it to the data until a stop-update constraint condition is met; the stop-update constraint condition is used to terminate the update of the security level of the data.
2. The data synchronization method for heterogeneous systems according to claim 1, characterized in that: Setting a data security level table and a corresponding security level identifier in the heterogeneous system, and setting the corresponding security level identifier when data is first stored in the heterogeneous system; The first security level for acquiring data specifically includes: The security level identifier set when the data is first stored in the heterogeneous system is obtained to obtain the first security level.
3. The data synchronization method for heterogeneous systems according to claim 1, characterized in that: The obtaining of the first security measure and acting on the data specifically includes: The first security measure is executed on the data when there is a data synchronization instruction.
4. The data synchronization method for heterogeneous systems according to claim 3, characterized in that: The security measures are used to limit the execution of data synchronization, and specifically include: The first security measure and the second security measure are different security measures; The security measure is based on a preset synchronization permission condition to determine whether the real-time synchronization condition satisfies the synchronization permission condition. If yes, the data synchronization instruction is allowed to be executed; otherwise, the data synchronization instruction is refused to be executed.
5. The data synchronization method for heterogeneous systems according to claim 1, characterized in that: The obtaining of update records of data within a security verification cycle specifically includes: The number of times P that the statistical data is modified within a security verification cycle; The number of devices Q corresponding to the modification of the statistical data within a security verification cycle in the heterogeneous system; Calculate the operation score by calculating the number of operators R and the authority points S corresponding to the operators in the heterogeneous system when the statistical data is modified within a security verification cycle. The operation score is used to characterize the change in the importance of data after being operated by a human; The number of modifications, the number of devices, and the operation score are packaged and defined as the update record.
6. The data synchronization method for heterogeneous systems according to claim 5, characterized in that: The second security level of the data automatically calculated and updated based on the update record specifically includes: The upgrade index of the data is calculated using the security level upgrade judgment formula, wherein the security level upgrade judgment formula is specifically: UpI=α1*RTUF+α2*DUF Among them, OS T-1 is the operational score of the T-1th security verification cycle, OS T is the operation score of the Tth security verification cycle, Q T-1 is the number of devices in the T-1th safety verification cycle, Q T is the number of devices in the Tth security verification cycle, P T-1 is the number of modifications in the T-1th security verification cycle, P T is the number of modifications in the Tth security verification cycle, | | is the absolute value operator, DUF is the deviation update factor, Dur is the duration corresponding to the security verification cycle, RTUF is the real-time update factor, α2 is the partial positive update factor correction parameter, α1 is the real-time update factor correction parameter, and UpI is the upgrade indicator; An upgrade indicator threshold is preset, and when the upgrade indicator is greater than or equal to the upgrade indicator threshold, it is determined that the security level of the data is updated and upgraded, and the upgraded security level is defined as the second security level.
7. The data synchronization method for heterogeneous systems according to claim 4, characterized in that: The obtaining of the second security measure and acting on the data specifically includes: The second security measure is executed on the data when the data synchronization instruction is present.
8. The data synchronization method for heterogeneous systems according to claim 1, characterized in that: The repeatedly executing steps S3 to S5 specifically includes: Based on the time series and the security supervision cycle, the update record is repeatedly obtained, the second security level of the data is automatically calculated and updated, and the second security measure is obtained and applied to the data.
9. The data synchronization method for heterogeneous systems according to claim 6, characterized in that: The stop updating constraint conditions are specifically: Where: SUS is the stop update signal score, when there is a stop update signal, SUS = 1, otherwise SUS = 0; DUF τ is the deviation update factor threshold; (a), (b) and (c) are the corresponding condition numbers; When any one of (a), (b) and (c) is satisfied, the updating of the second security level is stopped.
10. A data synchronization system for heterogeneous systems, the system being applicable to the data synchronization method for heterogeneous systems as claimed in any one of claims 1 to 9, characterized in that: The system includes: A first security level acquisition module, wherein the first security level acquisition module is configured to: acquire a first security level of the data; the first security level is used to identify the importance of the data; A first security measure module, wherein the first security measure module is configured to: use the first security level to match security measures in a preset security measure library, obtain a first security measure and apply it to data; the security measure library stores security measures corresponding to different security levels, and the security measures are used to limit the execution of data synchronization; A second security level acquisition module, wherein the second security level acquisition module is configured to: preset a security verification cycle, acquire an update record of data within the security verification cycle, and automatically calculate and update the second security level of the data based on the update record; the second security level is used to identify the importance of the updated data; A second security measure module, wherein the second security measure module is configured to: use the second security level to perform security measure matching in the security measure library, obtain a second security measure and act on the data; A long-term supervision module, wherein the long-term supervision module is configured as follows: repeatedly running the second security level acquisition module and the second security measure module based on a time series, updating the second security level and correspondingly updating the second security measure and then acting on the data until a stop update constraint condition is met; the stop update constraint condition is used to terminate the update of the security level of the data.