System and method for distributed security

• US 9,264,223 B2
• Filed: 04/28/2014
• Issued: 02/16/2016
• Est. Priority Date: 06/03/2003
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom, Inc.
• Inventors: Buer, Mark
• Primary Examiner(s): Rahman, Mahfuzur
• Application Number:
  US14/263,844
• Publication Number:
  US 20140365764A1
• Time in Patent Office: 659 Days
• Field of Search: 713/157
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: H04L 63/04 for providing a confidential data exchange among entities communicating through data packet networks
• 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/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 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 9/0825 using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
• CPC Class Codes: H04L 9/3265 using certificate chains, trees or paths; Hierarchical trust model

Abstract

A security architecture in which a security module is integrated in a client machine, wherein the client machine includes a local host that is untrusted. The security module performs encryption and decryption algorithms, authentication, and public key processing. The security module also includes separate key caches for key encryption keys and application keys. A security module can also interface a cryptographic accelerator through an application key cache. The security module can authorize a public key and an associated key server. That public key can subsequently be used to authorize additional key servers. Any of the authorized key servers can use their public keys to authorize the public keys of additional key servers. Secure authenticated communications can then transpire between the client and any of these key servers. Such a connection is created by a secure handshake process that takes place between the client and the key server. A time value can be sent from the key server to the client, allowing for secure revocation of keys. In addition, secure configuration messages can be sent to the security module.

Claims

1. A client device configured to create a hierarchy of key servers, the client device comprising:

a local host configured to transfer a first public key associated with a first key server, wherein the first public key is configured to expire after a predetermined period of time; and

a security module configured to;

determine that the first key server is authorized by comparing information stored in the security module with a hash value of the first public key,

determine whether the first key server is permitted to authorize additional key servers, and

sign a second public key of a second key server with the first public key to authorize the second key server in response to determining that the first key server is permitted to authorize additional key servers.

2. The client device of claim 1, wherein the security module is further configured to authorize an additional key server using the first public key or the second public key.

3. The client device of claim 1, wherein the first public key is configured to expire after a countdown timer reaches zero.

4. The client device of claim 1, wherein the security module is further configured to:

receive a configuration message from the local host;

determine whether the configuration message is accompanied by a signature created by an authorized public key; and

load content of the configuration message in response to determining that the configuration message is accompanied by the signature.

5. The client device of claim 4, wherein the configuration message is configured to alter a functionality available to the security module.

6. The client device of claim 4, wherein the configuration message is configured to place a constraint on key length or remove the constraint on key length.

7. The client device of claim 4, wherein the configuration message is configured to determine how a given key is to be used in accordance with a system security policy.

8. The client device of claim 4, wherein the configuration message is configured to determine a time interval over which a given key is usable, in accordance with a system security policy.

9. A client device configured to establish an authenticated connection with a key server, the client device comprising:

a local host configured to transfer a first public key associated with the key server, wherein the first public key is configured to expire after a predetermined period of time; and

a security module configured to;

send a client random number to the key server,

receive a server random number, a signed session key, and a certificate from the key server,

determine whether the signed session key has been signed with a verified public key, and

compare a hash of the first public key with information stored in the security module.

10. The client device of claim 9, wherein the security module is further configured to:

generate the client random number.

11. The client device of claim 9, wherein the security module is further configured to:

store the client random number.

12. The client device of claim 9, wherein the security module is further configured to:

verify the signed session key in response to determining that the signed session key has been signed with the verified public key.

13. The client device of claim 9, wherein the security module is further configured to:

verify a handshake process with the key server in response to comparing the hash of the first public key with the information stored in the security module.

14. The client device of claim 9, wherein the security module is further configured to:

send a client certificate to the key server;

engage in a key exchange with the key server;

incorporate a client session key into a finished hash;

send a client finished message to the key server; and

receive a server finished message from the key server.

15. The client device of claim 9, wherein the security module is further configured to:

receive a key and a time value from the key server;

load the key at a key cache;

set a countdown timer to the time value; and

decrement the countdown timer.

16. The client device of claim 15, wherein the security module is further configured to:

render the key unusable if the countdown timer reaches zero or a next key is received from the key server with a next time value.

17. A security module configured to create a hierarchy of key servers, the security module comprising:

a memory; and

a controller configured to;

determine that the first key server is authorized by comparing information stored in the memory with a hash value of a first public key associated with a first key server, wherein the first public key is configured to expire after a predetermined period of time,

determine whether the first key server is permitted to authorize additional key servers, and

sign a second public key of a second key server with the first public key to authorize the second key server in response to determining that the first key server is permitted to authorize additional key servers.

18. The security module of claim 17, wherein the security module is further configured to authorize an additional key server using the first public key or the second public key.

19. The security module of claim 17, wherein the security module is further configured to:

receive a configuration message from a local host;

determine whether the configuration message is accompanied by a signature created by an authorized public key; and

load content of the configuration message in response to determining that the configuration message is accompanied by the signature.

20. The security module of claim 19, wherein the configuration message is configured to alter a functionality available to the security module.