Table-connected tokenization

• US 10,560,451 B2
• Filed: 01/05/2019
• Issued: 02/11/2020
• Est. Priority Date: 09/30/2013
• Status: Active Grant

• Current Assignee: Protegrity USA, Inc. (Xcelera Inc.)
• Original Assignee: Protegrity Corporation
• Inventors: Mattsson, Ulf, Rozenberg, Yigal, Levy, Vichai
• Primary Examiner(s): Feild, Lynn D
• Assistant Examiner(s): Savenkov, Vadim
• Application Number:
  US16/240,734
• Publication Number:
  US 20190141025A1
• Time in Patent Office: 402 Days
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/84 Mapping; Conversion
• CPC Class Codes: G06F 21/6254 by anonymising data, e.g. decorrelating personal data from the owner's identification
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety
• 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/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 9/06 the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators

Abstract

A tokenization system tokenizes sensitive data to prevent unauthorized entities from accessing the sensitive data. The tokenization system accesses sensitive data, and retrieves an initialization vector (IV) from an IV table using a first portion of the sensitive data. A second portion of the sensitive data is modified using the accessed initialization vector. A token table is selected from a set of token tables using a third portion of the sensitive data. The modified second portion of data is used to query the selected token table, and a token associated with the value of the modified second portion of data is accessed. The second portion of the sensitive data is replaced with the accessed token to form tokenized data.

Claims

1. A method for improving the security of data in a tokenization environment, comprising:

receiving data to be tokenized, the received data comprising a first portion of received data and a second portion of received data different from the first portion of the received data;

accessing an initialization vector table, a first token table from a first server, and a second token table from a second server;

querying the initialization vector table with a value of the first portion of the received data to identify a first initialization vector and a second initialization vector; and

after accessing the first token table and the second token table and after querying the initialization vector table, transforming the received data to produce tokenized data by;

modifying, by a hardware processor, the second portion of the received data using the first initialization vector to produce a first modified portion of the received data;

replacing, by the hardware processor, the first modified portion of the received data with a first token mapped by the first token table to a value of the first modified portion of the received data to produce a first tokenized portion of the received data;

modifying, by the hardware processor, the first tokenized portion of the received data using the second initialization vector to produce a second modified portion of the received data; and

replacing, by the hardware processor, the second modified portion of the received data with a second token mapped by the second token table to a value of the second modified portion of the received data to produce a second tokenized portion of the received data.

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

a password, an account number, a social security number, a driver'"'"'s license number, information associated with a transaction, or date information.

3. The method of claim 1, wherein the initialization vector is received from an initialization vector table server different from the first server and the second server.

4. The method of claim 1, wherein modifying the second portion of the received data comprises adding the value of the second portion of the received data to a value of the first initialization vector.

5. The method of claim 1, wherein the first server is configured to select the first token table from a first set of token tables and the second server is configured to select the second token table form a second set of token tables, and wherein the first token table and the second token table are selected based on one of the received data, an identity of an entity associated with the received data, and a time associated with the received data.

6. The method of claim 1, wherein the first portion and the second portion of the received data do not overlap.

7. The method of claim 1, wherein the first portion and the second portion of the received data overlap at least in part.

8. A tokenization system for improving the security of data in a tokenization environment, comprising:

a non-transitory computer-readable storage medium storing executable instructions that, when executed by a processor, perform steps comprising;

receiving data to be tokenized, the received data comprising a first portion of received data and a second portion of received data different from the first portion of the received data;

accessing an initialization vector table, a first token table from a first server, and a second token table from a second server;

querying the initialization vector table with a value of the first portion of the received data to identify a first initialization vector and a second initialization vector; and

after accessing the first token table and the second token table and after querying the initialization vector table, transforming the received data to produce tokenized data by;

modifying, by a hardware processor, the second portion of the received data using the first initialization vector to produce a first modified portion of the received data;

replacing, by the hardware processor, the first modified portion of the received data with a first token mapped by the first token table to a value of the first modified portion of the received data to produce a first tokenized portion of the received data;

modifying, by the hardware processor, the first tokenized portion of the received data using the second initialization vector to produce a second modified portion of the received data; and

replacing, by the hardware processor, the second modified portion of the received data with a second token mapped by the second token table to a value of the second modified portion of the received data to produce a second tokenized portion of the received data; and

a hardware processor configured to execute the instructions.

9. The tokenization system of claim 8, wherein the received data is one of:

a password, an account number, a social security number, a driver'"'"'s license number, information associated with a transaction, or date information.

10. The tokenization system of claim 8, wherein the initialization vector is received from an initialization vector table server different from the first server and the second server.

11. The tokenization system of claim 8, wherein modifying the second portion of the received data comprises adding the value of the second portion of the received data to a value of the first initialization vector.

12. The tokenization system of claim 8, wherein the first server is configured to select the first token table from a first set of token tables and the second server is configured to select the second token table form a second set of token tables, and wherein the first token table and the second token table are selected based on one of the received data, an identity of an entity associated with the received data, and a time associated with the received data.

13. The tokenization system of claim 8, wherein the first portion and the second portion of the received data do not overlap.

14. The tokenization system of claim 8, wherein the first portion and the second portion of the received data overlap at least in part.

15. A non-transitory computer-readable storage medium storing executable computer instructions that when executed by a hardware processor perform steps for improving the security of data in a tokenization environment, comprising:

receiving data to be tokenized, the received data comprising a first portion of received data and a second portion of received data different from the first portion of the received data;

accessing an initialization vector table, a first token table from a first server, and a second token table from a second server;

querying the initialization vector table with a value of the first portion of the received data to identify a first initialization vector and a second initialization vector; and

after accessing the first token table and the second token table and after querying the initialization vector table, transforming the received data to produce tokenized data by;

modifying, by a hardware processor, the second portion of the received data using the first initialization vector to produce a first modified portion of the received data;

replacing, by the hardware processor, the first modified portion of the received data with a first token mapped by the first token table to a value of the first modified portion of the received data to produce a first tokenized portion of the received data;

modifying, by the hardware processor, the first tokenized portion of the received data using the second initialization vector to produce a second modified portion of the received data; and

replacing, by the hardware processor, the second modified portion of the received data with a second token mapped by the second token table to a value of the second modified portion of the received data to produce a second tokenized portion of the received data.

16. The non-transitory computer-readable storage medium of claim 15, wherein the received data is one of:

a password, an account number, a social security number, a driver'"'"'s license number, information associated with a transaction, or date information.

17. The non-transitory computer-readable storage medium of claim 15, wherein the initialization vector is received from an initialization vector table server different from the first server and the second server.

18. The non-transitory computer-readable storage medium of claim 15, wherein modifying the second portion of the received data comprises adding the value of the second portion of the received data to a value of the first initialization vector.

19. The non-transitory computer-readable storage medium of claim 15, wherein the first server is configured to select the first token table from a first set of token tables and the second server is configured to select the second token table form a second set of token tables, and wherein the first token table and the second token table are selected based on one of the received data, an identity of an entity associated with the received data, and a time associated with the received data.

20. The non-transitory computer-readable storage medium of claim 15, wherein the first portion and the second portion of the received data do not overlap.