IP Library Granted Patent US 9,684,800
Granted Patent B2
US 9,684,800 · App. 15/387,639 · Granted Jun 20, 2017

Tokenization in a centralized tokenization environment

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 9,684,800
App. No.
15/387,639
Granted
Jun 20, 2017
Kind
B2
Abstract

Data can be protected in a centralized tokenization environment. A request to tokenize sensitive data is received by an endpoint. A token for use in tokenizing the sensitive data is identified. A token certificate store is queried for a token certificate associated with the identified token. The token certificate can include a token status and use rules describing a permitted use of the token. Responsive to the token certificate store storing the queried token certificate, the endpoint tokenizes the sensitive data using the identified token if the token status indicates the token is available, and subject to the use rules included in the token certificate being satisfied. The token certificate is updated based on the tokenization of the sensitive data with the identified token and stored at the token certificate store.

Claims (62)

1. A method for detokenizing data, comprising:

receiving a request to detokenize tokenized data;

identifying a token used in tokenizing the tokenized data, the identified token comprising a token value mapped to a value of a portion of data tokenized to produce the tokenized data before a request to tokenize the data is received;

querying a token certificate store for a token certificate associated with the identified token, the token certificate comprising a status of the identified token; and

responsive to a determination that the token certificate store contains the token certificate associated with the identified token:

responsive to the token certificate indicating that the identified token is available for use, detokenizing the tokenized data using the identified token to produce detokenized data; and

updating the token certificate based on the detokenization of the tokenized data for storage in the token certificate store.

2. The method of claim 1 , wherein detokenizing the tokenized data comprises:

accessing a status of the identified token from the token certificate associated with the identified token; and

detokenizing the data with the identified token responsive to the accessed status indicating that the identified token is available.

3. The method of claim 1 , wherein the token certificate associated with the identified token further comprises a use rule describing a permitted use of the identified token based on characteristics of the tokenization request.

4. The method of claim 3 , wherein detokenizing the data with the identified token further comprises:

detokenizing the tokenized data with the identified token subject to characteristics of the tokenization request satisfying the use rule.

5. The method of claim 1 , further comprising:

responsive to a determination that the token certificate store does not contain the token certificate associated with the identified token:

detokenizing the tokenized data using the identified token to produce detokenized data;

generating the token certificate associated with the identified token, the generated token certificate describing the detokenization of the tokenize data; and

storing the generated token certificate in the token certificate store.

6. The method of claim 1 , wherein the detokenization request is received at an endpoint, and further comprising:

transmitting the detokenized data to a second endpoint for storage.

7. A non-transitory computer-readable storage medium storing executable computer instructions that, when executed by a hardware processor, perform steps comprising:

receiving a request to detokenize tokenized data;

identifying a token used in tokenizing the tokenized data, the identified token comprising a token value mapped to a value of a portion of data tokenized to produce the tokenized data before a request to tokenize the data is received;

querying a token certificate store for a token certificate associated with the identified token, the token certificate comprising a status of the identified token; and

responsive to a determination that the token certificate store contains the token certificate associated with the identified token:

responsive to the token certificate indicating that the identified token is available for use, detokenizing the tokenized data using the identified token to produce detokenized data; and

updating the token certificate based on the detokenization of the tokenized data for storage in the token certificate store.

8. The non-transitory computer-readable storage medium of claim 7 , wherein detokenizing the tokenized data comprises:

accessing a status of the identified token from the token certificate associated with the identified token; and

detokenizing the data with the identified token responsive to the accessed status indicating that the identified token is available.

9. The non-transitory computer-readable storage medium of claim 7 , wherein the token certificate associated with the identified token further comprises a use rule describing a permitted use of the identified token based on characteristics of the tokenization request.

10. The non-transitory computer-readable storage medium of claim 9 , wherein detokenizing the data with the identified token further comprises:

detokenizing the tokenized data with the identified token subject to characteristics of the tokenization request satisfying the use rule.

11. The non-transitory computer-readable storage medium of claim 7 , wherein the executable computer instructions, when executed by the hardware processor, perform further steps comprising:

responsive to a determination that the token certificate store does not contain the token certificate associated with the identified token:

detokenizing the tokenized data using the identified token to produce detokenized data;

generating the token certificate associated with the identified token, the generated token certificate describing the detokenization of the tokenize data; and

storing the generated token certificate in the token certificate store.

12. The non-transitory computer-readable storage medium of claim 7 , wherein the detokenization request is received at an endpoint, and wherein the executable computer instructions, when executed by the hardware processor, perform further steps comprising:

transmitting the detokenized data to a second endpoint for storage.

13. A method for detokenizing data, comprising:

receiving a request to detokenize tokenized data;

identifying a token used in tokenizing the tokenized data, the identified token comprising a token value mapped to a value of a portion of data tokenized to produce the tokenized data before a request to tokenize the data is received;

querying a token certificate store for a token certificate associated with the identified token, the token certificate comprising a status of the identified token; and

responsive to a determination that the token certificate store contains the token certificate associated with the identified token:

responsive to the token certificate indicating that the identified token is not available for use, denying the request to detokenize the tokenized data using the identified token; and

updating the token certificate based on the denial of the request to detokenize the tokenized data for storage in the token certificate store.

14. The method of claim 13 , wherein the identified token is not available for use in response to the identified token being checked out.

15. The method of claim 13 , wherein the identified token is not available for use in response to the identified token being revoked.

16. The method of claim 13 , wherein the detokenization request is received at an endpoint, and further comprising:

transmitting a notification of the denial of the request to detokenize the tokenized data to the endpoint.

17. A non-transitory computer-readable storage medium storing executable computer instructions that, when executed by a hardware processor, perform steps comprising:

receiving a request to detokenize tokenized data;

identifying a token used in tokenizing the tokenized data, the identified token comprising a token value mapped to a value of a portion of data tokenized to produce the tokenized data before a request to tokenize the data is received;

querying a token certificate store for a token certificate associated with the identified token, the token certificate comprising a status of the identified token; and

responsive to a determination that the token certificate store contains the token certificate associated with the identified token:

responsive to the token certificate indicating that the identified token is not available for use, denying the request to detokenize the tokenized data using the identified token; and

updating the token certificate based on the denial of the request to detokenize the tokenized data for storage in the token certificate store.

18. The method of claim 17 , wherein the identified token is not available for use in response to the identified token being checked out.

19. The method of claim 17 , wherein the identified token is not available for use in response to the identified token being revoked.

20. The method of claim 17 , wherein the detokenization request is received at an endpoint, and wherein the executable computer instructions, when executed by the hardware processor, perform further steps comprising:

transmitting a notification of the denial of the request to detokenize the tokenized data to the endpoint.

Assignments (3)
SECURITY INTEREST Recorded Aug 2, 2024
From: PROTEGRITY USA, INC.; PROTEGRITY LIMITED HOLDING, LLC; PROTEGRITY US HOLDING, LLC; PROTEGRITY CORPORATION; KAVADO, LLC
To: CANADIAN IMPERIAL BANK OF COMMERCE
Reel/Frame 068326/0020 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 29, 2024
From: PROTEGRITY CORPORATION
To: PROTEGRITY US HOLDING, LLC
Reel/Frame 067566/0462 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 22, 2016
From: MATTSSON, ULF; ROZENBERG, YIGAL
To: PROTEGRITY CORPORATION
Reel/Frame 040745/0035 →