Enclave pool shared key

Patent metadata

Field	Value
Publication number	US-10528722-B2
Application number	US-201715592802-A
Country	US
Kind code	B2
Filing date	May 11, 2017
Priority date	May 11, 2017
Publication date	Jan 7, 2020
Grant date	Jan 7, 2020

Abstract

In one example, an enclave pool is formed. The enclave pool may include a plurality of enclaves. Each enclave may have a private enclave key and a public enclave key. A shared enclave pool key may be generated from or otherwise based on the public enclave key of each enclave of the enclave pool. A first enclave may be allocated from the enclave pool to a first cryptlet. A payload of the first enclave is received. The payload of the first enclave may be signed with a first digital signature by the private enclave key of the first enclave. A payload of the second enclave may be received. The payload of the second enclave may be signed with a second digital signature by the private enclave key of the second enclave. The first digital signature and the second signature may be validated via the shared enclave pool key.

First claim

I claim:

1. An apparatus, comprising:
a device including at least one memory adapted to store run-time data for the device, and at least one processor that is adapted to execute processor-executable code that, in response to execution, enables the device to perform actions, including:
forming an enclave pool, wherein the enclave pool includes a plurality of enclaves, wherein the enclaves are secure execution environments, and wherein each enclave of the enclave pool has an enclave key pair including a private enclave key and a public enclave key;
generating a shared enclave pool key that is derived from the public enclave key of each enclave of the enclave pool;
allocating a first enclave of the enclave pool to a first cryptlet;
receiving a payload of the first enclave such that the payload of the first enclave has a first digital signature by the private enclave key of the first enclave;
allocating a second enclave of the enclave pool to the first cryptlet;
receiving a payload of the second enclave such that the payload of the second enclave has a second digital signature by the private enclave key of the second enclave; and
validating, via the shared enclave pool key, the first digital signature and the second signature.

2. The apparatus of claim 1 , the actions further comprising:
allocating a third enclave of the enclave pool to the first cryptlet;
receiving a payload of the third enclave such that the payload of the third enclave has a third digital signature by the private enclave key of the third enclave; and
further validating, via the shared enclave pool key, the third digital signature.

3. The apparatus of claim 1 , the actions further comprising:
adding a new enclave to the enclave pool to form an updated enclave pool; and
generating a new shared enclave pool key from the public enclave key of each enclave of the updated enclave pool, wherein validating the first digital signature and the second digital signature include validating the first digital signature and the second digital against the shared enclave key, and if no match is found, validating the first digital signature and the second digital against the new shared enclave key.

4. The apparatus of claim 1 , the actions further comprising:
removing an enclave from the enclave pool to form an updated enclave pool; and
generating a new shared enclave pool key from the public enclave key of each enclave of the updated enclave pool, wherein validating the first digital signature and the second digital signature include validating the first digital signature and the second digital against the shared enclave key, and if no match is found, validating the first digital signature and the second digital against the new shared enclave key.

5. The apparatus of claim 1 , wherein the enclaves of the plurality of enclaves are private, tamper-resistant execution environments that are secure from external interference.

6. The apparatus of claim 1 , wherein each enclave of the plurality of enclaves is at least one of a Virtual Secure Machine or a secure hardware enclave.

7. The apparatus of claim 1 , wherein the enclaves of the plurality of enclaves are secure execution environments in which code can be run in an isolated, private environment and for which results of the secure execution are capable of being attested to have run unaltered and in private.

8. The apparatus of claim 1 , wherein the first enclave is a hardware enclave, and wherein the private key of the first enclave is etched in silicon.

9. A processor-readable storage medium, having stored thereon process-executable code that, upon execution by at least one processor, enables actions, comprising:
creating an enclave pool, wherein the enclave pool includes a plurality of enclaves, the enclaves are secure execution environments, and wherein each enclave of the enclave pool stores an enclave key pair including a private enclave key and a public enclave key;
receiving the public enclave key of each enclave of the enclave pool;
generating a shared enclave pool key that is based upon the public enclave key of each enclave of the enclave pool;
assigning a first enclave of the enclave pool to a first cryptlet;
receiving a payload of the first enclave such that the payload of the first enclave has a first signature by the private enclave key of the first enclave;
assigning a second enclave of the enclave pool to the first cryptlet;
receiving a payload of the second enclave such that the payload of the second enclave has a second signature by the private enclave key of the second enclave; and
using the shared enclave pool key to validate the first signature and the second signature.

10. The processor-readable storage medium of claim 9 , the actions further comprising:
allocating a third enclave of the enclave pool to the first cryptlet;
receiving a payload of the third enclave such that the payload of the third enclave has a third digital signature by the private enclave key of the third enclave; and
further validating, via the shared enclave pool key, the third digital signature.

11. The processor-readable storage medium of claim 9 , the actions further comprising:
adding a new enclave to the enclave pool to form an updated enclave pool; and
generating a new shared enclave pool key from the public enclave key of each enclave of the updated enclave pool, wherein validating the first digital signature and the second digital signature include validating the first digital signature and the second digital against the shared enclave key, and if no match is found, validating the first digital signature and the second digital against the new shared enclave key.

12. The processor-readable storage medium of claim 9 , the actions further comprising:
removing an enclave from the enclave pool to form an updated enclave pool; and
generating a new shared enclave pool key from the public enclave key of each enclave of the updated enclave pool, wherein validating the first digital signature and the second digital signature include validating the first digital signature and the second digital against the shared enclave key, and if no match is found, validating the first digital signature and the second digital against the new shared enclave key.

13. The processor-readable storage medium of claim 9 , wherein each enclave of the plurality of enclaves is at least one of a Virtual Secure Machine or a secure hardware enclave.

14. The processor-readable storage medium of claim 9 , wherein the first enclave is a hardware enclave, and wherein the private key of the first enclave is etched in silicon.

15. A method, comprising:
forming an enclave pool, wherein the enclave pool includes a plurality of enclaves, wherein the enclaves are secure execution environments, and wherein each enclave of the enclave pool has an enclave key pair including a private enclave key and a public enclave key;
generating a shared enclave pool key that is derived from the public enclave key of each enclave of the enclave pool;
allocating a first enclave of the enclave pool to a first cryptlet;
receiving a payload of the first enclave such that the payload of the first enclave has a first digital signature by the private enclave key of the first enclave;
allocating a second enclave of the enclave pool to the first cryptlet;
receiving a payload of the second enclave such that the payload of the second enclave has a second digital signature by the private enclave key of the second enclave; and
validating, via the shared enclave pool key, the first digital signature and the second signature.

16

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Gray John Marley

Classifications

• G06F21/71 Primary

  to assure secure computing or processing of information · CPC title

• G06F21/53 Primary

  by executing in a restricted environment, e.g. sandbox or secure virtual machine · CPC title

• H04L9/3268

  using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL] · CPC title

• H04L9/0861

  Generation of secret information including derivation or calculation of cryptographic keys or passwords · CPC title

• H04L9/3247

  involving digital signatures · CPC title