OpenZeppelin / OpenZeppelin/guardian
TEE integration
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 10
- Forks
- 20
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 43
Description
In order to enforce confidentiality, we want to run the PSM server in a Trusted Execution Environment (TEE). The scope of this task is:
- to decouple the TLS layer from the API and the Storage layer from the rest of the app
- so upon receiving a request the flow is:
Host (TLS redirection) -> Enclave (TLS termination + API + business logic) -> Host (storage)
- We will initially use AWS nitro enclaves for this first integration
- We will manage TLS keys inside the enclave, so the host cannot read any inbound or outbound traffic.
- We will also keep an encryption key in the enclave, and encrypt/decrypt payloads from storage, so the host cannot read the payloads to be persisted.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by reviewing the Rust application's TLS, API, business-logic, and storage boundaries, then study AWS Nitro Enclaves integration. Done means TLS termination and key handling occur in the enclave, while the host only redirects TLS and stores encrypted payloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, rust
- Domain
- backend, cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100