# US 2026/0087178 A1 · Methods and associated computer systems for ensuring the integrity of data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0087178 A1
- Document ID: US20260087178A1
- Status: Published application
- Kind: A1
- Application number: 19/405,004
- Filed: 2025-12-01
- Published: 2026-03-26
- Earliest claimed: 2021-11-08
- Assignees: KraLos GmbH
- Applicants: KraLos GmbH
- Inventors: Christian Clemens Greiwe; Carsten Klein
- Web page: https://patentgrep.com/patent/US20260087178A1

## CPC

- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06F 11/1458: {Management of the backup or restore process}
- G06F 21/52: during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- H04L 63/1458: {Denial of Service}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Method of protecting integrity of data including steps of running web service on primary, secure computer system including original, complete data set created by user. Generating intended state of data of the web service on primary, secure computer system, so intended state of data has frontend data, files and information relevant for visual design and interaction of the web service. Transferring intended data set through secure connection to secondary computer system(s) in potentially insecure network on which the web service is executed. Checking integrity of intended data set by detecting manipulation of the underlying information of intended data by an attacker, after manipulation, manipulated data is placed in quarantine and may be analyzed in further step but is no longer executed and thus cannot cause any damage. Restoring intended state of data at time before manipulation by transferring intended data set stored on primary computer system to secondary computer system(s), so manipulation of data has been detected.

## Claims

### Claim 1

A method of protecting the integrity of data comprising the following steps:
a) running a web service on a primary, secure computer system including an original, complete data set created by the user;
b) generating an intended state of the data of the web service on the primary, secure computer system, wherein the intended state of data comprises frontend data, files and information relevant for visual design and interaction of the web service;
c) transferring the intended data set through a secure connection to one or more secondary computer systems in a potentially insecure network on which the web service is executed;
d) checking the integrity of the intended data set by detecting manipulation of the underlying information of the intended data by an attacker, wherein after manipulation, the manipulated data is placed in quarantine and may be analyzed in a further step but is no longer executed and thus cannot cause any damage; and
e) restoring the intended state of the data at the time before manipulation by transferring the intended data set stored on the primary computer system to one or more secondary computer systems, wherein a manipulation of data has been detected.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the method comprises a self-destruction function, comprising the following steps:
a) contacting a deposited server (cockpit server);
b) receiving and reviewing responses of a cockpit server;
c) verifying an underlying script or several scripts;
and/or
d) receiving information of a monitoring mechanism (watchdog);
and initiating a self-destruction if
i) no response of the cockpit server has been received;
ii) an incorrect response has been received by the cockpit server;
iii) a change in a script and/or hash value has been detected; and/or
iv) an unallowable access has been detected.

### Claim 3 (depends on 2)

The method according to claim 2, wherein the contacting the deposited server (cockpit server) is made at regular or irregular intervals.

### Claim 4 (depends on 2)

The method according to claim 2, wherein the availability of the cockpit server (response) is checked several times.

### Claim 5 (depends on 2)

The method according to claim 2, wherein the verification of the underlying script or several scripts is performed after receiving a user's request.

### Claim 6 (depends on 5)

The method according to claim 5, wherein the underlying script is the Fileserver.php script.

### Claim 7 (depends on 2)

The method according to claim 2, wherein the self-destruction comprises the mixture of an underlying code of involved scripts, rendering the underlying code unusable and/or impossible to recover.

### Claim 8 (depends on 7)

The method according to claim 7, wherein the PHP function “str_shuffle( )” is used rendering the underlying code of involved scripts unusable and/or impossible to recover.

### Claim 9 (depends on 1)

The method according to claim 1, wherein data defined by a user is registered for checking for manipulations, or data defined by a user is excluded from checking for manipulations.

### Claim 10 (depends on 1)

The method according to claim 1, wherein checking the integrity of the intended data set is performed immediately after manipulating the intended data set.

### Claim 11 (depends on 1)

The method according to claim 1, wherein triggering the transferring of the intended data set from the primary computer system to the one or more secondary computer systems
a) is triggered manually, or
b) is triggered automatically on a time-controlled basis, or
c) is triggered automatically after changing the intended state of the data.

### Claim 12 (depends on 1)

The method according to claim 1, wherein the data for generating the web service is selected from a database, and wherein the integrity of the data in the database is secured, wherein
a) either each query to the database is first checked for corrupt entries, then transmitted in a secured manner to the primary database of the primary computer system and subsequently the changes made are mirrored to a secondary database in the secondary computer system, or
b) each request to the database is first checked for malicious entries and then transmitted in a secured manner to the primary computer system, and read accesses to the database, in particular by an agent, are also checked and transmitted to the primary computer system, so that no database is required in the secondary system, or
c) the secondary database in the one or more secondary computer systems is checked regularly for changes to prohibited data records that should not be edited by the web service.

### Claim 13 (depends on 1)

The method according to claim 1, wherein in the step transferring of the intended data set only the difference of the intended state to the temporally preceding intended state of the data set is transferred from the primary computer system to the secondary computer system.

### Claim 14 (depends on 1)

The method according to claim 1, wherein a reverse proxy is used on the one or more secondary computer systems to advantageously protect the web service from (D)DoS attacks.

### Claim 15 (depends on 1)

The method according to claim 1, wherein several secondary computer systems are operated in parallel in order to advantageously enable load balancing, in particular of the web application.

### Claim 16 (depends on 1)

The method according to claim 1, wherein upon violation of the integrity of a datum, the entire secondary computer system on which the integrity has been damaged is isolated.

### Claim 17 (depends on 1)

The method according to claim 1, wherein the isolated secondary computer system is not terminated but continues to operate in isolation for the purpose of analyzing malware.

### Claim 18 (depends on 1)

The method according to claim 1, wherein after isolating the secondary computer system whose integrity has been damaged, another secondary computer system is started as a replacement system.

### Claim 19 (depends on 1)

The method according to claim 1, wherein, in addition to load balancing, protection against (D) DoS is implemented.

### Claim 20 (depends on 1)

The method according to claim 1, wherein after manipulation of the data of the intended data set has been performed, the manipulated data is analyzed by manual and automated data processing methods.

### Claim 21 (depends on 1)

The method according to claim 1, wherein the method is executed through a computer program product, and wherein data defined by a user is registered for checking for manipulations, or data defined by a user is excluded from checking for manipulations.

### Claim 22 (depends on 2)

The method according to claim 2, wherein the method is executed through a computer program product, and wherein the contacting the deposited server (cockpit server) is made at regular or irregular intervals.
