System Architecture Design

pSHIELDSystem Architecture DesignPU5 SPD RequirementsArchitecture is one of the structural characteristics of pSHIELD. The process for the definition of aconceptual formalized architectural framework demands as inputs a set of requirements, which are ofseveral types or simply express different system needs and priorities. We assign the term “SystemRequirements” in the collection concerning the overall design. This can be further decomposed inattributes independent of the application or reflecting the specific scenario needs. We aim at defining theSPD functionalities, which will be potentially possessed by a pSHIELD implementation, in order to serveits objective, being for example, the protection of asset and material in the railway transportation usecase. These requirements pave the way for the design and development of pSHIELD Architecture,synthesized by the four pSHIELD layers of node, network, middleware and overlay.Out of the broad list of D2.1, “System requirements and specifications”, we refer here to theserequirements, which relate, to a bigger or lesser extent, with the impact of specific SPD desired attributes,metrics and functionalities, in the formulation of the system architecture. Before that, an epigrammaticreminder of the three components comprising SPD concept and their meaning in the technologicalframework in pSHIELD follows.Security in the context of telecommunications and ESs is the resultant of three properties: confidentiality,integrity and availability. Their synthesis represents the discipline of protecting software and hardwareagainst attacks conducted by unauthorized interceptors.Apart from the apparent, colloquial meaning, Privacy, expanded respectively in communication theory, isthe seclusion or selective revelation of wire, oral or electronic communication while in transmission.Usually privacy is a notion broader than security. In pSHIELD, in expectation of an improved specificationof the term (probably through the application scenario use case), privacy can be a complementary andinterrelated term to security and more specifically, confidentiality.Even broader and multi-faceted is Dependability, a notion arriving in telecommunications from systemengineering and encompassing the reliability and trustworthiness of a system or network. As mentioned inD2.1, in pSHIELD, Dependability embraces the meaning of availability, reliability, safety, integrity andmaintainability.The description of each requirement is accompanied by the code with which it can be found (itself or a setof similar phrased ones) in D2.1. Either these requirements are tightly connected to architecturalcharacteristics or they imply features and functionalities dependent on the development of the architectureproposal.5.1 System Architecture Security RequirementsAvailabilityThe attribute concerns availability of information, node, network and system, for authorized users (0301,01003, 01014).IntegrityOf data (network layer), against unauthorized access, mechanisms based on hardware “hooks” andsecure key installation, protection of the TPM, integrity at node layer (0302, 06004, 01002, 01004, 01012,01015).PUD2.3.2Issue 5 Page 62 of 122