METHOD OF TRANSFERRING THE CONTROL OF A SECURITY MODULE FROM A FIRST ENTITY TO A SECOND ENTITY

• US 20140359295A1
• Filed: 10/12/2012
• Published: 12/04/2014
• Est. Priority Date: 10/14/2011
• Status: Active Grant

• Current Assignee: Orange S.A.
• Original Assignee: Orange S.A.
• Inventors: Saif, Ahmad, Pladeau, Bertrand
• Granted Patent: US 9,124,561 B2
• Time in Patent Office: Days
• US Class Current: 713/173
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/086 using security domains

Abstract

A method is provided for transferring control of a security module from a first entity to a second entity. The security module has a first security domain controlled by the first entity by at least one first secret control key specific to the first entity, and a second security domain, the second domain containing a private key and a certificate of a public key of a controlling authority. The method includes: receiving a request to obtain the certificate; sending the certificate; receiving data encrypted by the public key of the certificate, the data including at least one second secret control key specific to the second entity; decrypting the data; verifying the data; and if the verification is positive, replacing the at least one first secret control key by the at least one second secret control key.

Claims

1. A method comprising:

transferring the control of a security module from a first entity to a second entity, the security module having a first security domain controlled by the first entity by at least one first secret control key specific to the first entity, and a second security domain, said second security domain including both a certificate of a public key of a controlling authority and also a private key of the controlling authority, wherein transferring comprises the following steps performed by the security module;

the second security domain receiving a request to obtain a certificate, the request coming from the second entity;

the second security domain sending said certificate;

the first security domain receiving data from the second entity, which data has been encrypted by the public key certified by said certificate, the data including at least one second secret control key specific to the second entity;

the second security domain decrypting said data;

the first security domain verifying the data; and

if the verification is positive, the first security domain replacing the at least one first secret control key with said at least one second secret control key.

2. The method according to claim 1, including a reception step of receiving from the first entity a request to transfer control to the second entity.

3. The method according to claim 2, wherein the transfer request includes a certificate of the second entity.

4. The method according to claim 2, wherein the transfer request includes a unique identifier of the second entity.

5. The method according to claim 1, including a step of the first security domain calculating a signed unique token and sending it to the first entity.

6. The method according to claim 5, wherein the data also includes a unique token signed by the issuer first domain.

7. The method according to claim 5, wherein the unique token also includes an identifier specific to the security module.

8. The method according to claim 1, wherein the encrypted data is signed by a second entity, verification of the data consisting in verifying the signature of the data.

9. The method according to claim 1, wherein the decrypting step comprises the following substeps:

the first security domain sending to the controlling authority security domain a request to decrypt said data;

the controlling authority security domain decrypting said data by the secret key of the controlling authority; and

the controlling authority security domain sending the decrypted data to the first security domain.

10. A security module hardware device comprising:

a first security domain and a second security domain, said second security domain containing both a certificate of a public key of a controlling authority and also a secret key of the controlling authority, the first security domain being controlled by a first entity by means of at least one first control key specific to the first entity;

at least one memory device; and

a processing device configured by instructions stored in the at least one memory device to form the following elements;

first reception means arranged to receive a request to obtain a certificate coming from a second entity;

sender means arranged to send said certificate to the second entity;

second reception means arranged to receive from the second entity data that has been encrypted by the public key certified by said certificate, the data including at least one second secret control key specific to the second entity;

decryption means arranged to decrypt said data;

verification means arranged to verify said data; and

installation means arranged to install said at least one second secret control key, the second entity then controlling the first security domain.

11. (canceled)

12. A non-transitory data storage medium comprising a program stored thereon for installing in a security module, the program including instructions for configuring the security module to perform steps of a method of transferring control of the module from a first entity to a second entity when the program is executed by a processor, wherein the method comprises:

transferring the control of the security module from the first entity to the second entity, the security module having a first security domain controlled by the first entity by at least one first secret control key specific to the first entity, and a second security domain, said second security domain including both a certificate of a public key of a controlling authority and also a private key of the controlling authority, wherein transferring comprises the following steps;

the second security domain receiving a request to obtain a certificate, the request coming from the second entity;

the second security domain sending said certificate;

the first security domain receiving data from the second entity, which data has been encrypted by the public key certified by said certificate, the data including at least one second secret control key specific to the second entity;

the second security domain decrypting said data;

the first security domain verifying the data; and

if the verification is positive, the first security domain replacing the at least one first secret control key with said at least one second secret control key.

13. (canceled)