M24: so what?

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 Requirements

TREDISEC Framework Requirements: dimensions

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:

The 7 key innovation points of TREDISEC

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).

TREDISEC: 10 months later

The TREDISEC project started officially on the 1st of April, 2015. Today, 28th of January 2016, and after 10 months of intense collaboration among security researchers, business technologists and cloud experts, we are proud to say that we are now a step closer towards achieving the project objectives.