WP4 – Development of Resilient Systems
Coordinated by
IESE (M01-M36)
Objective
In this WP, tools and methods will be developed for supporting creation of resilient systems w.r.t security attacks and vulnerabilities. The scope is to develop systems that can cope with behavior disturbances caused by malicious attacks, that manifest into a loss of control and can bring a system into hazardous situations. A resilient system shall be able to compensate for interruptions and get back into a safe state in case of emergency situations caused by malicious attacks. In this regard the system shall be able to autonomously and automatically construct awareness of its security in a dynamic environment, to recognize critical situations and to identify the right operational mode for remaining into a secure and trusted operational state.
Concretely, this work package has the following objectives:
- To develop methods and tools that enable runtime evaluation of system operational state in dynamic environments.
- To enhance existing tools that can predict failure propagation caused by malicious attacks and support the transition of an ICT system into a resilient state. Prediction is performed in a simulated environment by counteracting the capabilities of the system under evaluation to detect that it is under evaluation.
- To develop methods that during runtime bring a system into a safe, trusted state, making it resilient to malicious attacks.
Deliverables
- D4.1 Report on Self-checking of vulnerabilities and failures WP4 (7 – RESILTECH) Report Confidential, only for members of the consortium (including the Commission Services) M30
- D4.2 Report on methods and tools for the failure prediction WP4 (2 – Fraunhofer) Report Confidential, only for members of the consortium (including the Commission Services) M24
- D4.3 Report on Method development for resilient systems WP4 (2 – Fraunhofer) Report Confidential, only for members of the consortium (including the Commission Services) M30
Outcomes
WP6 monthly meeting M7
The 1st March took place the WP6 monthly meeting. IESE presented their tool called SafeTbox and they introduced the Conditional Safety Certificates (ConSerts). During this monthly meeting, IESE presented their tool called safeTbox, a tool for modelling and safety...
WP6 monthly meeting M6
The 1st February took place the WP6 monthly meeting. During the meeting it was presented ResilBlockly, the new refactored and extended version of the Blockly4SoS tool. The main focus of this call was on the presentation of Blockly4SoS and on the live demo of the new...
WP6 monthly meeting M5
The 11th January took place the WP6 monthly meeting. Resiltech shared a document with requirements for the extension of Blockly4SoS. It has also been decided that MUD files will be an input of the modelling activities. Resiltech shared a document with requirements for...
WP6 Monthly meeting M4
The 7th December took place the WP6 monthly meeting. The partners discussed about the preliminary results of tasks T6.1 and T6.2. During the meeting, the partners discussed about the preliminary results of tasks T6.1 and T6.2, shared by Resiltech, leader of the two...
Bieco WP5 – Kick Off meeting
On 2th December 2020, we had a remote Kickoff Meeting for WP5 of the European cybersecurity project @bieco_org. It was a great meeting with participants from Portugal, Germany, Italy, Romania, Spain, Austria and Poland. Due to COVID-19 situation, the meeting was held...
Kick-Off meeting of WP4
On 12th of November, we had the internal Kick-Off meeting of WP4, led by Fraunhofer IESE. Within WP4, methods and tools are developed for assuring system resilience based on runtime evaluation of (Software) component behaviours. Specifically, in a runtime...
