Webpage tamper-proofing system and method

Abstract

The invention discloses a webpage tamper-proofing system and method. The system comprises a source file storage server and a central storage server of an intranet and an external server of an extranet, the source file is synchronized to the central storage server by the source file storage server and is synchronized to the external server by the central storage server; under the condition that the file stored in the central storage server is inconsistent with the source file, covering the file stored in the central storage server with the source file; and under the condition that the files stored in the external server are inconsistent with the files stored in the central storage server, covering the files stored in the external server with the files stored in the central storage server. Two-stage synchronous storage is carried out by utilizing a source file storage server and a central storage server in an intranet, files are synchronously stored by utilizing an external server in an external network, and file coverage is carried out when the files stored in the two-stage servers or the files stored in the intranet and the external network are inconsistent so as to ensure the consistency of the files stored in the servers, so that a webpage is prevented from being tampered; and the webpage security is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a web page tamper-proofing system and method. Background Art

[0002] Given the high security and stability requirements, web application systems generally require off-site disaster recovery deployment. Effectively preventing external web pages from being attacked or tampered with helps mitigate the negative impacts caused by abnormal website access or web pages being tampered with to create illegal content. With off-site disaster recovery deployment, it's crucial to ensure the consistency of files generated or uploaded by the system across all storage devices.

[0003] Currently, the main method for file synchronization and storage is to install synchronization software and a database or Redis on the server. A monitoring agent is then installed on the front-end site. When a file change is detected, the file or feature on the synchronization end is compared to confirm whether the file has been tampered with and then the file is restored. This method has the following disadvantages: 1) Most anti-tampering software uses server system event monitoring or file scanning to synchronize and protect differential files, which cannot guarantee the consistency of web page files on various Internet servers; 2) Most commercial anti-tampering software uses operating system events or cache technologies such as databases or Redis to achieve file comparison, but traditional database or Redis technologies carry the risk of human tampering; 3) After the anti-tampering software stops serving, the anti-tampering protection will become ineffective and cannot be detected in time. Overall, existing methods are difficult to reliably prevent web page tampering in real time, and web page security needs to be improved. Summary of the Invention

[0004] The present application provides a web page anti-tampering system and method to prevent web pages from being tampered with and improve web page security.

[0005] In a first aspect, an embodiment of the present application provides a webpage anti-tampering system, comprising:

[0006] Source file storage servers and central storage servers located on the intranet, and external servers located on the extranet;

[0007] The source file storage server is used to store source files of web pages, and the source files are synchronized from the source file storage server to the central storage server, and then synchronized from the central storage server to the external server;

[0008] The source file storage server is further configured to overwrite the file stored in the central storage server with the source file when the file stored in the central storage server is inconsistent with the source file;

[0009] The central storage server is further configured to overwrite the file stored in the external server with the file stored in the central storage server when the file stored in the external server is inconsistent with the file stored in the central storage server.

[0010] In a second aspect, an embodiment of the present application further provides a webpage anti-tampering method, which is applied to the webpage anti-tampering system as described in the first aspect, and the method includes:

[0011] When the file stored in the central storage server is inconsistent with the source file, the source file storage server overwrites the file stored in the central storage server with the source file;

[0012] When the file stored in the external server is inconsistent with the file stored in the central storage server, the central storage server overwrites the file stored in the external server with the file stored in the central storage server.

[0013] The embodiment of the present application provides a web page anti-tampering system and method. The system includes: a source file storage server and a central storage server in the intranet and an external server in the external network; the source file is synchronized from the source file storage server to the central storage server and then synchronized from the central storage server to the external server; when the file stored in the central storage server is inconsistent with the source file, the source file is used to overwrite the file stored in the central storage server; when the file stored in the external server is inconsistent with the file stored in the central storage server, the file stored in the external server is overwritten with the file stored in the central storage server. The above technical solution uses the source file storage server and the central storage server in the intranet to perform two-level synchronous storage, and uses the external server in the external network to synchronize the storage of files. When the files stored in the two-level servers or the internal and external networks are inconsistent, the files are overwritten to ensure the consistency of the files stored on each server, thereby preventing the web page from being tampered with and improving the security of the web page. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The above and other features, advantages, and aspects of the various embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that the originals and elements are not necessarily drawn to scale.

