D7.7. Business Models for TREDISEC

In order to generate revenue within the EU economic area, the consortium has identified business models that will sustain the outcome of the TREDISEC project in terms of business benefits and potential triggers for markets. This document describes the relevant customer segments, depending on their needs, focusing on the sectors with a higher risk of attack (and thus, more interested in improving their systems), and the best way to approach them. We have identified two main channels to reach potential customers: an online channel for reaching users with a technical profile and “turn” them into influencers inside their companies; and a field sales force for reaching larger companies that require customization.
The proposed business model advocates the project deliverables via a unified Framework, which is able to integrate (or “glue together”) all the Security Primitives developed by the project partners.
Following this business model proposal, a “freely” available Framework does not imply that there is no benefit from it. There are numerous ways in which TREDISEC can benefit from the Framework; For example, almost certainly, the Framework will need customization for different installations. So, there will be considerable need for consultancy, maintenance and customization work to be done.

D6.2. Evaluation criteria

In this deliverable we describe the methodologies that we plan to use in order to evaluate the outcomes of TREDISEC. We present our approach to assess whether the results of the project fulfil the requirements and necessities of the use cases, identified in deliverable D2.1 “Description of the context scenarios and use cases definition”, and to measure to what extent these requirements are met.
TREDISEC has two major technological outcomes: the TREDISEC Framework and the security primitives. In our approach, we perform the assessment of the maturity level of these results by deploying the TREDISEC Framework and security primitives in the use cases of the project and other internal testing environments.
Along the evaluation process we will validate compliance to the requirements identified in WP2 (cf. D2.2 “Requirements Analysis and Consolidation” ), and assess the degree of enhancement brought by the TREDISEC technological outcomes in each use case. On one side, we will evaluate the overall project success by concluding whether the objectives have been achieved. In this case, we refer to the evaluation criteria defined by all the use case owners and the framework owners. On the other side, we evaluate the TREDISEC technological outcomes, i.e. the framework and the security primitives, by deploying them in the use cases and using the corresponding indicators to perform measurements.
In order to homogenise the different evaluations, we have defined two different types of domain-specific indicators to evaluate TREDISEC technologies: use case process indicator, which focuses on the process described in each use case; and technology-related indicators, which focuses on functional and non-functional characteristics of the technologies developed. For each of the objectives a success criterion is defined together with the measurement methodologies.
Notice that for all use cases and the framework, the focus areas to be evaluated along the processes and requirements fulfilment are defined in detail by all use case and framework owners.

D4.4. A proposal for secure enforcement of policies in the Cloud

Cloud systems are a great platform for collaboration and shared resource usage. However, such cloud systems can only be successful if they securely enforce policies in the cloud, as they otherwise put users’ data at risk. During the course of this deliverable we will present three contributions targeted at providing a better enforcement of cloud policies.
We present the implementation of the TREDISEC security primitive Access Control for Multi-tenancy that was outlined as part of deliverable D4.1. Multi-tenancy makes cloud systems attractive for both customers and providers due to the lower costs. However, such systems also require special care in terms of access control as tenants have to be securely separated from each other.
We also present a novel technique aimed at enhancing the collaboration on cloud storage for group members, e.g. a set of employees. Such members want to use collaboratively-accessible cloud storage, but due to data protection regulation they also need secure deletion in order to protect customer privacy and data security.
Finally, we outline a new instantiation of interaction for multiple distrusting parties that want to make shared access control decisions on a shared cloud repository. Our system prevents a single party from monopolizing the access control decisions, but in contrast provides an efficient way for collaborative access control decisions for cloud storage using blockchain technologies.

D1.6. Innovation Management Report

The goal of this document is to outline the current progress of the TREDISEC project from the point of view of Innovation Management activities. Recall that the main purpose of innovation management is to ensure that the project research activities, technological developments, and achievements, are kept well connected to outside technology developments. An additional goal of innovation management here is to maintain low risk level for the project and to prevent the project results from losing relevance given the evolving trends in the market.

D7.4. First Dissemination and Communication activities reporting

This 1st Dissemination and Communication Activities report collects all the set of activities developed along the 1st year of the project (M01 – M12), using the selected means described in D7.2 and D7.3, and to evaluate if the progress reached to achieve dissemination and communication goals is satisfactory.
Additionally, the section “Next Steps” describes the schedule for the diffusion of the project along the 2nd year.

D5.2. Optimization of outsourcing activities and initial design of privacy preserving data processing primitives

This deliverable will provide a tool set to optimize the actual outsourcing process, by for example, parallelizing encryption before outsourcing data to the cloud. In this context, we introduce an initial design of privacy preserving primitives for data processing. This deliverable will also comprise the complete design and evaluation of privacy preserving data processing primitives.

D4.1. A Proposal for Access Control Models for Multitenancy

This deliverable will assess current approaches for access control and propose novel models, based on current progress in ABAC models, to cope with multi-tenancy requirements and in particular with distributed attributes.
A mapping between these ABAC-based models to enforceable policy languages (e.g. XACML) will be proposed, including the design of an enforcement component to parse, interpret and execute access control policies.