Activity 1: Compositional Methodology for Security Certification
WP1 "Baseline for compositional evaluation": Partners with security and safety backgrounds summarized existing compositional security regulations/interpretations (D1.1) what tools/ techniques exist (D1.2) how to do compositional certification for an SK-based product (D1.3).
WP2 "Standardisation of MILS integration methodology": We drafted the Base MILS Protection Profile (D2.1) using the Security Target (ST) and evaluated that it meets CC content requirements. We identified potential PP Modules that could be of use for the MILS community for additional functionality (D2.2). We edited the Base PP and PP Modules in parallel due to interdependency. We created templates for a security architecture (D2.3) and guidance for using an SK to build secure CPS systems (D2.4).
Activity 2: MILS Platform Certification
WP3 "MILS platform definition" served for the certification of an SK. We studied how the modular PP of WP2, consisting of a base PP and PP modules, represents this ST. We asked for certification body feedback.
WP4 "MILS platform enhancement" developed a security testing methodology, considering the relevant standards CC and IEC 62443 and fuzzing to discover hard to find vulnerabilities. We implemented a certifiable partitioned network driver with accelerators and described a certifiable MILS design of secure boot and update.
WP5 "MILS platform certification" provided assurance that the MILS SK works as specified in the ST. We reviewed product and development artefacts incl. the ST itself, documentation related to the product life cycle, development and guidance. We did testing and vulnerability analysis and produced evaluation reports for all CC activities.
Activity 3: Certification Pilots
WP6 "Pilot: Smart Grid": For medium-assurance, a pilot was based on Industrial and Automation Control System (IACS) of an electrical substation incl. Remote Terminal Units (RTU). We defined the security scope for the pilot, considering the standards IEC 62443 and CC. A master-slave configuration with control, communication and acquisition RTU devices was implemented. To scale the pilot from medium to high assurance, a compositional security design (with WP2 input) was made. We ported the RTU architecture to PikeOS and evaluated the results according to IEC.
WP7 "Pilot Railway": The use case demonstrator (security gateway) was presented and the railway pilot described. Security requirements based on IEC 62443 for the pilot were defined and the pilot implemented. Evaluation and certification were done for IEC 62443-4-1 and IEC 62443-4-2.
WP8 "Pilot Subway": We specified the HW platform and operational environment of the demonstrator, defined SW components, which must be implemented to create application “T-composition” and defined standards to show the principles and procedures for the implementation, acceptance and subsequent certification, and the pilot was implemented. Evaluation and certification were done for IEC 62443-4-1 and IEC 62443-4-2.
Activity 4: Management, dissemination and exploitation
We created a corporated identity to make certMILS recognisable in conferences, workshops and events. We set up an IT infrastructure, a website, social media and a Zenodo community for public deliverables. We validated our SK protection profile approach by soliciting feedback from SK experts (D9.2). We organized three MILS workshops with proceedings on Zenodo, published several papers incl. joint papers reporting on the consortium’s security certification experience of CPS under CC and IEC 62443 and based on the MILS architecture, and seven newsletters. To compensate for cancelled conferences due to the Covid-19 pandemic in 2020 and 2021, new dissemination activities were carried out. For instance, a podcast series and two videos about certMILS were published. Kick-off, technical and Advisory Board meetings and monthly telcos were held regularly and risk assessment continuously performed.