Method for secured data processing

• US 20040068650A1
• Filed: 02/24/2003
• Published: 04/08/2004
• Est. Priority Date: 03/08/2002
• Status: Active Grant

• Current Assignee: Algorithmic Research Limited
• Original Assignee: Algorithmic Research Limited
• Inventors: Naaman, Nir, Resnitzky, Uri
• Granted Patent: US 9,544,297 B2
• Time in Patent Office: Days
• US Class Current: 713/155
• 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/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 9/006 involving public key infrastructure [PKI] trust models network architecture or network communication protocol for supporting authentication of entities using certificates in a packet data network H04L63/0823
• CPC Class Codes: H04L 9/3268 using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]

Abstract

A method for facilitating secured data processing, the method includes generating, for each client out of at least two clients, a private key, and a public key; and storing at least the private keys at highly secured entity; whereas the highly secured entity is operable to utilize at least a the private key to perform public key infrastructure processing.

Claims

1. A method for facilitating secured data processing, the method comprising the steps of:

generating, for each client out of at least two clients, a private key, and a public key; and

storing at least the private keys at highly secured entity;

whereas the highly secured entity is operable to utilize at least a the private key to perform public key infrastructure processing.

2. The method of claim 1 further comprising a preliminary step of determining a need to generate a private and public key for a client.

3. The method of claim 2 whereas the step of determining is responsive to an enrollment of the client.

4. The method of claim 3 further comprising receiving client related information.

5. The method of claim 2 wherein the step of determining comprises accessing an entity other than the highly secured entity.

6. The method of claim 5 wherein the other entity is a client management entity.

7. The method of claim 1 further comprising a step of enabling a client to provide data to be processed by the highly secured entity.

8. The method of claim 7 wherein the step of enabling comprising establishing a secured session between a client and the highly secured entity.

9. The method of claim 8 wherein the step of establishing comprising generating and utilizing symmetric keys.

10. The method of claim 7 wherein the step of enabling comprising client authenticating.

11. The method of claim 1 further comprising preventing lower security level entities from retrieving the private key.

12. The method of claim 11 whereas each client is a lower security level entity.

13. The method of claim 1 wherein the public key infrastructure processing comprises generating digital signatures.

14. The method of claim 1 wherein the public key infrastructure processing comprises decryption.

15. The method of claim 1 further comprising encrypting the private key and storing the encrypted private key at the highly secured entity.

16. The method of claim 15 further comprising decrypting the encrypted private key during public key infrastructure processing.

17. The method of claim 15 wherein encrypting the private key by a secondary key.

18. The method of claim 17 wherein further comprising receiving client related information and generating the secondary key in response to the client related information.

19. The method of claim 1 wherein the highly secured entity comprises a tamper evident enclosure.

20. The method of claim 1 wherein the highly secured entity comprises a keyboard connected intelligent smartcard reader.

21. The method of claim 1 further comprising storing client attribute certificates at the highly secured entity.

22. The method of claim 1 further comprising the steps of requesting a certificate for a client and receiving the certificate for the client.

23. The method of claim 22 whereas the step of requesting comprises establishing a secure session with a certificate authority.

24. The method of claim 22 further comprising storing the received certificate in the highly secured entity.

25. The method of claim 22 wherein the highly secured entity comprises the certificate authority.

26. The method of claim 1 further comprising a step of deleting a private key in response to information provided by the client management entity.

27. The method of claim 1 further comprising a step of creating an audit log in the highly secure entity of all private key usages.

28. The method of claim 1 further comprising a step of sending data to be signed from the client to the highly secured entity and creating an archive of all signed documents.

29. The method of claim 1 further comprising a step of producing a backup encrypted database.

30. The method of claim 1 further comprising a step of updating the highly secured entity by digitally signed software.