Data protection and privacy regulations based on blockchain

Patent metadata

Field	Value
Publication number	US-11277411-B2
Application number	US-201816218935-A
Country	US
Kind code	B2
Filing date	Dec 13, 2018
Priority date	Dec 13, 2018
Publication date	Mar 15, 2022
Grant date	Mar 15, 2022

Abstract

Described herein includes a data controller that secures personal data and efficiency and reliably records data access events using blockchain. The system may include a data controller for: receiving a request to access data stored in a database on the data controller, the request including a web token; verifying the web token of the request; providing access to the data stored in the database; generating a data access event indicating that the data stored in the database has been accessed; and recording the data access event on a blockchain platform in accordance with blockchain.

First claim

What is claimed is:

1. A system, comprising:
at least one data processor; and
at least one memory storing instructions which, when executed by the at least one data processor, cause operations comprising:
receiving, by a data controller and via a frontend interface associated with an application server, a request to access data stored in a database on the data controller, the request including a web token;
verifying, by the data controller, the web token of the request;
providing, by the data controller and via the frontend interface, access to the data stored in the database;
generating, by the data controller, a data access event indicating that the data stored in the database has been accessed;
recording, by the data controller, the data access event on a blockchain platform in accordance with blockchain, wherein the blockchain platform is in remote communication with the data controller;
receiving, by the data controller, a reporting request to generate a data access event report, the data access event report comprising a log of the data access event stored on the blockchain platform; and
generating, by the data controller in response to the reporting request, the data access event report.

2. The system of claim 1 , wherein the data access event indicates that the data has been one or more of read, modified, written, and deleted.

3. The system of claim 1 , wherein the generating comprises:
retrieving, by the data controller, the data access event from the blockchain platform; and
retrieving, by the data controller, the data from the database that corresponds to the retrieved data access event.

4. The system of claim 3 , wherein the data stored in the database on the data controller includes a data object comprising an identifier, wherein the blockchain of the data access event includes the identifier, and wherein the identifier is configured to link the data object to the corresponding data access event.

5. The system of claim 1 , wherein the application server includes an application key and wherein the web token is configured to be generated by the data controller after verifying that the application key matches a stored application key that is stored on the data controller.

6. A computer-implemented method, comprising:
receiving, by a data controller and via a frontend interface associated with an application server, a request to access data stored in a database on the data controller, the request including a web token;
verifying, by the data controller, the web token of the request;
providing, by the data controller and via the frontend interface, access to the data stored in the database;
generating, by the data controller, a data access event indicating that the data stored in the database has been accessed;
recording, by the data controller, the data access event on a blockchain platform in accordance with blockchain, wherein the blockchain platform is in remote communication with the data controller;
receiving, by the data controller, a reporting request to generate a data access event report, the data access event report comprising a log of the data access event stored on the blockchain platform; and
generating, by the data controller in response to the reporting request, the data access event report.

7. The method of claim 6 , wherein the data access event indicates that the data has been one or more of read, modified, written, and deleted.

8. The method of claim 6 , wherein the generating comprises:
retrieving, by the data controller, the data access event from the blockchain platform; and
retrieving, by the data controller, the data from the database that corresponds to the retrieved data access event.

9. The method of claim 8 , wherein the data stored in the database on the data controller includes a data object comprising an identifier, wherein the in accordance with blockchain of the data access event includes the identifier, and wherein the identifier is configured to link the data object to the corresponding data access event.

10. The method of claim 6 , wherein the application server includes an application key and wherein the web token is configured to be generated by the data controller after verifying that the application key matches a stored application key that is stored on the data controller.

11. A non-transitory computer-readable medium storing instructions, which when executed by at least one data processor, result in operations comprising:
receiving, by a data controller and via a frontend interface associated with an application server, a request to access data stored in a database on the data controller, the request including a web token;
verifying, by the data controller, the web token of the request;
providing, by the data controller and via the frontend interface, access to the data stored in the database;
generating, by the data controller, a data access event indicating that the data stored in the database has been accessed;
recording, by the data controller, the data access event on a blockchain platform in accordance with blockchain, wherein the blockchain platform is in remote communication with the data controller;
receiving, by the data controller, a reporting request to generate a data access event report, the data access event report comprising a log of the data access event stored on the blockchain platform; and
generating, by the data controller in response to the reporting request, the data access event report.

12. The non-transitory computer-readable medium of claim 11 , wherein the data access event indicates that the data has been one or more of read, modified, written, and deleted.

13. The non-transitory computer-readable medium of claim 11 , wherein the generating comprises:
retrieving, by the data controller, the data access event from the blockchain platform; and
retrieving, by the data controller, the data from the database that corresponds to the retrieved data access event.

14. The non-transitory computer-readable medium of claim 13 , wherein the data stored in the database on the data controller includes a data object comprising an identifier, wherein the blockchain of the data access event includes the identifier, and wherein the identifier is configured to link the data object to the corresponding data access event.

15. The non-transitory computer-readable medium of claim 11 , wherein the application server includes an application key and wherein the web token is configured to be generated by the data controller after verifying that the application key matches a stored application key that is stored on the data controller.

Assignees

• Sap Se

Inventors

• Sun Xun
• Xue Jianmin

Classifications

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• H04L9/3213

  using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807) · CPC title

• H04L9/3239 Primary

  involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD · CPC title

• H04L63/0807

  using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213) · CPC title

• G06F21/6245

  Protecting personal data, e.g. for financial or medical purposes · CPC title