In this context, CONNECT is one of the first solutions that considers the composition of infrastructure entities extending from the traditional view of cloud-based services (including applications such as traffic control centres and/or intersection movement assistance services) and centralized security solutions (such as PKIs) to also align with the vision of disaggregating the services over the entire compute continuum so as to benefit from resource availability and optimal latency capabilities closer to the edge – features provided from emerging networking technologies and schemes like (B)5G and Multi-Access Edge Computing (MEC) architectures. Compounding this issue, CONNECT considered the integration of ETSI MEC as a driving factor for bringing processing power near the vehicle to meet ultra-low-latency requirements, and to reduce network traffic towards a centralized data-centre. To achieve this CCAM-wide trust quantification, CONNECT has designed an overarching framework comprising of two phases, namely the Design and Runtime phase. The Setup phase encompasses all operations needed for the correct establishment and deployment of CONNECT- related components needed to support the continuous trust assessment throughout the entire lifecycle of a (data and/or entity) resource: From the definition of the appropriate trust model templates considering the most prominent types of risks and attacks against the entire CCAM ecosystem, dictating the type of trustworthiness evidence that need to be continuously monitored, from each resource, so as to quantify its trust level and compare it to the Required Trust Level (RTL), to the deployment of all trust-related information and components as part of CONNECT’S Trusted Computing Base towards enforcing the circulated trust policies. The Runtime phase encompasses the (runtime) operation of all CONNECT attestation schemes and security controls (i.e. Misbehaviour Detection service), protected through their instantiation in a Trusted Execution Environment, for allowing the secure monitoring and exchange (in a verifiable manner) of a resource’s trustworthiness evidence based on which the trust assessment/quantification will occur. Such trustworthiness evidence will be further processed, before been transmitted outside the vehicle, so as to be adequately abstracted (harmonized trustworthiness evidence) in order to avoid privacy implications.