EPICA (Efficient and Privacy-respectful Interoperable Cloud-based Authorization) is a software implementation that controls access to resources (either services or data) in multi-tenant cloud environments. EPICA supports an ABAC-based model that extends XACML policies to represent trust relationships between tenants (so called “tenant-aware XACML policies”) in order to govern cross-tenant access to shared cloud resources.
The second primitive chosen to illustrate the results obtained along TREDISEC project in our corporate blog is Secure Data Migration service.
Our Secure Data Migration Service allows companies to securely outsource databases such as those used by enterprise resource planning software into the cloud. All sensitive data is stored encrypted in the cloud and all keying material for decryption is kept solely at the company. Despite encryption, our solution preserves the ability to execute arbitrary database queries.
We start this series of articles about the primitives developed in TREDISEC project with Secure Deletion.
The key feature of the Secure Deletion primitive is to allow users to retain more control over their data. Once a user decides to securely delete data, it is irrecoverably deleted. Thereby, secure deletion provides privacy and compliance with existing data retention laws. We provide a new multi-user secure deletion solution.
Cloud computing has changed both business and everyday life, that’s a fact. Its technological capabilities offer numerous opportunities to cut costs, drive business innovation, and enable new consumer services. On the other hand, a successful attack to critical cloud services, which might slow-down or interrupt services as well as leave data in-flight or at-rest completely exposed to non-authorized parties, could derive into contractual obligations or regulatory compliance violation, resulting in reputation, financial loss, and ultimately, even loss of lives in the case of health or defence critical systems. And suffering such an attack is not an unlikely possibility at all. Not anymore.
March 2017 means M24 in our project timeline terminology. We have submitted four new deliverables and the second year of the project is over. So what?
So... many things really!
If you have been disconnected from latest project news, here's a few of them that you must become acquainted with:
TREDISEC aims at providing a set of security primitives that will ensure the confidentiality and integrity of the outsourced data and computations to the cloud. To help with the design of these primitives, towards the end of December 2015, we have identified the different TREDISEC requirements ranging from functional prerequisites to specific security and privacy needs. With this aim, the following methodology has been applied:
Most existing cloud security solutions are not well-suited in the market because they either provide security at the expense of the economy of scale and cost effectiveness of the cloud (e.g. data is encrypted before being outsourced, which prevents any computation to be performed in the cloud), or they meet the latter objectives at the expense of security (e.g., data deduplication and compression optimally use the resources of the cloud provider but require the customer to blindly trust its cloud provider).
We are living a fascinating moment in what concerns Security in the Cloud, and we would like to share it with you.