IP Library › Granted Patent US 12,238,215
Granted Patent B2
US 12,238,215 · App. 18/076,793 · Granted Feb 25, 2025

Method and system for providing public cloud tokenization service for highly confidential data

Inventor: Prabhu Meena (Singapore, SG)
Assignee: JPMORGAN CHASE BANK, N.A.
H04L9/3213
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,238,215
App. No.
18/076,793
Granted
Feb 25, 2025
Kind
B2
Abstract

A method for using encryption and tokenization to protect confidential data that is stored in a public cloud database is provided. The method includes: receiving a first data set; tokenizing the first data set; obtaining a first token for at least one attribute of the first data set; encrypting an original value of the attribute and the first data set; storing each of the original value of the at least one attribute, the encrypted value of the at least one attribute, and the first token in a first memory; storing each of the first token and the encrypted first data set in a second memory; and storing the tokenized first data set in a third memory that is hosted on a public cloud server.

Claims (60)

1. A method for using encryption and tokenization to protect confidential data, the method being implemented by at least one processor, the method comprising:

receiving, by the at least one processor, a first data set;

tokenizing, by the at least one processor, the first data set;

obtaining, by the at least one processor, a first token for at least one attribute of the first data set;

encrypting, by the at least one processor, an original value of the at least one attribute and the first data set;

storing, by the at least one processor, each of the original value of the at least one attribute, the encrypted value of the at least one attribute, and the first token in a first memory;

storing, by the at least one processor, each of the first token and the encrypted first data set in a second memory; and

storing, by the at least one processor, the tokenized first data set in a third memory,

wherein the tokenizing comprises using an Amazon Web Services (AWS) Tokenization service; and wherein the first memory comprises an Elastic Cache of the AWS Tokenization service; and wherein the second memory comprises a Token Vault of the AWS Tokenization service.

2. The method of claim 1 , wherein the third memory is hosted on a public cloud server.

3. The method of claim 2 , further comprising:

receiving, from a user, a request for accessing data from the first data set;

retrieving the tokenized first data set from the third memory;

detokenizing the first data set; and

transmitting, to the user, the requested data.

4. The method of claim 1 , wherein the obtaining of the first token comprises generating the first token by using a zero hash collision function.

5. The method of claim 1 , wherein the obtaining of the first token comprises retrieving the first token from the first memory.

6. The method of claim 1 , wherein when the first memory becomes invalidated, the method further comprises:

retrieving, from the second memory, the first token and the encrypted first data set;

decrypting the encrypted first data set; and

using the decrypted first data set to recover the original value of the at least one attribute.

7. The method of claim 1 , wherein the third memory does not store any of the original value of the at least one attribute, and the third memory does not store an original value of any item included in the first data set.

8. The method of claim 1 , wherein the encrypting comprises fetching at least one encryption key from a secure encryption service and using the at least one encryption key to perform the encrypting.

9. A computing apparatus for using encryption and tokenization to protect confidential data, the computing apparatus comprising:

a processor;

a first memory; and

a communication interface coupled to each of the processor and the first memory,

wherein the processor is configured to:

receive, via the communication interface, a first data set;

tokenize the first data set by using an Amazon Web Services (AWS) Tokenization service;

obtain a first token for at least one attribute of the first data set;

encrypt an original value of the at least one attribute and the first data set;

store each of the original value of the at least one attribute, the encrypted value of the at least one attribute, and the first token in the first memory;

store each of the first token and the encrypted first data set in a second memory; and

store the tokenized first data set in a third memory,

wherein the first memory comprises an Elastic Cache of the AWS Tokenization service; and wherein the second memory comprises a Token Vault of the AWS Tokenization service.

10. The computing apparatus of claim 9 , wherein the third memory is hosted on a public cloud server.

11. The computing apparatus of claim 10 , wherein the processor is further configured to:

receive, from a user via the communication interface, a request for accessing data from the first data set;

retrieve the tokenized first data set from the third memory;

detokenize the first data set; and

transmit, to the user via the communication interface, the requested data.

12. The computing apparatus of claim 9 , wherein the processor is further configured to obtain the first token by using a zero hash collision function to generate the first token.

13. The computing apparatus of claim 9 , wherein the processor is further configured to obtain the first token by retrieving the first token from the first memory.

14. The computing apparatus of claim 9 , wherein when the first memory becomes invalidated, the processor is further configured to:

retrieve, from the second memory, the first token and the encrypted first data set;

decrypt the encrypted first data set; and

use the decrypted first data set to recover the original value of the at least one attribute.

15. The computing apparatus of claim 9 , wherein the third memory does not store any of the original value of the at least one attribute, and the third memory does not store an original value of any item included in the first data set.

16. The computing apparatus of claim 9 , wherein the processor is further configured to fetch at least one encryption key from a secure encryption service and use the at least one encryption key to perform the encryption.

17. A non-transitory computer readable storage medium storing instructions for using encryption and tokenization to protect confidential data, the storage medium comprising executable code which, when executed by a processor, causes the processor to:

receive a first data set;

tokenize the first data set by using an Amazon Web Services (AWS) Tokenization service;

obtain a first token for at least one attribute of the first data set;

encrypt an original value of the at least one attribute and the first data set;

store each of the original value of the at least one attribute, the encrypted value of the at least one attribute, and the first token in a first memory;

store each of the first token and the encrypted first data set in a second memory; and

store the tokenized first data set in a third memory,

wherein the first memory comprises an Elastic Cache of the AWS Tokenization service; and wherein the second memory comprises a Token Vault of the AWS Tokenization service.

18. The storage medium of claim 17 , wherein the third memory is hosted on a public cloud server.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 7, 2022
From: MEENA, PRABHU
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 062015/0188 →
Continuity (2)
Provisional Application 63266586 · Jan 10, 2022
Related Publication 20230224159A1 · Jul 13, 2023
References Cited (10)
US 20150143112A1 · Yavuz et al. · 2015 [cited by applicant]
US 20170201498A1 · Baig · 2017 [cited by examiner]
US 20180027006A1 · Zimmermann · 2018 [cited by examiner]
US 20200137097A1 · Zimmermann et al. · 2020 [cited by applicant]
US 20210234673A1 · Kurian · 2021 [cited by examiner]
US 20220035775A1 · Sriharsha · 2022 [cited by examiner]
US 20220247785A1 · Ly · 2022 [cited by examiner]
US 20220270129A1 · Dakic · 2022 [cited by examiner]
US 20220311597A1 · Goel · 2022 [cited by examiner]
International Search Report and Written Opinion in corresponding International Application No. PCT/US2022/052119, dated Mar. 7, 2023. [cited by applicant]