Open Enclave SDK

The SDK normalizes the attestation process across disparate TEE implementations through a consistent evidence and endorsement framework. Rather than requiring developers to handle Intel's EPID/DCAP or AMD's SEV-SNP attestation report formats separately, Open Enclave provides a single oe_get_evidence() API. This function collects hardware-specific claims, formats them according to standard IETF RATS conventions, and enables verification against a pluggable verifier plugin. The unified model supports both local attestation between enclaves on the same platform and remote attestation to external relying parties, simplifying the integration of confidential computing into existing identity and access management systems.

Open Enclave provides a restricted but familiar libc-compatible runtime inside the enclave boundary, supporting a subset of standard C library functions. This includes:

• Memory allocation with malloc/free operating on enclave-private heaps
• String manipulation and formatted I/O via snprintf
• Cryptographic operations through a built-in OpenSSL integration compiled for the enclave environment
• Threading primitives with mutexes and condition variables for multi-threaded enclave applications The runtime deliberately excludes system calls that would require host OS interaction, enforcing the security boundary while minimizing the learning curve for developers accustomed to standard programming models.

Communication between the untrusted host application and the trusted enclave is defined through an Enclave Definition Language file. The EDL declares:

• Trusted functions (ecalls): Entry points the host calls into the enclave
• Untrusted functions (ocalls): Exit points where the enclave calls back to the host for necessary OS services like file I/O or networking
• Data marshaling: Automatic serialization of complex structures across the trust boundary The oeedger8r tool processes EDL files at build time, generating proxy and bridge code that handles context switching, parameter deep-copying, and boundary validation. This formal interface contract prevents arbitrary memory access across the trust boundary and serves as a security audit point.

The SDK abstracts data protection primitives through a pluggable sealing API. The oe_seal_data() and oe_unseal_data() functions encrypt data for persistent storage, binding it to the enclave's identity or signing key depending on the sealing policy. The underlying encryption can leverage hardware-derived keys unique to each TEE platform. Additionally, Open Enclave integrates a crypto plugin framework that allows swapping between software-based cryptographic libraries and hardware-accelerated implementations available within specific TEEs. This ensures that sealing operations benefit from the strongest available root of trust without application-level code changes.

Open Enclave uses CMake with integrated toolchain files to manage cross-compilation for multiple TEE targets from a single build configuration. The SDK ships with:

• SGX toolchain leveraging Intel's SDK for enclave signing and page table management
• OP-TEE toolchain for ARM TrustZone-based enclaves on embedded and IoT devices
• Experimental backends for emerging TEE architectures Build artifacts include a signed enclave shared library, a host executable, and an optional enclave configuration file specifying stack size, heap size, and thread count. The build system also supports simulation mode, allowing developers to test enclave logic on workstations without TEE hardware, dramatically accelerating the development cycle.