5.3 - Report describing the security architecture and framework
Lead partner:
Due month:
30
Status:
Completed
Description:
This deliverable report describes the security architecture and framework of BioMedBridges. Deliverable 5.3 is based on three Work Tasks (WTs): WT 5, Security requirements for an e-infrastructure addressing the use cases, WT6, Threat and risk analysis for sharing data or biomaterials, and, particularly, WT7, Design of the security architecture and framework. Deliverable 5.3 also lays the groundwork for WT8, Implementation of a pilot for the security framework. Deliverable 5.3 builds upon the previous deliverables 5.1 [1] and 5.2 [2], and one of its central elements has been cooperation with other Work Packages (WPs). In order to better understand the security requirements and threats, close contacts were established with all Use Case (UC) work packages, i.e. WPs 6-10, and with the other construction work packages, especially WP4 Technical integration. Contacts to WP11 e-advisory task force also established a connection beyond BioMedBridges to external partners, including the European Grid Infrastructure. This report covers a complete series of steps from requirements (identified by means of the two surveys and based upon requirement clusters that are explained in the report to deliverable 5.1) to data flow diagrams and threats (constructed from results of the second survey) to risks, further to countermeasures, and finally towards the architectural elements of the proposed security framework. An important characteristic of the security architecture described here is its bottom-up development. As presented in section 9, process elements and descriptions are based on feedback from the research infrastructures and the use case work packages. Specifications in the form of activity diagrams (deliverable 5.1) and data flow diagrams (this deliverable report) were developed in direct interaction with representatives of the use case work packages. Domain specific (EGA) and domain independent (EGI) experience was sought for the definition of security specific process elements.
Tool/service links:
