Enabler placement and interactions. The service Orchestrator within the service management domain (see Figure 16) can ask the RA module to run a deep attestation validation on a designated network node. Before that, it can check if the target is RA compliant or request the list of the available and RA-active network nodes. The service Orchestrator can also ask to clean up a give network node from all the data and software related to RA. Finally, the service orchestrator has two options: (i) it gets the result of the RA module and analyses it by its own means and data or (ii) ask the RA module to analyse the results. The second option implies that the RA module has the necessary data to make the analysis (Given by the service Orchestrator, or retrieved on the network from, e.g., Security Data collector, Decision engine, Data services). Figure 16 RA placement in INSPIRE-5Gplus HLA
Enabler placement and interactions. The MANIFEST is a document which will be consumed by INSPIRE-5Gplus Policy & SSLA management module as shown in Figure 22. The MANIFEST Class will be managed in the Policy and SSLA Management and interact with the Security Orchestration and Discovery tool. The specific MANIFEST instance will be embedded in the Trust Management by the Security Orchestration. The MANIFEST instance will be developed in the context of T4.4 because it contains observations made by the INSPIRE-5Gplus. For inter-domain operation, this structure will be replicated following the component design pattern. Figure 22 MANIFEST placement in INSPIRE-5Gplus HLA
Enabler placement and interactions. 5.1.1.1 Potential interactions with HLA components Figure 18 ďĞůŽǁ ƐŚŽǁƐ ƚŚĞ ŵŽƐƚ ƌĞůĞǀĂŶƚ ƉůĂĐĞŵĞŶƚ ŽĨ level architecture. For clarity, the figure is a partial view of the complete HLA. The light blue areas represent the main areas of interactions of Systemic: security orchestration, trust management and Service management. As part of the Trust management area itself, Systemic may be interfaced with the other components inside the block but we have not set the linking arrows inside the block for clarity. The dark blue components are potential recipients or emitters of requests and data transfers to Systemic. The relevance and reality of each links are not yet defined at the time of writing of this deliverable and will be defined before the Project termination.
Enabler placement and interactions. The Policy & SSLA management can enforce the execution of the PoT validations on the network (e.g., regulations, SLA, etc.) towards the trust management component of PoT controller. Also, the PoT controller can obtain a vision of the nodes involved from the Security orchestrator (alternatively, from the service Management Domain). The enforcement policy will mandate monitoring the packets. The PoT controller will enforce the specific configuration, using the IETF draft specification [1] against the security agents in the nodes assigned. Once the policy is active, the alerts will be collected by the PoT controller deliver to each Trust Management Domain so that it can evaluate this information in terms of trust or reputation and integrate with the E2E Trust management.
Enabler placement and interactions. Figure 23: eTRM placement in INSPIRE-5Gplus HLA The eTRM is located inside the Trust Management module and inside the Security Management Domain (Figure 23). The eTRM interacts with the rest of the elements and modules inside the INSPIRE- 5Gplus architecture as follows:
Enabler placement and interactions. The TRM enabler will interact, through the Integration Fabric mostly via pub/sub services, with the entities from which it has to obtain data (to calculate the trust value), such as SSLAs and Security Data Collector as well as with E2E Trust Manager and with the Blockchain (Xxxxxxx). The latter is required to calculate the requested trust value, as it is obtained from the execution of a Smart Contract. The ĞŶĂďůĞƌ͛Ɛ ŽďƚĂŝŶĞcoĚm puǀteĂd tůrusƵt sĞcoƐre͕s w illĂbeƐst orǁedĞinůa ůda tabĂasƐe f orƚfuŚrthĞer historical post-processing. To get the needed parameters to compute the trust, the process defined below comprises all the involved parties. As an example, we will describe the interaction (through the Integration Fabric) with the PoT (Proof of Transit) enabler, but the same procedure must be carried out by any other enabler when providing their specific information to the TRM. Interaction between TRM and PoT (valid for any enabler), this process is depicted also in Figure 27:
