1 Executive Summary
CHARIOT Project envisions a holistic approach to the problems related to security, safety supervision and privacy in industrial IoT (Internet of Things) deployments. For this goal CHARIOT IPSE (IoT Privacy Safety Supervision Privacy and Security Engine) offers several cognitive capabilities on different parts of the CHARIOT architecture to handle these issues. CHARIOT IPSE is designed by considering the requirements of the three living labs in the CHARIOT Consortium.

In the preliminary design version of this document (D3.1), we reported the first phase of the design specifications of CHARIOT. All the technical components and their respective functional and non-functional requirements have been reported where functional requirements consist of the main functionalities of the engines and nonfunctional requirements highlight the quality and operation attributes of the system. The requirements were used by the Work Package 3 Partners to generate the high-level technical specifications of the component. Furthermore, interface definitions were presented, and several use cases and scenarios were highlighted.
In this final design version of the document, a project-wide consolidated requirements’ document and the rescoping document written after the mid-term review has been taken into consideration and reflected to the design and implementation of IPSE. In this, all revised or updated requirements were taken into account to reflect any updated requirements or design considerations. This has led to the final version of the deliverable as the IPSE final design.

CHARIOT IPSE functionality can be listed briefly as follows: CHARIOT Safety Supervision Engine is used to observe and share the system topology across Fog computation components and enforce rule based or machine learning based safety supervision policies across the industrial IoT setup. On top of this, safety supervision engine can be used to optimize the system signal rate under normal and emergency conditions. CHARIOT Privacy Engine ensures privacy by design by handling the encryption policies for data within CHARIOT. CHARIOT Security Engine processes firmware binary updates and identifies the security vulnerabilities of the firmware. We updated the requirements of the security engine considerably to align with the changes in task 3.3 documented in the project
amendment in Month 15. IoTL is the language used to define the state of the relevant industrial IoT setup and a web server that listens to state transfers from relevant nodes in the Fog network. Finally CHARIOT Dashboard integrates with the CHARIOT engines to provide reporting, configuration and visualization functionality for the engines.

The purpose of this deliverable is sharing the finalized design version of the CHARIOT IPSE design as CHARIOT D3.6. In this context, we share our output to align with work package 2 and work package 4 of CHARIOT Project, coordinate the partners’ effort on IPSE and to guide further development and innovation goals related to IPSE.
We deployed the IPSE to the three living labs in accordance with the requirements in this document and demonstrated its use in IBM LL in Dublin in the mid-term review. The document involves contributions from all WP3 partners and in particular WP2-3-4 task leaders of the CHARIOT Project.