IP Library Granted Patent US 10,776,503
Granted Patent B2
US 10,776,503 · App. 15/812,875 · Granted Sep 15, 2020

System of enclaves

Inventors: Nelly Porter (Kirkland, WA); David Benson Cross (Redmond, WA); Uday Ramesh Savagsonkar (Redmond, WA); Brandon S. Baker (Redmond, WA); Sergey Simakov (Redmond, WA)
Assignee: Google LLC
G06F21/6218G06F21/6245G06F21/64G06F21/70H04L63/08H04L63/126H04L67/10G06F2221/2105
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,776,503
App. No.
15/812,875
Granted
Sep 15, 2020
Kind
B2
Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for instantiating and managing systems that utilize hierarchal enclaves in a cloud environment.

Claims (29)

1. A method performed by data processing apparatus, the method comprising:

launching a root enclave;

accessing an enclave manifest by the root enclave, wherein the enclave manifest specifies, for each of a plurality of component enclaves, a particular role for the component enclave; and

instantiating each of the component enclaves, each component enclave configured to perform its respective role;

wherein:

the root enclave and the plurality of component enclaves form an enclave pod, wherein the enclave pod is an isolated and secure execution environment in which users may run their application payloads; and

each component enclave of the enclave pod has a respective first key to securely communicate with other component enclaves of the enclave pod through a voting process, wherein the first key is certified by the root enclave by use of a second key, wherein the respective first keys are respective fragments of the first key that has been split into the respective fragments and wherein the first key is an entire enclave pod signing key, and the first key generated by the respective key fragments is also certified by the root enclave, for each component enclave, by the same second key to share information among the component enclaves.

2. The method of claim 1 , further comprising:

generating logs based on all transactions or actions performed in at least the component enclaves; and

cryptographically signing the logs with keys of the enclave pod.

3. The method of claim 1 , further comprising:

providing, from the root enclave, to a verifier, the identity of the root enclave and that of the manifest; and

receiving, from the verifier in response to a verification of the identity of the root enclave and the manifest, one or more of data and code to the component enclaves.

4. The method of claim 1 , wherein each enclave is a trusted execution environment.

5. A system, comprising:

a plurality of computers each in data communication with each other; and

a non-transitory computer readable medium storing instructions executable by the computers and that upon such execution cause the computers to perform operations comprising:

launching a root enclave;

accessing an enclave manifest by the root enclave, wherein the enclave manifest specifies, for each of a plurality of component enclaves, a particular role for the enclave; and

instantiating each of the component enclaves, each component enclave configured to perform its respective role;

wherein:

the root enclave and component enclaves form an enclave pod, wherein the enclave pod is an isolated and secure execution environment in which users may run their application payloads; and

each component enclave of the enclave pod has a respective first key to securely communicate with other component enclaves of the enclave pod through a voting process, wherein the first key is certified by the root enclave by use of a second key, wherein the respective first keys are respective fragments of the first key that has been split into the respective fragments, and wherein the first key is an entire enclave pod signing key, and the first key generated by the respective key fragments is also certified by the root enclave, for each component enclave, by the same second key to share information among the component enclaves.

6. The system of claim 5 , the operations further comprising:

generating logs based on all transactions or actions performed in at least the component enclaves; and

cryptographically signing the logs with keys of the enclave pod.

7. System of claim 5 , the operations further comprising:

providing, from the root enclave, to a verifier, the identity of the root enclave and that of the manifest; and

receiving, from the verifier in response to a verification of the identity of the root enclave and the manifest, one or more of data and code to the component enclaves.

Assignments (2)
CHANGE OF NAME Recorded Dec 21, 2017
From: GOOGLE INC.
To: GOOGLE LLC
Reel/Frame 044940/0371 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 21, 2017
From: PORTER, NELLY; CROSS, DAVID BENSON; SAVAGSONKAR, UDAY RAMESH; BAKER, BRANDON S.; SIMAKOV, SERGEY
To: GOOGLE INC.
Reel/Frame 044188/0275 →
Continuity (2)
Provisional Application 62421905 · Nov 14, 2016
Related Publication 20180137299A1 · May 17, 2018
Cited By (1)
US 12,719,869