architecture of confidential computing in computing aware network

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 2 September 2022.¶

Copyright Notice

Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

2. Motivation and Scope

3. General Architecture of Confidential Computing in Computing-Aware Network

     Targeting
+--> Environment
|  +-------------+     +----------+
|  | Application |  +->| APP Owner|<--+
|  +-------------+  |  +----------+   |
|  |  Middleware |<-+                 |
|  +-------------+                    |
|  |  TEEP Agent |<-----+             |
|  +-------------+      |             |
|                       |             |
|  +--------------------+------+      |
|  | Hypervisor    TEEP Broker |<--+  |
|  +---------------------------+   |  |
|  | CPU/Firmware    Attesting |   |  |
|  |                Environment|   |  |
|  +---------------------+-----+   |  |
|                        |         |  |
+------------------------+         |  |
                                   |  |
              +--------------------+--+-+
              |  TAM & Middleware Repo  |
              |          M/OC           |
              +-------------------------+

Figure 1 shows the basic architecture of confidential computing in Computing-Aware Network. This architecture refers to RATs [I-D.ietf-rats-architecture] arch and TEEP[I-D.ietf-teep-architecture] arch for remote attestation and trust execution environment provisioning. Confidential computing needs the support of CPU, in which MUST have the function of generating isolated execution environment and attesting environment. The layer of Hypervisor is for virtualization.¶

(1)

Targeting Environment¶

Targeting Environment is the computing environment e.g. virtual machine, process that could provide confidentiality and integrity for applications. When used for remote attestation, the Targeting Environment will be attested by application owner. Targeting environment includes Application, Middleware, and TEEP Agent.¶

(2)

Application¶

Application which runs in Computing-Aware network.¶

(3)

Middleware¶

Middleware in CC has two functions: enable remote attestation and environment provisioning; provide a user-friendly environment. Some confidential computing CPU like SGX needs to use middleware to provide a environment in where applications don't have to change their source code, e.g. Enarx [Enarx] and Occlum [Occlum].¶

(4)

TEEP Agent¶

TEEP Agent is a module for provisioning middleware and application in Targeting Environment.¶

(5)

TEEP Broker¶

TEEP Broker is only for communication between TEEP Agent and TAM, it doesn't have to know any confidential information.¶

(6)

Attesting Environment¶

Attesting Environment is hardware based component, like Intel Quote SGX, AMD SEV-SP, etc. This component is a part of TCB, and is used to collect targeting environment evidence for remote attestation.¶

(7)

M/OC¶

M/OC is the manage and orchestration console of Computing-Aware Network.¶

(8)

TAM¶

Trust Application Management, this entity is for provisioning of application and relevant middleware.¶

(9)

Middleware Repository¶

This repository keeps a variety of middleware packages, which is for TAM to access based on Application type and confidential computing hardware type.¶

4. Environment Provisioning

When deploying applications in Computing-Aware network, TAM will choose confidential computing environment and relevant Middleware to fit their applications. Meanwhile, Computing-Aware Network needs to provide the secure procedure of provisioning middleware and applications. This document uses TEEP as reference to provision Middleware and applications in Computing-Aware network.¶

     Targeting
     Environment
   +-------------+     +----------+
   | Application |     | App Owner|<--+
   +-------------+     +----------+   |
   |  Middleware |                    |
   +-------------+                    |
   |  TEEP Agent |<-----+             |
   +-------------+      |3            |
                        |             |
   +--------------------+------+      |1
   | Hypervisor    TEEP Broker |<--+  |
   +---------------------------+   |  |
   | CPU/Firmware    Attesting |   |  |
   |                Environment|   |2 |
   +---------------------+-----+   |  |
                                   |  |
                                   |  |
                                   |  |
              +--------------------+--+-+
              |  TAM & Middleware Repo  |
              |          M/OC           |
              +-------------------------+

The Provisioning steps in Computing-Aware Network are illustrated below.¶

(1)

First, Application owner requests for confidential computing resource in Computing-Aware Network. Second, based on the request and confidential computing resource type, TAM will chose appropriate middleware.¶

(2)

TAM establishes connections with TEEP Broker to transfer provisioning information.¶

(3)

TEEP Broker triggers the confidential computing platform to create Targeting Environment with TEEP Agent. Then TEEP Broker establishes connections with TEEP agent. TEEP agent receives the provisioning information and unpacks it as Middleware.¶

Need to clarify that at this stage the Middleware dosen't contain any secret information. The secret information of application should be provisioned after remote attestation. The specific mechanism of building targeting environment is based on specific CPU and is out of scope of this document.¶

5. Remote Attestation

In Computing-Aware Network, remote attestation is used for application owner to appraise if the Targeting Environment is trusted. Only after remote attestation, application owner could trust the confidential computing environment and deploy secret information. The general architecture of remote attestation in Computing-Aware Network is shown below.¶

     Targeting
+--> Environment
|  +-------------+ 1/4 +----------+
|  | Application |  +->| APP Owner|<--+
|  +-------------+  |  +----------+   |
|  |  Middleware |<-+                 |
|  +-------------+                    |
|  |  TEEP Agent |                    |
|  +-------------+                    |
|2                                    |3
|  +--------------------+------+      |
|  | Hypervisor    TEEP Broker |<--+  |
|  +---------------------------+   |  |
|  | CPU/Firmware    Attesting |   |  |
|  |                Environment|   |  |
|  +---------------------+-----+   |  |
|                        |         |  |
+------------------------+         |  |
                                   |  |
              +--------------------+--+-+
              |  TAM & Middleware Repo  |
              |          M/OC           |
              +-------------------------+

The remote attestation steps in Computing-Aware Network are shown below. After appraising the remote attestation evidence, the application owner could deploy secret data in Targeting Environment.¶

(1)

Application owner establishes secure connection with middleware and launches remote attestation request with certain parameters like nonce.¶

(2)

Targeting Environment launches evidence collection by Middleware. Middleware sends request to Attesting Environment for remote attestation evidence. After generating evidence by Attesting Environment, the evidence will be sent back to Middleware.¶

(3)

The Application Owner requests for TEEP agent and middleware source code to generate reference value and appraise the remote attestation evidence.¶

(4)

The Targeting Environment sends the evidence to Application Owner. After appraising, Application Owner sends its application and private data to Targeting Environment.¶

6. Use Case

Confidential computing provides confidentiality and integrity of data and applications in the running stage. This document depicts the abstract architecture of confidential computing from the perspective of Computing-Aware Network. The following are some use cases of confidential computing in Computing-Aware Network.¶

VR/AR Application: Users wants to use Computing-Aware Network to host VR communication and interaction with other user. They don't want their conversation to be awared by the network. And it is hard to encrypt all the VR context because of unacceptable cost. So, the users choose confidential computing to protect their privacy. After the remote attestation of computing environment, the users could transfer and process private information in Computing-Aware Network.¶

Medical Imaging Aalysis: A medical institute wants to use Computing-Aware Network to share and process medical images in different branches. One primary concern is that they don't want the patients' medical images to be leaked. So they choose confidential computing to process these images.¶

7. Security Considerations

The root of trust of confidential computing is the CPU hardware. Application Owner could use the certificate or signature in remote attestation information to verify the identity of CPU. The connections between Application Owner and their applications are protected by security protocols like TLS.¶

8. Acknowledgements

The author would like to thank Eric Voit, Mike Bursul and Dave Thaler in CCC group who have provided valuable supports and suggestions.¶

9. IANA Considerations

This memo includes no request to IANA.¶

Authors' Addresses