Data management platform

Patent metadata

Field	Value
Publication number	US-12277243-B2
Application number	US-202318134883-A
Country	US
Kind code	B2
Filing date	Apr 14, 2023
Priority date	Apr 14, 2023
Publication date	Apr 15, 2025
Grant date	Apr 15, 2025

Abstract

A network system to allow global usage of data while allowing regional jurisdictions control over sensitive data. Different jurisdictions may declare different types of data as sensitive data that is not to be discoverable by a third party. The system allows the data to be shared across jurisdiction boundaries with complete auditability, traceability, and compliance. The system allows a first jurisdiction computing device to control the usage of the data that is stored outside of the jurisdiction. The technology allows the first jurisdiction to propagate rules, tokenization protocols, and updates to the system to manage the sensitive data. The system detokenizes the data when the data is to be used for an approved purpose by an approved party. If the original jurisdiction has a change in permissions for sensitive data, the jurisdiction can propagate a tokenization to all data stored in the data management system outside of the jurisdiction.

First claim

What is claimed is:

1. A data management system, comprising:
a first processor communicatively coupled to a first storage device operating in a first jurisdiction, wherein the first processor executes application code instructions that are stored in the first storage device to:
transmit data from the first processor in the first jurisdiction to a second processor that is operating in a second jurisdiction, the data comprising data fields with at least one data field classified as a sensitive data field having sensitive data, the sensitive data field being tokenized by the first processor according to a first tokenization protocol before transfer;
transmit detokenization controls to the second processor, the detokenization controls comprising conditions under which the second processor may detokenize tokenized data;
cause storage of the tokenized data on a second storage device in the second jurisdiction, wherein the second storage device is associated with the second processor, and wherein the second processor is unable to access data without satisfying the conditions;
receive a request to revoke access to the sensitive data field accessible in the second jurisdiction;
responsive to the request to revoke access to the sensitive data field accessible in the second jurisdiction, causing retokenization of the data at the first processor according to a second tokenization protocol, wherein the retokenization generates retokenized data and renders the retokenized data inaccessible to the second processor; and
propagate the retokenized data to the second storage device in the second jurisdiction.

2. The data management system of claim 1 , wherein propagating the retokenized data comprises:
accessing the sensitive data in the second storage device in the second jurisdiction; and
restoring the retokenized data on the second storage device.

3. The data management system of claim 1 , further comprising application code instructions to:
receive a second request for access by a third party device to the sensitive data; and
responsive to determining to deny access, transmitting a notification to the third party device that the second request is denied, wherein the notification further includes an explanation for denial or instructions to appeal the denial.

4. The data management system of claim 1 , further comprising:
identifying the sensitive data by filtering the data for content, identifiers, metadata, or any other data characteristic that identifies the data as sensitive; and
labelling the data as the sensitive data.

5. The data management system of claim 1 , wherein the second tokenization protocol comprises a mathematically reversible cryptographic function with a key for each instance of data.

6. The data management system of claim 1 , wherein the detokenization controls comprise rules based on location of a third party.

7. The data management system of claim 1 , wherein the detokenization controls comprise rules based on a legal agreement between a third party and the data management system.

8. The data management system of claim 1 , wherein satisfaction of the conditions and detokenization of the data occurs in real time.

9. The data management system of claim 1 , wherein detokenization of the data is only permitted for a third party within a particular geographic location or jurisdiction.

10. A method to provide data management security across jurisdictional boundaries using tokenization of sensitive data, comprising:
transmitting to a second computing device of a second data management system in a second jurisdiction, data comprising data fields with one or more data fields classified as a sensitive data fields, the sensitive data fields being tokenized according to a first tokenization protocol by a first computing system of a first data management system in a first jurisdiction before transfer;
transmit detokenization controls to the second computing device from a first computing device, the detokenization controls comprising conditions under which the second computing device may detokenize tokenized data;
cause storage, by the second computing device, of the data on a storage device in the second jurisdiction, wherein the second computing device is unable to access data without satisfying the conditions;
receive a request to revoke access to the sensitive data accessible in the second jurisdiction;
responsive to the request to revoke access to the sensitive data accessible in the second jurisdiction, causing retokenization of the data at the first computing device according to a second tokenization protocol, wherein the retokenization generates retokenized data and renders the data inaccessible by the second computing device; and
propagate the retokenized data to the storage device in the second jurisdiction.

11. The method of claim 10 , wherein the detokenization controls comprise rules based on a legal agreement between a third party and the first data management system.

12. The method of claim 10 , further comprising:
receiving a second request for access of the sensitive data by a third party device; and
responsive to determining to deny access, transmitting a notification to the third party device that the second request is denied, wherein the notification further includes an explanation for denial or instructions to appeal the denial.

13. The method of claim 10 , further comprising:
identifying the sensitive data by filtering the data for content, identifiers, metadata, or any other data characteristic that identifies the data as sensitive; and
labelling the data as sensitive.

14. The method of claim 10 , wherein the second tokenization protocol comprises a mathematically reversible cryptographic function with a key for each instance of data.

15. One or more non-transitory computer-readable media having computer-readable program instructions embodied thereon, the computer-readable program instructions causing one or more processors to:
transmit data from a first computing system in a first jurisdiction to a second computing system and second storage device operating in a second jurisdiction, the data comprising data fields with at least one data field classified as sensitive data, the sensitive data being tokenized according to a first tokenization protocol by the first computing system in the first jurisdiction before transfer;
transmit detokenization controls to the second computing system, the detokenization controls comprising conditions under which the second computing system detokenizes tokenized data;
cause storage of the data on the second storage device in the second jurisdiction, wherein the second computing system is unable to access data without satisfying the conditions;
receive a request to revoke access to the sensitive data accessible in the second jurisdiction;
responsive to the request to revoke access to the sensitive data accessible in the second jurisdiction, causing retokenization of the data at the first computing system according to a second tokenization protocol, wherein the retokenization renders the data inaccessible by the second computing system; and
propagate retokenized data to the second storage device in the second jurisdiction.

16. The one or more non-transitory computer-readable media of claim 15 , wherein the conditions are based on location.

17. The one or more non-transitory computer-readable media of claim 15 , wherein the conditions are based on a legal agreement between a third party and a data management system.

18. The one or more non-transitory computer-readable media of

Assignees

• Citibank Na

Inventors

• Trotta Walter
• Kumar Vaibhav
• Kass Samuel J
• Shanmugasundaram Sasisekar

Classifications

• G06F21/6254

  by anonymising data, e.g. decorrelating personal data from the owner's identification · CPC title

• G06F21/6245

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

• G06F21/6218 Primary

  to a system of files or objects, e.g. local or distributed file system or database · CPC title