Demand Based Encryption and Key Generation and Distribution Systems and Methods

• US 20140369501A1
• Filed: 08/15/2014
• Published: 12/18/2014
• Est. Priority Date: 11/03/2011
• Status: Active Grant

• Current Assignee: Arvind Gidwani
• Original Assignee: Arvind Gidwani
• Inventors: Gidwani, Arvind
• Granted Patent: US 9,270,447 B2
• Time in Patent Office: Days
• US Class Current: 380/282
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• 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/062 for key distribution, e.g. centrally by trusted party cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 9/08 Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords network architectures or network communication protocols for supporting key management in a packet data network H04L63/06
• CPC Class Codes: H04L 9/0819 Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) network architectures or network communication protocols for key distribution in a packet data network H04L63/062
• CPC Class Codes: H04L 9/083 involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
• CPC Class Codes: H04L 9/30 Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy

Abstract

Systems and methods providing a key management platform that generates and distributes demand-based encryption and decryption keys are described.

Claims

1. A requester system, the system comprising:

processor operable to;

generate a request, identification information identifying a receiver system, and one or more use parameters associate with a data file;

send the request to a key management system, wherein the sending of the request is configured to cause the key management system to generate a private encryption key and a public encryption key;

send the identification information to the key management system, wherein the sending of the identification information is configured to cause the key management system to send the public encryption key to the receiver system;

receive the private encryption key from the key management system;

encrypt the data file using the private encryption key; and

send the encrypted data file to the receiving system.

2. The requester system of claim 1, wherein the processor encrypts the data file based on the use parameters.

3. The requester system of claim 1, wherein the processor is further operable to:

send the use parameters to the key management system, wherein the sending of the use parameters is configured to cause the key management system to generate the public encryption key based on the use parameters.

4. The requester system of claim 3, wherein the use parameters specify an expiration date of the public encryption key.

5. The requester system of claim 1, wherein the processor is further operable to:

modify the data file with the use parameters before the data file is encrypted.

6. The requester system of claim 1, wherein the processor is further operable to:

generate payment information; and

send the payment information to the key management system, wherein the sending of the payment information is configured to cause the key management system to generate the private encryption key and the public encryption key upon authentication of the payment information.

7. The requester system of claim 1, wherein the processor is further operable to:

send an access instruction to the receiving system, wherein the sending of the access instruction is configured to prohibit the receiving system from accessing the data file after a first number of access attempts by the receiving system and after an elapsed time period from when the encrypted data file was sent to the receiving system.

8. The requester system of claim 1, wherein the processor is further operable to:

receive a notification relating to an attempt, by the receiving system, at taking an action in relation to the data file;

generate, based on the notification, an instruction configured to deny the action; and

send the instruction to the receiving system, wherein the sending of the instruction is configured to prevent the receiving system from completing the action.

9. A key management system, the system comprising:

a processor operable to;

receive, from a requester system, a request to generate a private encryption key and a public encryption key;

receive, from the requester system, identification information identifying a receiver system;

generate a first private encryption key and a first public encryption key in response to receiving the request;

send the first private encryption key to the requester system; and

send the first public encryption key to the receiver system.

10. The key management system of claim 9, wherein the processor is further operable to:

receive, from the requester system, use parameters; and

generate, based on the use parameters, the first public encryption key.

11. The key management system of claim 10, wherein the use parameters specify an expiration date for the public encryption key.

12. The key management system of claim 9, wherein the processor is further operable to:

send an instruction specifying the use parameters to an application running on the receiving system, wherein the application controls access to an encrypted data file that was received from the requester system by the receiver system based on the instruction specifying the use parameters.

13. The key management system of claim 9, wherein the processor is further operable to:

generate one or more passcodes associated with the first private encryption key and the first public encryption key;

send at least one of the passcodes to the requester system; and

send at least one of the passcodes to the receiver system.

14. A requester system, the system comprising:

an interface for receiving an input from a user; and

a processor operable to;

generate a request for encryption, identification information identifying a receiver system, and one or more use parameters associate with a data file based upon the input from the user;

send the request to a key management system, wherein the sending of the request is configured to cause the key management system to identify the user and generate a private encryption key and a public encryption key;

send the identification information to the key management system, wherein the sending of the identification information is configured to cause the key management system to send the public encryption key to the receiver system;

receive the private encryption key from the key management system;

encrypt the data file using the private encryption key and based on the use parameters; and

send the encrypted data file to the receiver system.

15. The requester system of claim 14, wherein the processor is further operable to:

send the use parameters to the key management system, wherein the sending of the use parameters is configured to cause the key management system to generate the public encryption key based on the use parameters.

16. The requester system of claim 15, wherein the use parameters specify an expiration date of the public encryption key.

17. The requester system of claim 14, wherein the use parameters specify security restrictions of the data file.

18. The requester system of claim 14, wherein the use parameters restrict operation of the data file.

19. The requester system of claim 14, wherein the encryption is embedded in the data file.

20. The requester system of claim 14, wherein the processor is further operable to:

validate the private encryption key.

21. The requester system of claim 14, wherein the processor is further operable to:

modify the data file with the use parameters before the data file is encrypted.

22. The requester system of claim 14, wherein the processor is further operable to:

generate payment information; and

send the payment information to the key management system, wherein the sending of the payment information is configured to cause the key management system to generate the private encryption key and the public encryption key based upon authentication of the payment information.

23. The requester system of claim 14, wherein the processor is further operable to:

send an access instruction to the receiver system, wherein the sending of the access instruction is configured to prohibit the receiver system from accessing the data file after a first number of access attempts by the receiver system and after an elapsed time period from when the encrypted data file was sent to the receiver system.

24. The requester system of claim 14, wherein the processor is further operable to:

receive a notification relating to an attempt, by the receiver system, at taking an action in relation to the data file;

generate, based on the notification, an instruction configured to deny the action; and

send the instruction to the receiver system, wherein the sending of the instruction is configured to prevent the receiver system from completing the action.