The VESSEDIA project has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 731453.
Public RTD Deliverables
D1.1 “Security requirements for connected medium security-critical applications“ [September 2017]
This deliverable reports the general methodology developed in T1.1., in which general guidelines for requirement analyses will be reviewed and particularized with respect to the project scope.
D1.3 “Modelling framework Description“ [June 2018]
This document describes the model-based language resulting from T1.2.
D2.1. “Basic analyzers intermediate release“[June 2018]
Initial version of front-ends and specification libraries, improved analyzers and prototypes of new analyzers.
D3.1 „Methodological report for modular reasoning for system validation and verification“ [June 2018]
This report will contain the methodology about modular reasoning for system validation and verification (task 3.1).
D4.1 “Metrics for VESSEDIA tools in quality assurance“ [June 2018]
In this deliverable, the definition of metrics defined in Task 4.1. are stated and described.
D4.2 “VESSEDIA approach for security evaluation“ [June 2018]
D4.2 includes the analysis on using VESSEDIA results in security evaluation methodologies (Task 4.2).
D1.5 “Analyses choice methodology report” [December 2018]
This report presents the findings of T1.4 “Flexible selection of static analyses” regarding a cost-efficient trade-off between basic and sophisticated analyses.
D1.7 “Vulnerability discovery methodology” [December 2018]
This report presents ways to detect the most common vulnerabilities using Frama-C.
D3.3 “Guidelines for combination of static and dynamic analyses” [December 2018]
This report is the output of task 3.2 and will contain guidelines for combination of static and dynamic analyses.
D3.2 Preliminary version of the platforms [August 2018]
This deliverable will contain the first prototypes of an environment of technologies to enable modular system verifications and of the “verification as a service” (tasks 3.1 and 3.3)