Efficiency factors. Our protocol consists in a cryptographic protocol using data from trust anchors (i.e., TPM (Trusted Platform Module) and vTPM (Virtual TPM)). The result of the protocol is a quote. The verification of the quote gives a Boolean (True, if the quote is valid, False, if the quote is invalid). We will prove the security of the cryptographic protocol using game-based proofs.
Efficiency factors. Our goal is to provide a manifest which: ● Identifies the actors which take a responsibility in the lifecycle of the Component ● Expresses the properties that can be expected from the Component ● Expresses the constraints that the user is expected to apply in order to use the Component in a way that avoids security or performance issues, ● Expresses the operational constraints that a user may choose to apply to the Component in order to take into account a specific context linked to the infrastructure where the Component is integrated ● Demonstrates the authenticity of the claims made by authors. In particular, it is necessary to ensure the integrity of the assertion and to authenticate its author in order to materialize its commitment to the claim. ● Can be used generically for any component of the 5G ecosystem ● Is modular to evolve at each step of its lifecycle and allow multiple stakeholders to take commitments independently. Another way to evaluate efficiency of MANIFEST will be potential and demonstrable interaction between MANIFEST structures and other enablers of the project, in particular RCAs and RAG enablers for WP4. Table 5 Comparison of MANIFEST with other manifests Criteria VNFD NSD MUD profile MANIFEST Identify actors Express properties Express usage constraints — Express operational limitations — — — Authenticity of claims — — — Genericity — — — Modularity In Table 5, the black square represents a feature supported by the manifest, the empty square represents a partially supported feature and — means it is not covered. As can be seen in our comparison, only our MANIFEST meets all the above criteria.
Efficiency factors. The efficiency of the solution derives from the three different efficiency factors listed below. Our evaluation of the efficiency factor in written in blue uppercase letters:
Efficiency factors. The security policy can establish the expected level of efficiency. The trust reference value for the PoT enabler will be the event message contents related to the verification status of each node involved in the monitored topology. Additionally, if verification fails at the final node, that means that a node has been avoided or bypassed, a specific alert is generated. This process will be customized in verification frequency and number of nodes to be verified. Additionally, it is worth to mention that the algorithms used, Shamir͛s Secret Sharing Scheme (SSS) [3], achieves information-theoretic security i.e., it cannot be broken by an attacker even with unlimited computing power. Nonetheless, wrong implementations or insecure channels between Controller and nodes could be exploited.
Efficiency factors. The goal of this enabler is to reduce or increase the level of trust and reputation in a networking domain based on the probability of faults (provided by an RCA block that will be described in D4.3). The efficiency of this enabler to compute the right values of reputation can be potentially measured by verifying that the following rules are always met: x When the probability of fault of any networked element is neutral (around 0.5) its reputation becomes near zero as an intent to stay neutral regarding that network element. x When probability of fault increases significantly, its reputation value should plummet to zero. x When probability of fault drops below a certain threshold, its reputation value should increase but in a controlled way, as reputation must be very easy to lose but very difficult to earn. Figure 14 shows how the reputation model should evolve over time. Only one sample of fault probability is needed to plummet reputation score to zero, while several positive probability of fault values (e.g., <0.3) are required to increase its reputation score. This increasing will be proportional to the number of consecutive positive samples 1, 2, and 3 provided as example. Figure 14: Example on how individual reputation values are updated over time Figure 14 describes the reputation model envisioned for our enabler. In case of any network degradation leading to high probability faults, the reputation value should quickly decrease to zero.
Efficiency factors. The evaluation of the trustworthiness properties for a component will give a first idea regarding its capacity to be resilient for different attacks. As the properties will be evaluated with metrics, the DTwC will give a score for each property. Depending on the SSLA requested by the 5G provider, CCT can help by selecting the most appropriate component for the requested SSLA.
Efficiency factors. The values obtained by the Smart Contract (the trust and reliability score) can be used as an indicator of the success of the Trust Manager. The required time to obtain the trust score can be also used as a metric of efficiency. Research of the efficiency of Smart Contracts and Hyperledger platforms is currently being performed.
