Deliverables

This report presents the three CUREX use cases that both highlight and set the means to derive the user requirements of the CUREX platform. More specifically, firstly the different CUREX stakeholders (e.g. patients, medical professionals) are presented. Then the use cases are described along with their scenarios to be supported. A key part of the report is the collection the requirements of the stakeholders, which are obtained through standard techniques employed to extract knowledge from domain experts. These requirements will fuel next project activities regarding the system design. Then, key performance indicators (KPIs) are devised (based on the specified requirements) to create a set of measurable goals for the platform validation in subsequent project phases. In summary, the use case descriptions and the requirements specification in this deliverable trigger the CUREX agile and iterative development approach to meeting the project objectives.

 

This document aims at presenting the reference architecture that has been designed for the CUREX solution. The process to build the CUREX reference architecture followed an incremental analysis process that started from the general requirements presented in the Description of Action and continued with the use cases and requirements performed in D2.1. Deliverable D2.2 will be used by all CUREX partners as the baseline for the design and development of all CUREX components and will provide the guidelines to integrate the CUREX toolkit with the Private blockchain, the end-users and their corresponding applications, into a unified secured platform for the risk assessment of health data exchange.

 

This document describes the design and implementation of the Asset Discovery Tool (ADT), which is part of the CUREX architecture. It presents the state of the art in the field of asset discovery and other technologies that will be used in the development, the main characteristics of the tool, its internal architecture and the detailed description of each of its components. Moreover, the document presents the ADT in the context of CUREX, its interactions with other tools and in the CUREX uses cases.

 

This  document  describes  the  conceptual  and  physical  design  and  implementation  of  the Knowledge Extraction  Analytics  (KEA)  component  of  the  CUREX  platform.  It  presents  its  main  functionalities,  the reference architectures and the constituent analytics techniques. The detailed analysis of the architecture aims  to  reveal  all  the  interconnections  between  the  KEA  component  and  the  other  CUREX  platform components, such as the Threat Intelligence Engine component that will eventually encompass KEA. An additional objective of this document is to design and implement specific methods for detecting threats, identifying threat patterns and predicting possible threatstailored to the CUREX setting.This deliverable plays  a  key  role  in  the  CUREX  platform  architecture,  as  it  comprises  complementary  techniques  for vulnerability  analysis  in  T3.3/D3.3  (Vulnerability  Discovery  Manager  component),  through  providing threat patterns. Also, the analytics performed in the context of KEA will be complemented by the work to be performed in T3.4/D3.4 (TIE component). Finally, KEA receives input from both ADT (T3.1/D3.1) and TIE. All these interactions are explained in detail.

 

This document presents definitions of the main concepts and technical aspects related to the vulnerability analysis methods and practices. It provides details on the six main phases of any vulnerability management process (preparation, scanning, discovery, analysis, remediation and verification), and presents useful and up-to-date information about the healthcare ecosystems in terms of vulnerabilities, highlighting the main risks and challenges to which healthcare organizations are currently exposed, as well as available solutions to face them.

 

This deliverable constitutes a report on the activities performed in the context of task T3.4, entitled “Threat Intelligence Engine”. Its purpose it to present the CUREX Threat Intelligence Engine (TIE), which is the tool responsible for delivering threat intelligence functionalities within the CUREX architecture.

 

This report presents the design specifications for CUREX’s Private Blockchain. A blockchain technology overview and a review on the current state of the art for solutions in the permissioned setting are presented first. Based on it and the results from Task 2.1 (D2.1 Use cases and requirements) the requirements for the CUREX’s Private Blockchain are then presented. Additionally, more fine-grained information from the MyHealthMyData (MHMD) blockchain is included in a separate section to assist and complement the information already presented in deliverable D2.1. The aim here is to help guide the decisions for future work on implementation and integration within both blockchains. In summary, the technology selection and rationale behind the CUREX’s Private Blockchain design are introduced.

logo_inverse

is loading the page...