[0015] Figure 1 A schematic diagram of the structure of a webpage anti-tampering system provided in an embodiment of the present application;

[0016] Figure 2 A schematic diagram of an implementation of a web page synchronization storage process provided by an embodiment;

[0017] Figure 3A schematic diagram illustrating implementation of overwriting or incremental synchronization when files are changed, provided in one embodiment;

[0018] Figure 4 A schematic diagram of an internal and external network deployment for web page tamper prevention provided by an embodiment;

[0019] Figure 5 A flowchart of a web page anti-tampering method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] The present application will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are intended only to illustrate the present application and are not intended to limit the present application. It should also be noted that, for ease of description, the accompanying drawings only illustrate portions of the present application, not all of the structures.

[0021] Before discussing the exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe the steps as sequential processes, many of the steps can be implemented in parallel, concurrently, or simultaneously. In addition, the order of the steps can be rearranged. The process can be terminated when its operation is completed, but can also have additional steps not included in the accompanying drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0022] It should be noted that the concepts of "first" and "second" mentioned in the embodiments of this application are only used to distinguish different devices, modules, units or other objects, and are not used to limit the order or interdependence of the functions performed by these devices, modules, units or other objects.

[0023] In addition, the embodiments and features in the embodiments of the present application may be combined with each other unless there is any conflict.

[0024] The acquisition, storage, use, and processing of data in this application's technical solution comply with relevant national laws and regulations.

[0025] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned. They should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the relevant content of the solution.

[0026] Figure 1 This is a structural diagram of a webpage anti-tampering system provided in an embodiment of the present application. This embodiment is applicable to the case of real-time webpage anti-tampering of video data. Figure 1 As shown, the system includes:

[0027] A source file storage server 10 and a central storage server 20 are set up in the intranet, and an external server 30 is set up in the external network; the source file storage server 10 is used to store the source files of the web page, and the source files are synchronized from the source file storage server 10 to the central storage server 20, and synchronized from the central storage server 20 to the external server 30. It should be noted that the intranet and the external network are isolated, that is, the internal network of the enterprise and the external Internet are physically or logically isolated to protect the security of internal data and prevent external attacks and data leakage. In the intranet, the source file storage server 10 and the central storage server 20 are used to perform two-level synchronous storage of the source files of the web page; in the external network, the external server 30 can be understood as the third-level storage; between the intranet and the external network, the central storage server 20 synchronizes its stored files to the external server 30.

[0028] For example, there is one source file storage server 10, and there can be multiple central storage servers 20, thereby achieving multi-site disaster recovery. There can also be multiple external servers 30, each of which is synchronized with a corresponding central storage server 20. The relationship between the central storage server 20 and the external servers 30 can be one-to-one or one-to-many. Unless otherwise specified, the embodiments of this application use the case where one central storage server 20 corresponds to one external server 30 as an example.

[0029] The source file storage server 10 is also used to overwrite the files stored in the central storage server 20 with the source files when the files stored in the central storage server 20 are inconsistent with the source files; the central storage server 20 is also used to overwrite the files stored in the external server 30 with the files stored in the central storage server 20 when the files stored in the external server 30 are inconsistent with the files stored in the central storage server 20.

[0030] For example, the consistency of the files stored on the two servers can be determined by using the signature codes, hash values, or other unique identifiers of the files stored on the two servers. These identifiers are generated in real time based on the files. Once the files change (abnormality) the corresponding identifiers will also change. If the files (identifiers) stored on the two-level servers are inconsistent, it means that the file stored on the latter-level server has been tampered with. In this case, the tampered file can be overwritten with the file stored on the previous-level server of the tampered server, thereby ensuring that the files stored on each level of the server are consistent with the source files stored on the source file storage server 10. On this basis, web pages can be reliably prevented from being tampered with in real time, improving web page security and protection reliability.

