WP4 – Development of Resilient Systems

 Coordinated by
IESE (M01-M36)


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:

  1. To develop methods and tools that enable runtime evaluation of system operational state in dynamic environments.
  2. 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.
  3. To develop methods that during runtime bring a system into a safe, trusted state, making it resilient to malicious attacks.


  • 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


Fuzzing Tool

Fuzzing Tool will test System Under Test (SUT) security vulnerabilities or inputs not contemplated that could compromise the system; as a black-box process, by using unintended or incorrect inputs and monitoring their corresponding outputs.


This exploitation result consists in cybersecurity consultancy services supported by ResilBlockly (former Blockly4SoS), a Model-Driven Engineering tool that has been developed in the context of BIECO.

Security evaluation methodology

Security evaluation methodology to evaluate the security of an ICT system. The methodology is based on standards such as ISO 31000 standard for Risk Management, the ISO 29119 standard for Security Testing or the MUD standard…

Extended MUD file

The extended Manufacturer Usage Description (MUD) file is an extension of the MUD Internet Engineering Task Force (IETF) standard…

BIECO Project

SUBSCRIBE and become part of the BIECO community!

We don’t spam!

Share This