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

WP5 meeting

In the meetings of November, the members of WP5 have fine-tuned the user interaction with the Auditing Component, part of the BIECO framework. Demo’s preparation is progressing with benefits from profitable and interesting discussions between WP5 members. Taking...

Presentation of BIECO’s project report at ICTSS21

Presentation of BIECO’s project report at ICTSS21

the 33rd IFIP International Conference on Testing Software and Systems (ICTSS)On 11th of November, Ricardo Silva Peres from UNINOVA presented a summary of WP2 in the Project Report of BIECO titled „The BIECO Conceptual Framework Towards Security and Trust in ICT...

NIST Bug Framework – BIECO taxonomy Sync

NIST Bug Framework – BIECO taxonomy Sync

On 16th of November we‘ve had the honour to synchronize on WP4 research activities with experts from NIST, INMETRO and Ericsson. Productive discussions with Irena Bojanova (NIST: https://www.nist.gov/people/irena-bojanova ), Carlos Galhardo (INMETRO...

WP5 – Specification of the check Trajectory

WP5 – Specification of the check Trajectory

On 17th of Nov. we have deepened the specification of the check Trajectory function within the local planner of the robotic use case. This step brings us further towards creation of horizontal abstraction for the digital twin creation.

WP4 meeting

WP4 meeting

BIECO WP4Within WP4 today we have explored the extent to which the ICT GW Use Case developed by RESILTECH within Net2DG project can accommodate runtime downloads of new functionalities and/or runtime..

BIECO Project

SUBSCRIBE and become part of the BIECO community!

We don’t spam!

Share This