Blockchain technology for data integrity regulation and proof of existence in data protection systems
One example method includes creating a backup of data, creating metadata associated with the backup, hashing the backup to create a backup hash, obtaining a key from a blockchain, generating an aggregate hash of a combination that includes the key and the backup hash, and transmitting the aggregate hash to a blockchain network. Because the aggregate hash is not modifiable when stored in a blockchain, an immutable record exists that establishes when a particular backup was created.
1. A system, comprising:
one or more hardware processors; and
a non-transitory storage medium having stored therein instructions which are executable by the one or more hardware processors to perform operations comprising:
creating a backup of data;
creating metadata associated with the backup;
hashing the backup to create a backup hash;
obtaining a key from a blockchain of a blockchain network, wherein the key is associated with a creation time of the backup;
generating an aggregate hash of a combination comprising: the key; and, the backup hash, wherein information in the aggregate hash establishes that particular data did, or did not, exist in the backup as of a particular point in time; and
transmitting, by way of a blockchain plugin to a backup server, the aggregate hash to a blockchain network.
2. The system as recited in claim 1 , wherein the aggregate hash forms the basis for a block in the blockchain.
3. The system as recited in claim 1 , wherein the operations further comprise:
restoring the backup;
hashing the restored backup to create a second backup hash;
comparing the second backup hash with the backup hash to determine whether data of the restored backup matches the data in the backup;
restoring a second backup upon which a third backup hash is based;
hashing the restored second backup to create a fourth backup hash;
comparing the third backup hash and the fourth backup hash to determine whether data of the restored second backup matches data in the second backup; and
when data of the restored backup matches the data in the backup, and data in the restored second backup matches data in the second backup, comparing the data of the backup with the data of the second backup to determine whether or not data that is present in the backup is present in the second backup.
4. The system as recited in claim 3 , wherein comparison of the data of the backup with the data of the second backup enables a determination as to whether or not a particular data management transaction involving data of the backup took place.
5. The system as recited in claim 3 , wherein the comparison of the data of the backup with the data of the second backup enables a determination as to what particular data of the backup was deleted, and when that particular data was deleted.
6. The system as recited in claim 1 , wherein the key is a last observed key in the blockchain.
7. The system as recited in claim 1 , wherein the key is one of a plurality of periodically generated keys.
8. The system as recited in claim 1 , wherein an entity that performs part of the method comprises a node of the blockchain network.
9. The system as recited in claim 1 , wherein the combination from which the aggregate hash is generated further comprises the metadata associated with the backup.
10. The system as recited in claim 3 , wherein the operations recited in claim 3 are performed as a result of receipt of a request to demonstrate that the data in the backup did, or did not, exist as of a particular time.
11. The system as recited in claim 10 , further comprising responding to the request by providing information establishing either that the data had been deleted as of the particular point in time, or that the particular data had not been deleted as of the particular point in time.
12. A system, comprising:
one or more hardware processors; and
a non-transitory storage medium having stored therein instructions which are executable by the one or more hardware processors to perform operations comprising:
creating a backup of data;
creating metadata associated with the backup;
hashing the backup to create a backup hash;
obtaining a key from a blockchain of a blockchain network, wherein the key is associated with a creation time of the backup;
generating an aggregate hash of a combination comprising: the key; and, the backup hash, wherein information in the aggregate hash establishes that particular data did, or did not, exist in the backup as of a particular point in time;
transmitting, by way of a blockchain plugin to a backup server, the aggregate hash to a blockchain network; and
performing an audit process in response to receipt of a request to demonstrate either existence, or non-existence, of the particular data as of the particular point in time.
13. The system as recited in claim 12 , wherein the aggregate hash forms the basis for a block in the blockchain.
14. The system as recited in claim 12 , wherein the key is a last observed key in the blockchain.
15. The system as recited in claim 12 , wherein the key is one of a plurality of periodically generated keys.
16. The system as recited in claim 12 , wherein an entity that performs part of the method comprises a node of the blockchain network.
17. The system as recited in claim 12 , wherein the combination from which the aggregate hash is generated further comprises the metadata associated with the backup.
18. The system as recited in claim 12 , wherein the backup is taken before the particular point in time, and the audit process comprises comparing data of the backup with data of a second backup taken at, or after, the particular point in time.
19. The system as recited in claim 12 , further comprising transmitting results of the audit process.
20. The system as recited in claim 12 , wherein the audit process comprises determining whether or not the particular data has been compromised.