LibSEAL

Abstract

Users of online services such as messaging, code hosting and collaborative document editing expect the services to uphold the integrity of their data. Despite providers' best efforts, data corruption still occurs, but at present service integrity violations are excluded from SLAs. For providers to include such violations as part of SLAs, the competing requirements of clients and providers must be satisfied. Clients need the ability to independently identify and prove service integrity violations to claim compensation. At the same time, providers must be able to refute spurious claims.We describe LibSEAL, a SEcure Audit Library for Internet services that creates a non-repudiable audit log of service operations and checks invariants to discover violations of service integrity. LibSEAL is a drop-in replacement for TLS libraries used by services, and thus observes and logs all service requests and responses. It runs inside a trusted execution environment, such as Intel SGX, to protect the integrity of the audit log. Logs are stored using an embedded relational database, permitting service invariant violations to be discovered using simple SQL queries. We evaluate LibSEAL with three popular online services (Git, ownCloud and Dropbox) and demonstrate that it is effective in discovering integrity violations, while reducing throughput by at most 14%.

Secure end-to-end processing of smart metering data

“…In order to protect the confidentiality and authenticity of objects stored in the KVS, a microservice was added in front of our REST API. We refer to it as the TLS interceptor which is based on TaLoS [14], our library for building applications that support TLS connection termination inside enclaves. This interception service has the role of intermediating the connection between applications and storage components, handling the HTTPS requests inside the enclaves and encrypting the data that is written to the KVS.…”

Managing confidentiality leaks through private algorithms on Software Guard eXtensions (SGX) enclaves

“…The novelty of our work is as follows: 1 we consider mutually distrustful entities (HO, DO, AO) with conflicting interests in the cloud, 2 we differentiate the private algorithms and the private data, 3 we show the bad practices on use of TEE in the cloud, 4 we create a taxonomy for secure execution of private algorithms in untrusted remote environments, 5 we provide practical insights to enclave development, 6 we perform a security analysis on existing dynamic code loaders with interpreter enclaves, and 7 we evaluate our execution model in three adversarial settings in the cloud.…”

“…The Horizon2020 funded research projects under SERECA 3 focus on a number of goals to build secure enclaves. These goals include application partitioning [36], trusted architectures for web services [8,33], container architecture [3] and library support for unmodified applications (SGX-LKL 4 ), better integrity [5] and isolation [7], and enclave memory safety [35] in the cloud.…”

“…European Commission funded several projects on TEE research under SecureCloud (TRUSTEE) 5 . The main direction of TRUSTEE projects is dependability in the cloud.…”

“…The key point is that neither the DO nor the enclave can change the execution after this stage. 5 The result of the computation is returned to the DO.…”