[0031] In one embodiment, the source file storage server 10 is also used to overwrite the file stored in the central storage server 20 with the source file when the file stored in the external server 30 is inconsistent with the source file and the file stored in the central storage server 20 is inconsistent with the source file; the central storage server 20 is also used to overwrite the file stored in the external server 30 with the file overwritten by the central storage server 20 when the file stored in the external server 30 is inconsistent with the source file and the file stored in the central storage server 20 is inconsistent with the source file.

[0032] In this embodiment, if the files stored on both the central storage server 20 and the external server 30 are tampered with, the source file on the source file storage server 10 will overwrite the file stored on the central storage server 20, and then the file stored on the external server 30 will be overwritten with the file stored on the central storage server 20. In other words, while ensuring the consistency of the files stored on both servers, the files stored on each server level can be guaranteed to be consistent with the source files. It will be appreciated that whenever a file stored on the central storage server 20 is overwritten by the source file, the central storage server 20 will also overwrite the file stored on the external server 30 with the latest file stored on it.

[0033] In one example, leveraging the isolation between the intranet and external networks, the source files for a website's webpages can be placed on an intranet source file server (SS). These files are then synchronized to three internal central storage servers (IS) at locations A, A1, and B within the intranet. These servers then synchronize the files to the corresponding external server clusters (ES) at locations A, A1, and B, which serve as the internet portals. If a file on the internet portal cluster ES is tampered with, the ES and IS are automatically compared for consistency. If any inconsistency is found, the IS file is promptly synchronized to the ES to overwrite it, preventing the accessed webpage from being tampered with. If a file on the ES is tampered with through an illegal attack, the SS and ES files are automatically compared for consistency. The SS source file is then overwritten on the IS, and the IS is then overwritten on the ES, completing the restoration of the tampered file's source file.

[0034] In one embodiment, the source file storage server 10 is further used to generate a first hash value for the source file in real time; the central file storage is further used to generate a second hash value for the file stored in the central file storage in real time; the external server 30 is further used to generate a third hash value for the file stored in the external server 30 in real time; the first hash value and the second hash value are stored in the first blockchain; and the third hash value is stored in the second blockchain.

[0035] In this embodiment, a hash algorithm (also known as a hash function, hash function, or digest algorithm) can be used to generate a fixed-length unique identifier, i.e., a hash value (also known as a hash value or message digest), for data of any length. For example, each server level can use the SM3 algorithm in the national encryption algorithm to generate corresponding hash values ​​in real time for static resources (such as web pages or images) in its stored files.

[0036] Furthermore, the hash values ​​of files stored on servers at all levels can be stored in the blockchain. The blockchain can be understood as a decentralized distributed ledger that is tamper-proof, secure, and reliable, with block chain storage. Transactions and information can be recorded through a growing data block chain to ensure data security and transparency. The hash values ​​of files stored on the intranet (i.e., the first hash value and the second hash value) can be stored on the chain corresponding to the intranet (i.e., the first blockchain, also known as a private chain), and the hash values ​​of files stored on the external network (i.e., the third hash value) can be stored on the chain corresponding to the external network (i.e., the second blockchain, also known as a private sub-chain). On this basis, by writing the hash value into the enterprise's lightweight private chain, each service node corresponds to a chain node, which can realize blockchain evidence storage, use the hash value to achieve tamper-proof and distributed verification, and effectively prevent a node from being tampered with or invalidated.

[0037] In one embodiment, the central storage server 20 is further used to determine whether the file stored in the central storage server 20 is consistent with the source file based on the real-time second hash value of the file stored on the central storage server 10 and the second hash value stored on the first blockchain; the external server 30 is further used to determine whether the file stored on the external server 30 is consistent with the file stored on the central storage server 20 based on the real-time third hash value of the file stored on the external server and the third hash value stored on the second blockchain.

