IP Library Granted Patent US 8,401,183
Granted Patent B2
US 8,401,183 · App. 11/965,173 · Granted Mar 19, 2013

Method and system for keying and securely storing data

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,401,183
App. No.
11/965,173
Granted
Mar 19, 2013
Kind
B2
Abstract

An approach is provided for securely storing sensitive data. A system is provided that includes a central device configured to receive a key from a requester, to obtain a new key associated with the key, and to transmit the new key to the requestor, and a storage device for storing the new key in association with the key. Also, a secure system is provided that includes a parsing unit that parses an actual data value into a first data field and a second data field, a key generation unit that generates a key, a first process that transmits the key to a central manager and receives a new key associated with the key from the central manager, and at least one storage device configured to store the first data field in association with the key, and to store the second data field in association with the new key.

Claims (63)

1. A method comprising:

receiving, at a remote device, a storage request of a requesting device and a key for a secure storage of data, wherein the data is parsed, by the requesting device, into a first data field and a second data field, and the first data field is stored with the key in a first storage of the requesting device in a manner whereby the first data field is retrievable from the first storage using the key;

generating, by the remote device, a new key corresponding to the key, and storing the new key with the key in a remote storage of the remote device; and

transmitting, by the remote device, the new key to the requesting device for storage of the second data field with the new key in a second storage of the requesting device in a manner whereby the second data field is retrievable from the second storage using the new key.

2. The method according to claim 1 , wherein the new key is generated by encrypting the key.

3. The method according to claim 1 , wherein the new key is generated by generating a replacement key for the key.

4. The method according to claim 1 , wherein the new key is generated by encrypting the key and generating a replacement key for the encrypted key.

5. The method according to claim 1 , wherein the new key does not have an algorithmic link to the key.

6. The method according to claim 1 , further comprising:

receiving, from the requesting device, a retrieval request and the key;

retrieving the new key; and

transmitting the new key to the requesting device for retrieval of the second data field.

7. The method according to claim 1 , wherein the first and second data fields are stored in an unencrypted format.

8. A method comprising:

parsing, by a client device, data into a first data field and a second data field for secure storage of the data, and storing the first data field with a key in a first storage of the client device in a manner whereby the first data field is retrievable from the first storage using the key;

transmitting a request and the key, to a remote device, for generation of a new key corresponding to the key, wherein, in response to the request, the new key is generated and stored with the key in a remote storage of the remote device;

receiving, by the client device, the new key; and

storing the second data field with the new key in a second storage of the client device in a manner whereby the second data field is retrievable from the second storage using the new key.

9. The method according to claim 8 , wherein the new key is an encrypted version of the key.

10. The method according to claim 8 , wherein the new key is a replacement key for the key.

11. The method according to claim 8 , wherein the new key is a replacement key for an encrypted version of the key.

12. The method according to claim 8 , further comprising:

transmitting a retrieval request and the key for retrieval of the new key;

receiving the new key;

retrieving the first data field from the first storage using the key;

retrieving the second data field from the second storage using the new key; and

restoring the data using the retrieved first data field and the retrieved second data field.

13. The method according to claim 8 , wherein the first and second data fields are stored in an unencrypted format.

14. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code for one or more programs,

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following:

receive, from a requesting device, a storage request and a key for a secure storage of data, wherein the data is parsed, by the requesting device, into a first data field and a second data field, and the first data field is stored with the key in a first storage of the requesting device in a manner whereby the first data field is retrievable from the first storage using the key;

generate a new key corresponding to the key;

transmit the new key to the requesting device for storage of the second data field with the new key in a second storage of the requesting device in a manner whereby the second data field is retrievable from the second storage using the new key; and

store the new key with the key.

15. The apparatus according to claim 14 , wherein the apparatus is further caused to:

generate the new key by encrypting the key.

16. The apparatus according to claim 14 , wherein the apparatus is further caused to:

generate the new key by generating a replacement key for the key.

17. The apparatus according to claim 14 , wherein the apparatus is further caused to:

encrypt the key, and to generate the new key by generating a replacement key for the encrypted key.

18. The apparatus according to claim 14 , wherein the new key does not have an algorithmic link to the key.

19. The apparatus according to claim 14 , wherein the apparatus is further caused to,

receive, from the requesting device, a retrieval request and the key,

retrieve the new key, and

transmit the new key to the requesting device for retrieval of the second data field.

20. An apparatus according to claim 14 , wherein the first and second data fields are stored in an unencrypted format.

21. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code for one or more programs,

the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following:

parse data into a first data field and a second data field for secure storage of the data;

generate a key;

transmit a request and the key to a remote device for generation of a new key corresponding to the key, wherein, in response to the request, the new key is generated and stored with the key in a remote storage of the remote device, and configured to receive the new key; and

store the first data field with the key in a manner whereby the first data field is retrievable from the at least one storage module using the key, and store the second data field with the new key in a manner whereby the second data field is retrievable from the at least one storage module using the new key.

22. The apparatus according to claim 21 , wherein the apparatus is further caused to,

transmit a retrieval request and the key for retrieval of the new key,

receive the new key,

retrieve the first data field from the at least one storage module using the key,

retrieve the second data field from the at least one storage module using the new key, and

restore the data using the retrieved first data field and the retrieved second data field.

23. An apparatus according to claim 21 , wherein the first and second data fields are stored in an unencrypted format.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 18, 2009
From: VERIZON BUSINESS NETWORK SERVICES INC.
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 023250/0710 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 27, 2007
From: DODD, THOMAS LANCE
To: VERIZON BUSINESS NETWORK SERVICES INC.
Reel/Frame 020294/0200 →