EBCC: Enclave-Backed Confidential Containers via OCI-Compatible Runtime Integration
Di Lu, Qingwen Zhang, Yujia Liu, Xuewen Dong, Yulong Shen + 2 more
TLDR
EBCC integrates TEE-backed confidential containers with standard OCI runtimes, simplifying management of secure workloads.
Key contributions
- EBCC provides an OCI-compatible runtime for managing confidential computing workloads.
- Unifies REE and TEE stages into a single containerized composite, preserving OCI lifecycle operations.
- Maintains persistent per-instance state and artifacts for request handling and evidence binding.
- Demonstrates cross-TEE compatibility across enclave-style, VM-style, and embedded-style TEEs.
Why it matters
Existing confidential container systems often deviate from standard OCI lifecycles. EBCC bridges this gap, making TEE-backed execution manageable via OCI without materially enlarging the protected-side TCB. This simplifies deployment and integration of secure workloads.
Original Abstract
Container runtimes provide a stable operational interface for deploying, monitoring, and controlling modern workloads, while trusted execution environments (TEEs) provide hardware-enforced isolation for sensitive computation. Existing confidential-container systems often rely on VM-backed deployment stacks or TEE-specific execution substrates, which can separate confidential execution from the conventional OCI runtime lifecycle. This paper presents EBCC (Enclave-Backed Confidential Containers), an OCI-compatible runtime architecture for managing composite confidential-computing workloads. EBCC treats the REE-side anchor and TEE-side confidential stages as a single containerized confidential-computing composite, preserves standard OCI lifecycle operations, and keeps TEE-specific execution behind a backend adapter. It also maintains persistent per-instance state and per-stage artifacts for request handling, response generation, logging, and evidence binding. We implement EBCC on a Keystone backend and evaluate its correctness, performance, footprint, and concurrent execution behavior. The results show that EBCC introduces additional latency over native Keystone execution, mainly due to lifecycle mediation, request validation, EID allocation, backend dispatch, and artifact persistence, while keeping the added footprint concentrated on host-side management state. Cross-TEE case studies on SGX, TDX, and OP-TEE show that the same lifecycle and stage abstraction can be mapped to enclave-style, VM-style, and embedded-style TEEs. These results indicate that EBCC can make TEE-backed execution manageable through an OCI-style lifecycle without materially enlarging the protected-side TCB.
📬 Weekly AI Paper Digest
Get the top 10 AI/ML arXiv papers from the week — summarized, scored, and delivered to your inbox every Monday.