[0038] Figure 2 FIG. 1 is a schematic diagram of an implementation of a web page synchronization storage process provided by an embodiment. Figure 2 As shown, the central source file is the file stored on the central storage server 20, and the central website is the external server. The file publishing system can generate or modify the page for publication. After publication, the newly added file hash is stored on the private chain. For modified or deleted files, the records on the private chain can also be modified or deleted accordingly. After the file hash is stored, the source file can be stored on the source file system of the intranet and synchronized to the central storage server in each location. The central storage server in each location is then synchronized to the corresponding external server in the external network. The hash value of the stored file is stored in the blockchain. If the hash value of the sub-link changes, it is considered that the file has been tampered with and can be overwritten by synchronizing with the source file.

[0039] In one embodiment, the source file storage server 10 is also used to synchronize the source file increments to the central storage server 20 when the source file is modified or newly added; the central storage server 20 is also used to synchronize the file increments stored in the central storage server 20 to the external server 30 when the files stored in the central storage server 20 are modified or newly added.

[0040] In this embodiment, new files can be incrementally synchronized, with source files being synchronized to each central storage device via synchronization tasks. The file hash is compared with the hash on the private chain in real time. If there is a discrepancy, the abnormal file is overwritten from the source storage to the central source storage. Furthermore, when new or updated source files are detected in each central source file, the file is incrementally synchronized to the external service website server, completing the file release process from generation to external service provision.

[0041] It is important to note that the overwriting process can also be done using incremental synchronization. By optimizing incremental synchronization, only the hash differences can be synchronized, reducing cross-region bandwidth consumption.

[0042] Figure 3 This is a schematic diagram of implementing overwriting or incremental synchronization when files are changed in one embodiment. Taking the above-mentioned locations A, A1, and B as an example, each of which has a central storage server and a corresponding external server, the central source file is the file stored in the central storage server, and the central web site is the external server. Figure 3 As shown, if a file on any central website changes, consistency comparison can be used to determine if the file on the central website has been tampered with. The tampered file will be overwritten in real time with the corresponding central source file. If a file stored on any central storage server changes, consistency comparison can be used to determine if the central source file has been tampered with. The tampered file will be overwritten in real time with the source file. In addition, if the source file is modified or added, the modified or added file can be incrementally synchronized, thereby reducing bandwidth pressure and processing volume.

[0043] Optionally, you can adopt zero-trust authorization and least privilege strategies, that is, each modification of the source file content requires multi-factor authentication, such as using dynamic passwords + biometrics for authentication. Each change requires a separate application for operation permissions and generates a one-time operation token, which expires immediately after the operation.

[0044] In one embodiment, each external server 30 provides domain name mapping external services based on load balancing.

[0045] For example, load balancing can be achieved by using F5 (load balancing device). Generally, a load balancing device can be composed of multiple external servers. When external access is made, the access will be evenly distributed to each external server according to the configuration balance.

[0046] Figure 4 This is a schematic diagram of an internal and external network deployment for web page tamper prevention provided by an embodiment. Figure 4 As shown, the central source storage is the storage of the central storage server, and the central website is the storage of the external server.

[0047] The source files for webpage content are stored on source file storage servers, divided into two levels of storage: source file storage and central source file storage. Externally serving websites are deployed in the Internet extension zone and do not directly provide external services. Instead, they utilize a load balancing F5 server to provide domain name mapping for external services. F5 servers are deployed in the Internet service zone, directly facing internet customers, to isolate internal and external networks, making illegal attacks and tampering more difficult.

[0048] The web page anti-tampering system of the embodiment of the present application adopts dynamic hashing and blockchain for file comparison between servers at all levels, which can ensure that each file upload or distribution can effectively monitor whether it is distributed to all front-end servers, thereby ensuring the consistency of the file; it adopts blockchain evidence storage and takes advantage of its tamper-proof nature to enhance the credibility of verification. When a dispute occurs, it can provide on-chain evidence to prove the original state of the content. Databases or caches are likely to be tampered with from the source, and blockchain can effectively avoid similar operations; in addition, it can reduce potentially risky operations or infiltrations based on zero-trust authorization to avoid the possibility of files being tampered with from the source; and it can timely issue alarms through real-time detection of file consistency, whether the system automatically recovers or human intervention can be handled in a timely manner; by incrementally synchronizing hash difference files, cross-regional bandwidth consumption is reduced and tampered files are quickly overwritten.

