Collision avoidance in a distributed tokenization environment

• US 9,699,149 B2
• Filed: 03/25/2016
• Issued: 07/04/2017
• Est. Priority Date: 09/30/2013
• Status: Active Grant

• Current Assignee: Protegrity USA, Inc. (Xcelera Inc.)
• Original Assignee: Protegrity USA, Inc. (Xcelera Inc.)
• Inventors: Mattsson, Ulf, Ferentz, Zvika
• Primary Examiner(s): Smithers, Matthew
• Assistant Examiner(s): Li, Mary
• Application Number:
  US15/080,589
• Publication Number:
  US 20160212105A1
• Time in Patent Office: 466 Days
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04W 12/02 Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]

Abstract

A client receives sensitive data to be tokenized. The client queries a token table with a portion of the sensitive data to determine if the token table includes a token mapped to the value of the portion of the sensitive data. If the mapping table does not include a token mapped to the value of the portion of the sensitive data, a candidate token is generated. The client queries a central token management system to determine if the candidate token collides with a token generated by or stored at another client. In some embodiments, the candidate token includes a value from a unique set of values assigned by the central token management system to the client, guaranteeing that the candidate token does not cause a collision. The client then tokenizes the sensitive data with the candidate token and stores the candidate token in the token table.

Claims

1. A computer-implemented method for tokenizing data comprising:

receiving, by each of a plurality of clients each associated with a corresponding numeric identifier and communicatively coupled to a central token management system, a unique set of values from the central token management system associated with the corresponding numeric identifier, wherein each unique set of values is generated by the central token management system for the plurality of clients to avoid collisions between the plurality of clients;

accessing, by a client, data to be tokenized;

selecting, by the client, a portion of the accessed data;

determining, by the client, if a token table associated with the client includes a token value mapped to a value of the selected portion of the data;

responsive to a determination that the token table does not include a token value mapped to the value of the selected portion of the data, generating, by the client, a token value unique to the client by selecting a value from the received unique set of values;

tokenizing the accessed data by replacing the selected portion of the data with the generated token value; and

updating the token table to include the generated token value mapped to the value of the selected portion of the data.

2. The method of claim 1, further comprising:

responsive to a determination that the token table does include a token value mapped to the value of the selected portion of the data, tokenizing the accessed data using the token value mapped to the value of the selected portion of the data.

3. The method of claim 1, further comprising:

responsive to a determination that the token table associated with the client includes a token value for each value in the unique set of values corresponding to the client, requesting an additional unique set of values from the central token management system;

wherein the generated token value includes a value from the additional unique set of values.

4. The method of claim 1, wherein the data is one of:

a credit card number, a bank account number, a social security number, a driver'"'"'s license number, and a passport number.

5. The method of claim 1, wherein each unique set of values comprises a numeric range of values.

6. The method of claim 1, wherein each client periodically receives a new unique set of values from the central token management system.

7. A non-transitory computer-readable medium storing executable computer instructions for tokenizing data, the instructions, when executed by a hardware processor, configured to perform steps comprising:

receiving, by each of a plurality of clients each associated with a corresponding numeric identifier and communicatively coupled to a central token management system, a unique set of values from the central token management system associated with the corresponding numeric identifier, wherein each unique set of values is generated by the central token management system for the plurality of clients to avoid collisions between the plurality of clients;

accessing, by a client, data to be tokenized;

selecting, by the client, a portion of the accessed data;

determining, by the client, if a token table associated with the client includes a token value mapped to a value of the selected portion of the data;

responsive to a determination that the token table does not include a token value mapped to the value of the selected portion of the data, generating, by the client, a token value unique to the client by selecting a value from the received unique set of values;

tokenizing the accessed data by replacing the selected portion of the data with the generated token value; and

updating the token table to include the generated token value mapped to the value of the selected portion of the data.

8. The computer-readable medium of claim 7, wherein the instructions, when executed by the hardware processor, are configured to perform further steps comprising:

responsive to a determination that the token table does include a token value mapped to the value of the selected portion of the data, tokenizing the accessed data using the token value mapped to the value of the selected portion of the data.

9. The computer-readable medium of claim 7, wherein the instructions, when executed by the hardware processor, are configured to perform further steps comprising:

responsive to a determination that the token table associated with the client includes a token value for each value in the unique set of values corresponding to the client, requesting an additional unique set of values from the central token management system;

wherein the generated token value includes a value from the additional unique set of values.

10. The computer-readable medium of claim 7, wherein the data is one of:

a credit card number, a bank account number, a social security number, a driver'"'"'s license number, and a passport number.

11. The computer-readable medium of claim 7, wherein each unique set of values comprises a numeric range of values.

12. The computer-readable medium of claim 7, wherein each client periodically receives a new unique set of values from the central token management system.

13. A system for tokenizing data comprising:

a central token management system configured to generate a unique set of values for each of a plurality of clients to avoid collisions between the plurality of clients; and

a plurality of client devices, each client device communicatively coupled to the central token management system, each client device corresponding to a numeric identifier and comprising a hardware processor and a non-transitory computer readable medium comprising instructions, the instructions when executed by the processor of the client device, configured to cause the client device to;

receive a unique set of values from the central token management system associated with the corresponding numeric identifier;

access data to be tokenized;

select a portion of the accessed data;

determine if a token table associated with the client includes a token value mapped to a value of the selected portion of the data;

responsive to a determination that the token table does not include a token value mapped to the value of the selected portion of the data, generate a token value unique to the client by selecting a value from the received unique set of values;

tokenize the accessed data by replacing the selected portion of the data with the generated token value; and

update the token table to include the generated token value mapped to the value of the selected portion of the data.

14. The system of claim 13, wherein the instructions, when executed by the processor of the client device, are further configured to cause the client device to:

responsive to a determination that the token table does include a token value mapped to the value of the selected portion of the data, tokenize the accessed data using the token value mapped to the value of the selected portion of the data.

15. The system of claim 13, wherein the instructions, when executed by the processor of the client device, are further configured to cause the client device to:

responsive to a determination that the token table associated with the client includes a token value for each value in the unique set of values corresponding to the client, request an additional unique set of values from the central token management system;

wherein the generated token value includes a value from the additional unique set of values.

16. The system of claim 13, wherein the data is one of:

a credit card number, a bank account number, a social security number, a driver'"'"'s license number, and a passport number.

17. The system of claim 13, wherein each unique set of values comprises a numeric range of values.

18. The system of claim 13, wherein each client periodically receives a new unique set of values from the central token management system.