# US 2014/0095879 A1 · Storing a key in a remote security module > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0095879 A1 - Document ID: US20140095879A1 - Status: Published application - Kind: A1 - Application number: 13/948,286 - Filed: 2013-07-23 - Published: 2014-04-03 - Earliest claimed: 2006-03-15 - Assignees: Activldentity, Inc. - Applicants: Activldentity - Inventors: Dominique Fedronic; Eric Le Saint; John Babbidge; Hong Liu - Web page: https://patentgrep.com/patent/US20140095879A1 ## CPC - H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates} - G06F 21/602: {Providing cryptographic facilities or services} - G06F 21/606: {by securing the transmission between two devices or processes} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A system obtains assurance by a content provider that a content control key is securely stored in a remote security module for further secure communications between the content provider and the security module. A security module manufacturer, which has a pre-established trustful relation with the security module, imports a symmetric transport key into the security module. The symmetric transport key is unique to the security module. The content provider shares the symmetric transport key with the security module manufacturer. The content provider exchanging messages with the security module through a security module communication manager in order to get the proof that the security module stores the content control key. At least a portion of the messages exchanged between the content provider and the security module are protected using the symmetric transport key. The symmetric transport key is independent of said content control key. ## Claims ### Claim 1 A method for obtaining assurance by a content provider that a content control key is securely stored in a remote security module for further secure communications between said content provider and said security module, the method comprising: a security module manufacturer, which has a pre-established trustful relation with said security module, importing a symmetric transport key into said security module, wherein said symmetric transport key is unique to said security module; said content provider sharing said symmetric transport key with said security module manufacturer; and said content provider exchanging messages with said security module through a security module communication manager in order to get the proof that said security module stores said content control key; wherein at least a portion of said messages exchanged between said content provider and said security module are protected using said symmetric transport key. ### Claim 2 (depends on 1) The method of claim 1, wherein said content provider stores said content control key, wherein a public key of an asymmetric key pair is transmitted to said security module, the corresponding private key of said asymmetric key pair being exclusively known by said content provider, and wherein said exchange of messages between said content provider and said security module comprises: said security module generating a session key, wrapping said session key with said public key and transmitting said wrapped session key to said content provider; said content provider receiving and unwrapping said session key thanks to said private key; and said content provider doubly wrapping said content control key with said session key and said symmetric transport key, and transmitting said doubly wrapped content control key to said security module. ### Claim 3 (depends on 2) The method of claim 2, wherein said exchange of messages between said content provider and said security module comprises: said content provider transmitting said public key to said security module along with a digital signature; and said security module verifying with said public key whether said digital signature was derived from said private key. ### Claim 4 (depends on 2) The method of claim 2, wherein said content control key is a secret symmetric key. ### Claim 5 (depends on 2) The method of claim 2, wherein said content control key is a private key of an asymmetric key pair, the corresponding public key of which is known by the content provider. ### Claim 6 (depends on 1) The method of claim 1, wherein said security module generates said content control key, wherein said content control key is a private key of an asymmetric key pair, wherein the corresponding public key of said asymmetric key pair is transmitted to said content provider, and wherein said exchange of messages between said content provider and said security module comprises: said content provider generating a challenge and transmitting it to said security module; said security module signing said challenge with said content control key, wrapping said signed challenge with said symmetric transport key and transmitting said wrapped signed challenge to said content provider; and said content provider unwrapping and verifying said wrapped signed challenge thanks to said public key and said symmetric transport key thus proving that said content control key is stored in said security module. ### Claim 7 (depends on 1) The method of claim 1, wherein said security module generates said content control key, wherein said content control key is a private key of an asymmetric key pair, wherein the corresponding public key of said asymmetric key pair is transmitted to said content provider, and wherein said exchange of messages between said content provider and said security module comprises: said content provider generating a challenge, wrapping said challenge with said symmetric transport key and transmitting said wrapped challenge to said security module; said security module unwrapping said challenge thanks to said symmetric transport key, signing said challenge with said content control key and transmitting said signed challenge to said content provider; and said content provider verifying said signed challenge thanks to said public key thus proving that said content control key is stored in said security module. ### Claim 8 (depends on 6, 7) The method of claim 6 or 7, wherein said content provider authenticates to said security module during said exchange of messages between said content provider and said security module. ### Claim 9 (depends on 1) The method of claim 1, wherein said security module communication manager does not have access to said symmetric transport key and said content control key. ### Claim 10 (depends on 1) The method of claim 1, wherein said symmetric transport key is generated using a unique identifier of said security module. ### Claim 11 A system for obtaining assurance by a content provider that a content control key is securely stored in a remote security module for further secure communications between said content provider and said security module, the system comprising: said content provider; said security module; a security module communication manager; and a security module manufacturer, which has a pre-established trustful relation with said security module and an interface for importing a symmetric transport key into said security module, wherein said symmetric transport key is unique to said security module, said security module manufacturer sharing said symmetric transport key with said content provider; wherein: said content provider and said security module are functionally connected for exchanging messages through a security module communication manager in order to get the proof that said security module stores said content control key; and said content provider and said security module are designed for protecting at least a portion of said messages exchanged between said content provider and said security module using said symmetric transport key. ### Claim 12 (depends on 11) The system of claim 11, wherein said content provider stores said content control key, wherein a public key of an asymmetric key pair is stored in said security module, the corresponding private key of said asymmetric key pair being known by said content provider, and wherein: said security module comprises a key generator for generating a session key, wrapping said session key with said public key and transmitting said wrapped session key to said content provider; said content provider comprising a receiver for receiving and unwrapping said session key thanks to said private key; and said content provider comprising a transmitter for doubly wrapping said content control key with said session key and said symmetric transport key, and transmitting said doubly wrapped content control key to said security module. ### Claim 13 (depends on 11) The system of claim 11, wherein said security module comprises a generator for generating said content control key, wherein said content control key is a private key of an asymmetric key pair, wherein the corresponding public key of said asymmetric key pair is stored in said content provider, and wherein: said content provider comprises a challenge generator for generating a challenge and transmitting it to said security module; said security module comprises a response generator for signing said challenge with said content control key, wrapping said signed challenge with said symmetric transport key and transmitting said wrapped signed challenge to said content provider; and said content provider comprises a receiver for unwrapping and verifying said wrapped signed challenge thanks to said public key and said symmetric transport key thus proving that said content control key is stored in said security module. ### Claim 14 (depends on 11) The system of claim 11, wherein said security module comprises a generator for generating said content control key, wherein said content control key is a private key of an asymmetric key pair, wherein the corresponding public key of said asymmetric key pair is stored in said content provider, and wherein: said content provider comprises a challenge generator for generating a challenge, wrapping said challenge with said symmetric transport key and transmitting said wrapped challenge to said security module; said security module comprises a response generator for unwrapping said challenge thanks to said symmetric transport key, signing said challenge with said content control key and transmitting said signed challenge to said content provider; and said content provider comprises a receiver for verifying said signed challenge thanks to said public key thus proving that said content control key is stored in said security module.