The adaptation layer for cloud computing presented in this deliverable considers a hybrid cloud model used for WITDOM, where the trusted domain relies on a private cloud infrastructures, such as OpenStack, while the untrusted domain benefits from the use of public clouds, such as AmazonWeb Services.
Requirements & Design
This deliverable includes the final scenario-specific architectural description for the use-cases of both WITDOM eHealth and Financial Services scenarios. The document updates and supersedes the previous version of the deliverable D4.3. The document first revises the generic architecture as presented in Deliverable D4.2, and discusses how this architecture fulfills the needs of both WITDOM scenarios, eHealth and Financial Services.
The architectural work package of WITDOM develops a flexible end-to-end secure architecturewhich forms the basis for securing use-case applications. The description of the generic architecture for processing data in untrusted domains, presented in this report, defines each component of the architecture, their responsibilities, interfaces, security properties, and dependencies with other components.
This revision of Deliverable D3.1 presents the discussion on the formal technological security, privacy and verifiability requirements of WITDOM platform and scenarios, taking into account the connection with user-centric requirements and European privacy and data protection legislation.
The requirements for the WITDOM platform and the genomic and financial scenarios are classified into three categories (core research requirements, demo requirements and production requirements), according to the advancein SoTA that they convey in WITDOM.
The deliverable D2.2 provides a list of functional requirements and a list of use-cases for the both project scenarios: eHealth and Financial Services.
In addition to the required output, this document reports as well on the requirement elicitation process carried out by the consortium.
It includes the description of the methodology SPACE (Security and PrivAcy CodEsign) used for eliciting privacy and security requirements, an analysis of the two application scenarios (namely eHealth and Financial Services) in which the WITDOM platform will be instantiated in future stages of the project, a thorough review of the applicable security and privacy standards, a study of the scenario-specific cloud computing needs and a schematic list of the security and privacy high-level requirements for the application scenarios.