The security objective is set to reduce the security risks as much as possible by defining security functions and enablers. This document, D4.2, builds upon the security functions, mechanisms, and techniques that are described in D4.1 [D4.1] and provides their further developments within WP4 to meet the requirements enabling more secure and reliable networks than those that we have today. These functions, mechanisms and techniques include the Authentication, Access Controls (Capability-Based Access Control and Multi-Level Security) Cryptographic function, Key Management and Resiliency aspects of security. The deliverable overall provides the relevant specifications and analysis, the design aspects, Proof of Concept implementations (PoC), and related PoC tests.
Given the guidelines stated in the introduction section of this deliverable, therefore, in the following sections of the deliverable we provide, to a certain extent, the description of the following aspects in relation to all of the security functions specified above:
- The scenarios for application of specified security functions/enablers
- The specification of relevant functions and their designs into modular components
- The software architecture block and sequence diagrams
- The relevant policies to realise the functionality of each security component
- The interfaces and interactions with other components
- The code and configuration of components
- The implementation and realisation of components for PoC experimentation purposes
- Identification of tests to be conducted for PoC
- Component-level PoC tests conducted in-house at each partner’s premises and the results obtained.
Future directions are also specified to further the work in each of the activities within the WP4 tasks and to provide the implemented security functions and enablers for integration and tests to WP6. Given the above aspects, we tried to build the case for “ease of use” and “ease of configuration” of security components for their installation and integration in WP6 scenarios.