[0049] Figure 5 This is a flowchart of a webpage anti-tampering method provided in an embodiment of the present application. This embodiment can be applied to the case of real-time webpage anti-tampering of video data. This method can be applied to the webpage anti-tampering system described in any of the above embodiments. It should be noted that the technical details not fully described in this embodiment can be referred to any of the above embodiments. Figure 5 As shown, the method includes:

[0050] S110: If the file stored in the central storage server is inconsistent with the source file, the source file storage server overwrites the file stored in the central storage server with the source file;

[0051] S120: When the file stored in the external server is inconsistent with the file stored in the central storage server, the central storage server overwrites the file stored in the external server with the file stored in the central storage server.

[0052] The webpage anti-tampering method of this embodiment uses a source file storage server and a central storage server in the intranet to perform two-level synchronous storage, and uses an external server in the extranet to synchronously store files. When the files stored on the two-level servers or on the intranet and extranet are inconsistent, the files are overwritten to ensure the consistency of the files stored on each server, thereby preventing the webpage from being tampered with and improving the security of the webpage. In one embodiment, the method further includes:

[0053] S130. When the file stored on the external server is inconsistent with the source file, and the file stored on the central storage server is inconsistent with the source file, the source file storage server overwrites the file stored on the central storage server with the source file; the central storage server overwrites the file stored on the external server with the file overwritten by the central storage server.

[0054] In one embodiment, the method further comprises:

[0055] S101: The source file storage server generates a first hash value for the source file in real time, and the first hash value is stored in a first blockchain;

[0056] S102: The central file storage device generates a second hash value for the file stored in the central file storage device in real time, and the second hash value is stored in the first blockchain;

[0057] S103. The external server generates a third hash value for the file stored on the external server in real time, and the third hash value is stored in the second blockchain;

[0058] The source file storage server determines whether the file stored on the central storage server is consistent with the source file based on the real-time second hash value of the file stored on the central storage server and the second hash value stored on the first blockchain;

[0059] The central storage server determines whether the file stored on the external server is consistent with the file stored on the central storage server based on the real-time third hash value of the file stored on the external server and the third hash value stored on the second blockchain.

[0060] In one embodiment, the method further comprises:

[0061] S140: When the source file is modified or newly added, the source file storage server synchronizes the source file increment to the central storage server;

[0062] S150: When a file stored in the central storage server is modified or newly added, the central storage server synchronizes the file increment stored in the central storage server to the external server.

[0063] The web page anti-tampering method provided in the embodiment of the present application can be applied to the web page anti-tampering system provided in any of the above embodiments, and has corresponding functions and beneficial effects.

[0064] In some embodiments, the method of the above embodiment can be implemented as a computer program, which is tangibly included in a computer-readable storage medium. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 10 via a ROM and / or a communication unit. When the computer program is loaded into the RAM and executed by the processor, one or more steps of the method described above can be performed. Alternatively, in other embodiments, the processor can be configured to perform any of the above-described embodiment methods by any other appropriate means (e.g., by means of firmware).

[0065] Various embodiments of the systems and techniques described 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), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0066] Computer programs for implementing the methods of the present application 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 the computer program is executed by the processor, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The computer program may be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0067] In the context of the present application, a computer-readable storage medium can be a tangible medium that can contain or store a computer program for use by an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. A computer-readable storage medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0068] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device 10 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 can provide input to the electronic device 10. Other types of devices can also be used to provide interaction with the user; for example, the 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 acoustic input, voice input, or tactile input).

[0069] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0070] A computing system may include clients and servers. The clients and servers are typically remote from each other and typically interact via a communication network. This client-server relationship arises through computer programs running on the respective computers, creating a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host. This server is a hosting product within the cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosting and VPS services.

[0071] An embodiment of the present application further provides a computer program product, including a computer program and / or instructions, which, when executed by a processor, implements the web page anti-tampering method as described in any of the above embodiments.

[0072] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this application can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of this application can be achieved. This is not limited herein.

