Table-connected tokenization

• US 9,906,523 B2
• Filed: 03/27/2017
• Issued: 02/27/2018
• 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, Rozenberg, Yigal, Levy, Vichai
• Primary Examiner(s): Revak, Christopher
• Assistant Examiner(s): Savenkov, Vadim
• Application Number:
  US15/470,351
• Publication Number:
  US 20170201511A1
• Time in Patent Office: 337 Days
• Field of Search: None
• 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, a second portion of received data, and a third portion of received data, the first portion, second portion, and third portion comprising different portions of the received data;

selecting, by a hardware processor, a token table from a set of token tables using a first portion of the received data, the selected token table mapping each of a plurality of input values to a different token value; and

after selecting the token table, transforming the received data to produce tokenized data by;

querying an initialization vector table with a value of the third portion of received data to obtain an initialization vector mapped to the value of the third portion of received data;

modifying, by the hardware processor, the second portion of the received data with the initialization vector;

querying, by the hardware processor, the token table with the modified second portion to identify a token value mapped to a value of the modified second portion; and

replacing, by the hardware processor, the second portion of the received data with the identified token value to produce the tokenized 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 second portion of the received data is modified at least in part by adding the value of the third portion of the received data to a value of the second portion of the received data.

4. The method of claim 1, wherein the set of token tables are stored on a plurality of servers.

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

6. The method of claim 1, wherein two or more of the first portion, the second portion, and the third portion of the received data overlap in part.

7. The method of claim 1, wherein the initialization vector table is received from an external entity.

8. The method of claim 1, wherein the initialization vector table is generated based on an identity of a user.

9. The method of claim 1, wherein the initialization vector table is generated based on a time or date of a requested tokenization operation.

10. 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, a second portion of received data, and a third portion of received data, the first portion, second portion, and third portion comprising different portions of the received data;

selecting a token table from a set of token tables using a first portion of the received data, the selected token table mapping each of a plurality of input values to a different token value; and

after selecting the token table, transforming the received data to produce tokenized data by;

querying an initialization vector table with a value of the third portion of received data to obtain an initialization vector mapped to the value of the third portion of received data;

modifying the second portion of the received data with the initialization vector;

querying the token table with the modified second portion to identify a token value mapped to a value of the modified second portion; and

replacing the second portion of the received data with the identified token value to produce the tokenized data; and

a hardware processor configured to execute the instructions.

11. The non-transitory computer-readable storage medium of claim 10, 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.

12. The non-transitory computer-readable storage medium of claim 10, wherein the second portion of the received data is modified at least in part by adding the value of the third portion of the received data to a value of the second portion of the received data.

13. The non-transitory computer-readable storage medium of claim 10, wherein the set of token tables are stored on a plurality of servers.

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

15. The non-transitory computer-readable storage medium of claim 10, wherein two or more of the first portion, the second portion, and the third portion of the received data overlap in part.

16. 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, a second portion of received data, and a third portion of received data, the first portion, second portion, and third portion comprising different portions of the received data;

selecting a token table from a set of token tables using a first portion of the received data, the selected token table mapping each of a plurality of input values to a different token value; and

after selecting the token table, transforming the received data to produce tokenized data by;

querying an initialization vector table with a value of the third portion of received data to obtain an initialization vector mapped to the value of the third portion of received data;

modifying the second portion of the received data with the initialization vector;

querying the token table with the modified second portion to identify a token value mapped to a value of the modified second portion; and

replacing the second portion of the received data with the identified token value to produce the tokenized data.

17. The non-transitory computer-readable storage medium of claim 16, 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.

18. The non-transitory computer-readable storage medium of claim 16, wherein the second portion of the received data is modified at least in part by adding the value of the third portion of the received data to a value of the second portion of the received data.

19. The non-transitory computer-readable storage medium of claim 16, wherein the set of token tables are stored on a plurality of servers.

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