A platform for building distributed systems with hardware-backed remote attestation and encrypted communication using Trusted Execution Environments.
Oak is a platform for building distributed systems with hardware-backed security, using Trusted Execution Environments (TEEs) to create remotely attestable Enclave Applications. It solves the problem of establishing trust in untrusted environments by enabling nodes to verify each other's software identity and communicate over encrypted channels. This allows developers to build systems where service providers cannot access sensitive data or tamper with computations.
Developers and organizations building secure, privacy-preserving distributed systems that require verifiable trust across untrusted infrastructure, such as in cloud computing, financial services, or healthcare.
Oak provides a unique combination of hardware-rooted remote attestation, encrypted communication, and a split architecture that minimizes trust in service providers. Its transparent release process and support for multiple TEEs offer verifiable security and flexibility not found in typical confidential computing solutions.
Meaningful control of data in distributed systems.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Leverages TEEs from manufacturers like AMD or Intel to provide cryptographically signed evidence of Enclave Application identity, enabling trust distribution without relying on service providers, as outlined in the Remote Attestation section.
Establishes end-to-end encrypted communication with guaranteed confidentiality, integrity, and authenticity, bound to remote attestation evidence, ensuring secure interactions between nodes.
Uses a split architecture to separate Enclave Applications (in TEEs) from untrusted Host Applications, reducing the attack surface and TCB, as described in the Split Architecture section.
Offers Oak Restricted Kernel for minimal, reviewable TCB and Oak Containers for full Linux compatibility and higher performance, catering to different security and performance trade-offs.
Integrates with verifiable logs like Rekor to publish binary artifacts, preventing undetected backdoors and enabling reproducible builds for external verification.
The README explicitly states that TEEs are vulnerable to side-channel attacks, which Oak cannot fully defend against, requiring additional host security measures and defense-in-depth strategies.
Requires specific TEE hardware (e.g., AMD SEV-SNP, Intel TDX) and involves a multi-stage attestation process with split architecture, increasing deployment complexity and limiting platform flexibility.
Oak Restricted Kernel sacrifices features and performance for minimal TCB, while Oak Containers expand the TCB significantly, making full code review infeasible and complicating security reasoning.
Relies on hardware manufacturers (e.g., AMD, Intel) as roots of trust, which may not align with scenarios requiring vendor-neutral or software-only trust models.