[0073] The above specific embodiments do not constitute a limitation on the scope of protection of this application. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application shall be included within the scope of protection of this application.

Claims

1. A webpage anti-tampering system, characterized in that: include: Source file storage servers and central storage servers located on the intranet, and external servers located on the extranet; The source file storage server is used to store source files of web pages, and the source files are synchronized from the source file storage server to the central storage server, and then synchronized from the central storage server to the external server; The source file storage server is further configured to overwrite the file stored in the central storage server with the source file when the file stored in the central storage server is inconsistent with the source file; The central storage server is further configured to overwrite the file stored in the external server with the file stored in the central storage server when the file stored in the external server is inconsistent with the file stored in the central storage server.

2. The system according to claim 1, wherein: The source file storage server is further configured to overwrite the file stored in the central storage server with the source file when the file stored in the external server is inconsistent with the source file and the file stored in the central storage server is inconsistent with the source file; The central storage server is further configured to overwrite the file stored in the external server with the file overwritten by the central storage server when the file stored in the external server is inconsistent with the source file and the file stored in the central storage server is inconsistent with the source file.

3. The system according to claim 2, characterized in that The source file storage server is further configured to generate a first hash value for the source file in real time; the central file storage is further configured to generate a second hash value for the file stored in the central file storage in real time; and the external server is further configured to generate a third hash value for the file stored in the external server in real time. The first hash value and the second hash value are stored in the first blockchain; and the third hash value is stored in the second blockchain.

4. The system according to claim 3, characterized in that The central storage server is further configured to determine whether the file stored on the central storage server is consistent with the source file based on the real-time second hash value of the file stored on the central storage server and the second hash value stored on the first blockchain; The external server is further used to determine whether the file stored on the external server is consistent with the file stored on the central storage server based on the real-time third hash value of the file stored on the external server and the third hash value stored on the second blockchain.

5. The system according to claim 1, wherein: The source file storage server is further configured to synchronize the source file increments to the central storage server when the source file is modified or newly added; The central storage server is further configured to synchronize incremental files stored in the central storage server to the external server when files stored in the central storage server are modified or newly added.

6. The system according to claim 1, wherein: Each of the external servers provides domain name mapping external services based on load balancing.

7. A webpage anti-tampering method, characterized in that: Applied to a webpage anti-tampering system, the webpage anti-tampering system includes a source file storage server and a central storage server set up on an intranet, and an external server set up on an external network; the source file storage server is used to store source files of webpages, and the source files are synchronized from the source file storage server to the central storage server, and then synchronized from the central storage server to the external server; the method includes: When the file stored in the central storage server is inconsistent with the source file, the source file storage server overwrites the file stored in the central storage server with the source file; When the file stored in the external server is inconsistent with the file stored in the central storage server, the central storage server overwrites the file stored in the external server with the file stored in the central storage server.

8. The method according to claim 7, characterized in that Also includes: In the case that the file stored in the external server is inconsistent with the source file, and the file stored in the central storage server is inconsistent with the source file, The source file storage server overwrites the file stored in the central storage server with the source file; The central storage server overwrites the file stored in the external server with the file overwritten by the central storage server.

9. The method according to claim 7, characterized in that Also includes: The source file storage server generates a first hash value for the source file in real time, and the first hash value is stored in the first blockchain; The central file storage generates a second hash value for the file stored in the central file storage in real time, and the second hash value is stored in the first blockchain; The external server generates a third hash value for the file stored on the external server in real time, and the third hash value is stored in the second blockchain; The central storage server determines whether the file stored on the central storage server is consistent with the source file based on the real-time second hash value of the file stored on the central storage server and the second hash value stored on the first blockchain; The external server determines whether the file stored on the external server is consistent with the file stored on the central storage server based on the real-time third hash value of the file stored on the external server and the third hash value stored on the second blockchain.

10. The method according to claim 7, characterized in that Also includes: The source file storage server synchronizes the source file increments to the central storage server when the source file is modified or added; When the files stored in the central storage server are modified or newly added, the central storage server synchronizes the file increments stored in the central storage server to the external server.

Images