US 9,313,195 B2Granted

Collision avoidance in a distributed tokenization environment

AssigneeProtegrity Corporation

InventorsUlf Mattsson, Zvika Ferentz

Life of this patent

Estimating the term…

Loading patent…

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.

Claims12

Dependent claims

A computer-implemented method for tokenizing data in a distributed tokenization environment comprising a central token management system communicatively coupled to a plurality of clients, the method comprising:

receiving, by each of the plurality of clients each associated with a numeric identifier, a set of values from the central token management system such that each value in each set of values is not included in any other set of values and such that the set of values comprises a range of values associated with the numeric identifier associated with the client;
receiving, at a client, sensitive data to be tokenized;
querying a token table associated with the client with a portion of the sensitive data to determine if the token table includes a token mapped to a value of the portion of the sensitive data, the token table storing a plurality of tokens each mapped to a different value;
and
responsive to a determination that the token table does not include a token mapped to a value of the portion of the sensitive data:
after the client receives the set of values from the central token management system, generating a token unique to the client by selecting a value from the set of values received by the client from the central token management system, the selected value not included in any other set of values received by any other client of the plurality of clients;
tokenizing the sensitive data using the generated token;
and
storing the generated token in the token table associated with the client.

6 more elements

A non-transitory computer-readable medium storing executable computer instructions for tokenizing data in a distributed tokenization environments comprising a central token management system communicatively coupled to a plurality of clients, the instructions configured to:

receive, by each of the plurality of clients each associated with a numeric identifier, a set of values from the central token management system such that each value in each set of values is not included in any other set of values and such that the set of values comprises a range of values associated with the numeric identifier associated with the client;
receive, at a client, sensitive data to be tokenized;
query a token table associated with the client with a portion of the sensitive data to determine if the token table includes a token mapped to a value of the portion of the sensitive data, the token table storing a plurality of tokens each mapped to a different value;
and
responsive to a determination that the token table does not include a token mapped to a value of the portion of the sensitive data:
after the client receives the set of values from the central token management system, generate a token unique to the client by selecting a value from the set of values received by the client from the central token management system, the selected value not included in any other set of values received by any other client of the plurality of clients;
and
store the generated token in the token table associated with the client.

5 more elements

A system for tokenizing data comprising:

a plurality of client devices, each client device comprising a hardware processor and a non-transitory computer readable medium comprising instructions, the instructions when executed by the processor of the client device, cause the processor of the client device to:
receive, by each of the plurality of client devices each associated with a numeric identifier, a set of values from a central token management system such that each value in each set of values is not included in any other set of values and such that the set of values comprises a range of values associated with the numeric identifier associated with the client;
receive sensitive data to be tokenized;
query a token table associated with the client with a portion of the sensitive data to determine if the token table includes a token mapped to a value of the portion of the sensitive data, the token table storing a plurality of tokens each mapped to a different value;
and
responsive to a determination that the token table does not include a token mapped to a value of the portion of the sensitive data:
after the client receives the set of values from the central token management system, generate a token unique to the client device by selecting a value from the set of values received by the client from the central token management system, the selected value not included in any other set of values received by any other client of the plurality of clients;
and
store the generated token in the token table associated with the client device;
and
the central token management system communicatively coupled to the plurality of client devices.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application: 14/042,325Filed 30 Sep 2013
Published: US 2015/0096056 A12 Apr 2015
Granted: 12 Apr 2016
Term ends: Not estimatedThe source records don’t support an estimate.

Classification10 codes

H04L 63/0428
For providing a confidential data exchange among entities communicating through data packet networks: wherein the data content is protected, e.g.…
G06F 21/335
Using certificates: for accessing specific resources, e.g. using Kerberos tickets
H04L 63/04
Network architectures or network communication protocols for network security: for providing a confidential data exchange among entities…
H04L 63/08
Network architectures or network communication protocols for network security: for authentication of entities