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:

  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.

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

Monitoring Tool

The monitoring tool is an infrastructure in charge of setting up and managing a monitoring component. It is based on event messages and enables the collection of complex events.

Security Testing Tool

GdpR-based cOmbinatOrial Testing (GROOT) is a general combinatorial strategy for testing systems managing GDPR’s concepts (e.g., Data Subject, Personal Data or Controller).

Domain Specific Language

The domain specific language enables specification of digital twin behaviour in a manner that can enable a predicted evaluation of its trustworthy behaviour in a simulated environment

Fail-operation clock synchronization methodology

Synchronization loss can occur due to many reasons, either because of a device or link failure or due to a targeted attack on the reference node, which supplies the corrected time to the network’s nodes.

Time sensitive network simulation

Simulate the real time communication for the distributed based on the Time sensitive network simulation. Additionally, simulate the fail-operation clock synchronization methodology. This simulation will validate the communication stack.

BIECO Project

SUBSCRIBE and become part of the BIECO community!

We don’t spam!

Share This