Token-based secure data management
First Claim
1. A method comprising:
- receiving, by one or more computing devices, encrypted user data that includes sensitive user data and related nonsensitive user data related to a transaction;
decrypting, by at least one of the one or more computing devices, the encrypted user data;
generating, by at least one of the one or more computing devices, a token for the sensitive user data, the token including a description of a data type of the sensitive user data and a randomly generated string;
storing, with a first data storage service by at least one of the one or more computing devices, the sensitive user data;
storing, with a second data storage service by at least one or more computing devices, the token with the related nonsensitive data;
providing, to a first entity by at least one of the one or more computing devices, the token and the related nonsensitive data, the token provided in place of the sensitive user data;
receiving, by at least one of the one or more computing devices, a request for the sensitive user data from a second entity, wherein the request includes the token previously provided to the first entity and subsequently provided to the second entity by the first;
determining by at least one of the one or more computing devices, an authorization of the second entity to access the sensitive user data based on access policies for the second entity; and
providing, by at least one of the one or more computing devices, the sensitive user data to the second entity in accordance with the access policies for the second entity;
wherein;
the access policies for the second entity specify that the second entity is authorized to receive only a portion of the sensitive user data; and
providing the sensitive user data to the second entity further comprises providing only the portion of the sensitive user data specified by the access policies for the second entity.
1 Assignment
0 Petitions
Accused Products
Abstract
In some implementations, tokens that are representative of sensitive data may be used in place of the sensitive data to maintain the security of the sensitive data. For example, data may be separated into sensitive data and nonsensitive data, and at least the sensitive data is securely delivered to a data storage service. The data storage service generates a token that is representative of the sensitive data and stores the sensitive data as secure data. The data storage service may deliver the token to an entity that also receives the nonsensitive data, and the entity may use the token in place of the sensitive data. In some implementations, different tokens are generated each time the same piece of sensitive data is submitted for storage as secure data. Further, in some implementations, access policies define authorizations regarding which entities are able to resolve a token to access the actual sensitive data.
-
Citations
19 Claims
-
1. A method comprising:
-
receiving, by one or more computing devices, encrypted user data that includes sensitive user data and related nonsensitive user data related to a transaction; decrypting, by at least one of the one or more computing devices, the encrypted user data; generating, by at least one of the one or more computing devices, a token for the sensitive user data, the token including a description of a data type of the sensitive user data and a randomly generated string; storing, with a first data storage service by at least one of the one or more computing devices, the sensitive user data; storing, with a second data storage service by at least one or more computing devices, the token with the related nonsensitive data; providing, to a first entity by at least one of the one or more computing devices, the token and the related nonsensitive data, the token provided in place of the sensitive user data; receiving, by at least one of the one or more computing devices, a request for the sensitive user data from a second entity, wherein the request includes the token previously provided to the first entity and subsequently provided to the second entity by the first; determining by at least one of the one or more computing devices, an authorization of the second entity to access the sensitive user data based on access policies for the second entity; and providing, by at least one of the one or more computing devices, the sensitive user data to the second entity in accordance with the access policies for the second entity; wherein; the access policies for the second entity specify that the second entity is authorized to receive only a portion of the sensitive user data; and providing the sensitive user data to the second entity further comprises providing only the portion of the sensitive user data specified by the access policies for the second entity. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A method comprising:
-
receiving, by one or more computing devices sensitive data and related nonsenstive data, a first time, wherein the sensitive data and related nonsensitive data are related to a transaction; generating, by at least one of the one or more computing devices, a first token for the sensitive data, the first token including a description of a data type of the sensitive data and a first randomly generated string; storing, by at least one of the one or more computing devices, the sensitive data as secure data; providing, by at least one of the one or more computing devices, the related nonsensitive data and the first token in place of the sensitive data to an entity authorized to receive the related nonsensitive data for the transaction; receiving, by at least one of the one or more computing devices, the sensitive data a second time; generating, by at least one of the one or more computing devices, a second token for the sensitive data, the second token including a second randomly generated string that is different than the first randomly generated string associated with the first token; receiving, by at least one of the one or more computing devices, a demand from one or more data consumers desiring to access the sensitive data and the nonsensitive data; and establishing, by at least one of the one or more computing devices, access policies defining authorizations of each of the one or more data consumers to access the sensitive data and the nonsensitive data; wherein the access policies specify that different data consumers are provided different amounts of the sensitive data in response to calls received using a same token. - View Dependent Claims (7, 8, 9, 10, 11, 12, 13)
-
-
14. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed, cause one or more processors to perform operations comprising:
-
receiving a first piece of sensitive data and nonsensitive data associated with the first piece of sensitive data; generating a first token for the first piece of sensitive data, the first token including a randomly generated first string, and a description of a data type of the first piece of sensitive data; storing the first piece of sensitive data as secure data; providing the nonsensitive data associated with the first piece of sensitive data and the first token in place of the first piece of sensitive data to a first entity; receiving, by a data storage service, a second piece of sensitive data that is same as the first piece of sensitive data; generating a second token for the second piece of sensitive data, the second token including a randomly generated second string that is different from the first string, and a description of a data type of the second piece of sensitive data; providing the second token in place of the second piece of sensitive data to a second entity that maintains nonsensitive data associated with the second piece of sensitive data; receiving a demand from one or more data consumers desiring to access the sensitive data; and establishing access policies that allow different data consumers to be provided with different amounts of the sensitive data in response to demands received using a same token. - View Dependent Claims (15, 16, 17, 18, 19)
-
Specification