Trust Framework

Trust Framework


1. Scope and objectives

This building block defines the trust-specific elements of a trust framework within a data space. Trust is essential because the most critical processes - such as verifying participant identities, validating attestations, and ensuring data is managed in accordance with the data space rulebook - depend on it. A robust trust framework not only strengthens security but also accelerates trust decisions and facilitates data exchanges, thereby supporting the growth of the data space.

The objectives of this building block are:

  • To articulate the core components and principles of a trust framework tailored to data spaces.

  • To define the roles and responsibilities of entities that establish and maintain trust (e.g., trust anchors, trust service providers, trusted data sources, notaries).

  • To explain how existing trust frameworks can be utilized or extended to meet the data space’s needs.


2. Capabilities

The main capabilities of a Trust Framework include:

  1. Validation and Verification of participants and services: Ensures all participants and services are verifiable against the established rules, facilitating the establishment of trust between participants, and enabling fair and trustworthy data transactions.

  2. Governance Enforcement: Enforces the conditions and rules set by the data space governance authority, thereby increasing transparency and interoperability. With reference to the layers of interoperability described in the European Interoperability Framework, the Trust Framework specified under this Pillar specifically addresses the technical, organizational and semantic layers.

  3. Definition of Trust Entities: Provides clear guidelines for establishing Trust Anchors and other entities (e.g., Trust Service Providers, Conformity Assessment Bodies) that are accredited to issue attestations on identities or other attributes.

  4. Data Space Registry integration: Offers mechanisms (via the Data Space Registry) to store the data space rulebook, lists of accredited trust anchors (including revoked ones), and the data space schemas used to assess compliance.


3. Specifications

3.1 General elements of a trust framework

A trust framework provides the methodology and technical specifications for collecting, organizing, and verifying information to support trust decisions - that is, decisions about whether an entity, piece of information, or transaction can be trusted.
A trust framework is comprised of:

  • (business related) policies, rules, and standards.
    These are collected and documented in the data space rulebook.

  • procedures for automation and implementation:
    These procedures enable both the automation (via IT systems) and the practical implementation (through organizational processes, such as Know Your Customer/Know Your Business ) of the business-related components.

To establish an effective trust framework, the following key components are required:

  1. Defined Criteria for Participants:
    A set of criteria - linked to regulatory, business, or technical requirements - applies to data space participants. These criteria, which may pertain to identities or other relevant elements, are detailed in the data space rulebook managed by the Data Space Governance Authority (DSGA).

Embracing common rules that can be further specialized with domain-specific requirements is essential for enhancing cross-data space interoperability. For example, Gaia-X provides one mandatory conformity scheme (Gaia-X Standard Compliance) and three optional schemes (Gaia-X Labels, from Label 1 to Label 3). These cross-sectorial schemes reflect European values such as transparency, security, interoperability, portability, sustainability, and data protection, with additional requirements addressing European control in Gaia-X Label 2 and Label 3. Data spaces can use these schemes as a basis, complementing them with additional requirements and corresponding assessment methods tailored to their specific needs.
  1. Processes and Technical Means for Validation:
    Robust processes and technical mechanisms must be implemented to validate and verify the defined criteria - potentially through automation. This involves:

    • Defining the format of claims (as defined in ISO CASCO terminology, where claims are assertions made about subjects).

    • Establishing mechanisms to collect these claims.

    • Digitalizing the criteria.

    • Developing semantic models and ontologies.

    • Setting protocols for exchanging attestations.

    • Implementing technical standards to validate, verify, and, if necessary, revoke or suspend attestations.

    • Providing solutions for rights and trust delegation.

These aspects are further discussed in the Identity & Attestation Management building block.

  1. Accredited Sources of Trust:
    A list of entities accredited by the DSGA as trusted sources for the claims made by data space participants must be defined.

    Note: Different levels of trustworthiness may be established by applying distinct sets of criteria or by referencing different sources of trust for each level.

3.2 Roles ensuring trust

This section employs terminology from ISO CASCO and the W3C VC: Verifiable Credentials Data Model v2.0 . Corresponding definitions are provided in the Glossary section.

The following roles are defined:

3.2.1 Trust Anchors

Trust Anchors are authoritative entities for which trust is assumed and not derived. Each Trust Anchor is accepted by the data space governance authority in relation to a specific scope of attestation.
Examples include governmental bodies. Their fundamental role is to ensure the authenticity, integrity, security, and reliability of identities, data services and transactions within the data space.

3.2.2 Trust Service Providers (TSPs)

Trust Service Providers (also referred to as Trusted Issuers) are legal or natural persons deriving their trust from one or more Trust Anchors and designated by the data space governance authority as parties eligible to issue attestations about specific objects.
They provide and preserve certificates, like digital certificates to create and validate electronic signatures and to authenticate their signatories, for instance, websites in general.

Data spaces may accept

Conformity Assessment Bodies (CABs), accredited to attest to conformity with established standards, codes of conduct, and regulations, as Trust Service Providers.

Trust Service Providers issue cryptographic material based on documented Know Your Business/Know Your Customer (KYB/KYC) processes, which verify the identity of the party requesting the digital certificate associated to the cryptographic material.

For interdependent attributes, the data space rulebook may require that one attribute be signed by the same issuer as another. For example, a rule might mandate that the attestation regarding whether a Data Product contains Personal Identifiable Information (PII) must be signed solely by the Data Product's Producer.

3.2.3 Notaries

When a designated Trust Service Provider is unable to issue cryptographic material or directly sign a claim, the data space governance authority may accredit one or more

notaries. Notaries validate claims using objective evidence from
trusted data sources and convert non-machine-readable proofs into machine-readable formats. However, attestations issued by a notary typically carry a lower trust level than those directly issued by a Trust Service Provider.

For example, while the European Commission provides several APIs (including one for verifying the validity of an EORI number), these do not return machine-readable proofs in the Verifiable Credential format. Consequently, data spaces may rely on a notary service that leverages the European Commission API as a trusted data source for validation.

According to the ISO CASCO terminology, “Entity” in the first column of the table below refers to the entity which is the subject of the claim (in the third column). In the last column, the generic term “trust source” is used to summarily denote Trust Anchors, Trust Service Providers, and Notaries. While the formulation of criteria, attributes, and claims is technology-agnostic, we recommend the use of suitable W3V Verifiable Credentials, for instance, Participant Credentials or Service Credentials. Entity Criterion Attribute/Claim Possible Trust Sources Participant (Legal Person - all roles) The participant shall be uniquely identified. Registration number of the legal person (typically issued by national bodies), which identifies one specific legal entity. Trusted data sources: EORI (European Commission API) LEI Code (Global Legal Entity Identifier (GLEIF) API OpenCorporate API VAT Information Exchange System (VIES) API Notary services: Alternatively, one can use notary services who provide more services and service level agreements. These notary services, eventually, also consult the trusted data sources quoted above. Participant (Legal Person - all roles) Proof of Data Space Membership is required Data Space Membership Credential Data Space Governance Authority Participant (Legal Person - Provider) The physical location of the Participant’s headquarters shall be provided. ISO 3166-2 code eIDAS TSP (declaration) Participant (Legal Person - Provider) The physical location of the Participant's legal registration shall be provided ISO 3166-2 code eIDAS TSP (declaration) Service The Provider shall ensure there are provisions governing the rights of the parties to use the service and any Customer Data therein. This criterion is attested through the following three attributes: LegallyBindingAct, CustomerDataProcessingTerms and CustomerDataAccesTerms eIDAS TSP (declaration)/Assessment and Monitoring Bodies for BSI C5, CISPE and EU Codes of Conducts, CSA CCM (certification) Participant (Provider) The Provider shall clearly define if and to what extent sub-processors will be involved, and the measures that are in place regarding sub-processors management. If the attribute possiblePersonalDataTransfers is declared, then the DataTransfer attribute is also provided in the credential. eIDAS TSP (declaration)/Assessment and Monitoring Bodies for SecNumCloud, CISPE and EU Codes of Conducts (certification) Participant (Data Provider) The Data Provider shall have the legal authorization from the Data Producer to include the data in the Data Product links to authorization documents which are signed through a data space-accredited Trust Service Provider. Data Space Governance Authority Data Product For each Data Product, the Data Provider shall provide in the Data Product Description a Data License defining the usage policy in ODRL for all data in this Data Product. The Data Product Description shall include a data license expressed as a valid ODRL document containing at least indication whether or not the data product contains licensed data. eIDAS TSP (declaration)

3.3 Use and extension of existing trust frameworks

A data space can leverage - and, if necessary, modify - existing trust frameworks to define both governance and the associated technical and procedural components. Generic trust frameworks, such as the IDSA Rulebook or those provided by Gaia-X, iSHARE or Ayra, can serve as foundational models. Additionally, frameworks developed for specific projects or initiatives, like Catena-X, DOME or Simpl-Open of the European Commission, may also be (re-)used.

From a governance standpoint, these existing frameworks establish requirements and criteria for identities, authorization, and other key elements governing interactions among data space participants, including data usage, processing, and the roles of intermediaries.

Moreover, established trust frameworks define processes and methods that integrate widely adopted technical standards to operationalize the validation and verification of compliance with the data space rulebook.

Existing frameworks can be extended by:

  • Introducing more stringent requirements for the acceptance of trust anchors and trust service providers, thereby selecting a subset of those accepted in the trust framework which is extended;

  • Adding additional rules into the rulebook by:

    • Introducing more criteria for a specific credential type - for instance, imposing additional transparency requirements for participant onboarding.

    • Designating new, data-space-specific trust anchors and trust service providers for the new criteria.


4. Interlinkages

  • Identity & Attestation Management: the definition of a trust framework relates to the definition of the elements in both this building block and the “Identity and Attestation Management” building block, which provides guidance on the use of standards to express and manage attestations.

  • Access & Usage Policies Enforcement: defining and enforcing data access and usage policies are integral to implementing a trust framework.

  • Data Exchange: verifying critical entity-related information is vital for secure data exchange. In addition, data exchange–specific models - covering data transactions, intermediaries, and consent management - contribute to the process of collecting claims within the trust framework.

  • Organisational Form and Governance Authority: the Data Space Governance Authority is responsible for developing and maintaining the overall governance framework and the data space rulebook. This rulebook outlines the requirements for data space participation and specifies the accepted Trust Anchors and Trust Service Providers, forming the foundation of the trust framework.


5. Co-creation questions

The following questions aim to guide data space initiatives in defining/adopting a trust framework:

  • What kind of trust anchors should the data space have to validate and verify the credentials of participants? (ref. Functional Analysis and Data Space Design step 1 - Q4)

  • How the roles of Trust Anchors, Trust Service Providers, Trusted Data Sources and Notaries are implemented by the Data Space Governance Authority in the data space? (ref. Functional Analysis and Data Space Design step 1 - Q4)
    Data spaces should identify entities to trust. These can be the Data Space Governance Authority itself (providing trust with regards to the participation in the data space and - hence - the compliance with the Rulebook) or third party identity & attestation trust providers. Depending on the set-up, these third parties can provide legal proof.

  • What type of registry is adequate to store and keep updated the list of trust anchors in data spaces? (ref. Functional Analysis and Data Space Design step 1 - Q5)

  • What type of methods and technical enablers can be combined to increase the level of trust among the participants? (ref. Functional Analysis and Data Space Design - step 2 Q1)

  • Are there existing regulatory schemes, standards and existing trust frameworks to be considered as a basis/component for the definition of the data space-specific trust framework?


6. Implementation

6.1 Federation Services

The lists of trust anchors, trust service providers, trusted data sources, and notaries accredited by the data space governance authority are stored in and can be discovered via the Data Space Registry.

Identity Provisioning and Conformity Assessment Services are employed to implement this building block. These trust services assess the identities and other relevant claims made by participants or service providers seeking qualification to operate in the data space.

Below are some relevant examples:

eIDAS Trust Services The eIDAS regulatory framework is a key enabler for secure cross-border transactions, focusing on electronic identification, authentication, and trust services. The first version eIDAS1.0 defines five main trust service categories to enhance security and trust levels in data spaces: QESeals: Similar to traditional business stamps, these can be applied to an electronic document to guarantee its origin and integrity. QESigs: Similar to handwritten signatures but in an electronic format with the same legal implications. QWACs: Electronic certificates to prove that a website is reliable, secure and trustworthy. QETimestamps: Provide evidence that an electronic document existed at a specific point in time (e.g., for purchase orders). QERDS: Provide proof of electronic registered delivery services and validation of data sent via RDS (Registered Delivery Service). The updated eIDAS2 regulation (electronic Identification, Authentication, and Trust Services) further enhances trust, security, and interoperability in cross-border digital transactions within the European Union. The introduction of new trust services and digital identity wallets for both individuals and organizations is a significant step towards a more secure and user-centric digital ecosystem. The new trust services are: Electronic Attestations of Attributes (EAA): Allow organizations to issue verifiable credentials attesting specific attributes (e.g., professional qualifications, educational degrees, or medical information). These attestations, issued by a competent authority, have the same legal effect as paper-based documents across the EU. Electronic Ledgers: Enable the recording of data in a tamper-evident manner using distributed ledger or blockchain technology. They offer a secure, transparent means of recording transactions, agreements, or processes, with the same legal standing as traditional records. Electronic Archiving: Ensures the long-term preservation and integrity of electronic data and documents. It provides a secure and reliable way to store critical information for extended periods while maintaining legal admissibility. Electronic Signature Creation Devices (ESCD): Manage the creation of electronic signatures and seals via secure hardware and software. These services facilitate remote signing and carry the same legal effect as traditional handwritten signatures across the EU. In addition to these new trust services, eIDAS2 introduces European Digital Identity Wallets (EUDI) to further enhance trust and security in cross-border digital transactions within the EU. The EUDI framework ensures legal validity and interoperability across Member States and reinforces security and privacy by integrating privacy-preserving technologies. For instance, Zero Knowledge Proof (ZKP) methods allow an entity to validate whether a given statement, based on the person’s identification data and attestation of attributes, is true without revealing any underlying data. This approach effectively preserves the privacy of the users. Examples of Available Trusted Data Sources Legal/Natural entity verification (eIDAS) - https://ec.europa.eu/tools/lotl/eu-lotl.xml Legal registration number (EORI)- the European Commission API Legal registration number - VAT information exchange system (VIES) API Global Legal Entity Identifier (GLEIF) API EU Trusted Lists Regulation (EU) 910/2014 (the original eIDAS, now significantly amended by eIDAS2) mandates that each Member State establish, maintain, and publish trusted lists containing information about qualified Trust Service Providers (TSPs) and the trust services they offer. A Qualified Trust Service Provider may only provide its qualified trust services after the qualified status has been indicated in the relevant trusted list. These lists need to be electronically sealed or signed. The technical specifications are defined in ETSI TS 119 612 v2.1.1. To simplify access to these trusted lists, the European Commission provides a central directory called the List Of Trusted Lists (LOTL). The LOTL is available in a readable format and in XML for automated processing. It consists of four components: Issuing scheme information, i.e. relevant scheme underlying the issuance and maintenance of the trusted list. Trust Service Providers recognised by the scheme. Service(s) provided by these Trust Service Providers, including their types and the current status of the service(s). Status history of each service. Examples of Available Trusted Lists: EC Trusted Lists browser eID.AS Trusted Lists viewer Trusted Lists browser

7. Future topics

  • In cooperation with the Regulatory Compliance building block: analysis of the impact of the implementation of the European Digital Identity Framework Regulation in terms of requirements for specific roles or types of data spaces.

  • Definition of cross-data space interoperability, in relation to different dimensions (e.g. technical, semantic and organisational) and by identifying the means to achieve it. This topic will be deepened reflecting the outcomes of the ongoing work in the Eclipse Dataspace Working Group (EDWG) and the efforts around the creation of a common data space ontology.

  • Deepening on semantic models defined in trust frameworks.

  • Alignment with the CEN Trusted Data Transaction pre-standardization workshop program.


8. Further reading

8.1 The European Digital Identity Framework Regulation

The European Digital Identity Framework Regulation (commonly known as eIDAS 2.0) governs electronic identification and trust services for electronic transactions within the internal market. To promote cross-border use, the regulation mandates that trust services be accepted as evidence in legal proceedings in all Member States. Consequently, Member States are required to establish, maintain, and publish trusted lists containing information on qualified Trust Service Providers and the trust services they offer. Each Member State publishes its own Trusted List, while the European Commission maintains the List Of Trusted Lists (LOTL), accessible via various technical means.

In addition, the regulation will require Member States to provide citizens, residents, and businesses (hereafter “users”) with a notified European Digital Identity Wallet (EUDI Wallet) upon request. An EUDI Wallet is an electronic tool - deployable on mobile devices - that enables users to identify themselves and authenticate at a high-security level using a national identifier. Furthermore, EUDI Wallets can store attestations of attributes that users may present at their discretion. Users remain sovereign in the sense that they are not forced to use a specific EUDI Wallet implementation or product; they can choose any one of the notified EUDI Wallets.

Moreover, where private service providers (with the exception of microenterprises and small enterprises) are required by Union or national law - or by contractual obligation - to employ strong user authentication for online identification, these service providers must, within 36 months of the entry into force of the relevant implementing acts, accept European Digital Identity Wallets that comply with the Regulation (see Article 5f of the European Digital Identity Framework). This requirement is activated only upon the user’s voluntary request.

Within the context of this building block, the use of Qualified Electronic Attestations of Attributes (QEAA) is particularly relevant. QEAA are issued by qualified Trust Service Providers, which maintain an interface for requesting and delivering these attestations, including a mutual authentication interface with EUDI Wallets and potentially an interface towards Authentic Sources to verify attributes.

QEAA Providers provide information or the location of the services that can be used to enquire about the validity status of the QEAAs without accessing any information about the use of the attestations.

Further information on the European Digital Identity Framework Regulation and its updates is available here.

8.2 References to existing Trust Frameworks


9. Glossary

Term

Description

Data Space Governance Authority

The body of a particular data space, consisting of participants that is  committed to the governance framework for the data space, and is responsible for developing, maintaining, operating and enforcing the governance framework.

Accreditation

third-party attestation related to a conformity assessment body, conveying formal demonstration of its competence, impartiality and consistent operation in performing specific conformity assessment activities (ref. ISO/IEC 17000:2020(en), Conformity assessment — Vocabulary and general principles )

Accreditation body

authoritative body that performs accreditation (ref. ISO/IEC 17000:2020(en), Conformity assessment — Vocabulary and general principles )

Attestation

issue of a statement, based on a decision, that fulfilment of specified requirements has been demonstrated (ref. ISO/IEC 17000:2020(en), Conformity assessment — Vocabulary and general principles )

Claim

an assertion made about a subject. (ref. Verifiable Credentials Data Model v2.0 (w3.org)

Evidence

Evidence can be included by an issuer to provide the verifier with additional supporting information in a verifiable credential (ref. Verifiable Credentials Data Model v2.0 (w3.org) )

Issuer

A role an entity can perform by asserting claims about one or more subjects, creating a verifiable credential from these claims, and transmitting the verifiable credential to a holder. (ref. Verifiable Credentials Data Model v2.0 (w3.org) )

Conformity Assessment Body

body that performs conformity assessment activities, excluding accreditation (ref. ISO/IEC 17000:2020(en), Conformity assessment — Vocabulary and general principles )

Trust Framework

A trust framework is comprised of:

  • (business-related) policies, rules, and standards collected and documented in the rulebook.

  • procedures for automation and implementation of the business-related components.

Trust Anchor

Trust Anchors are authoritative entities for which trust is assumed and not derived. Each Trust Anchor is accepted by the data space governance authority in relation to a specific scope of attestation.

Trust Service Provider

Trust Service Providers (also referred to as Trusted Issuers) are legal or natural persons deriving their trust from one or more Trust Anchors and designated by the data space governance authority as parties eligible to issue attestations about specific objects.

Trusted Data Source

Source of the information used by the issuer to validate attestations. The data space defines the list of Trusted Data Sources for the Data Space Conformity Assessment Scheme/s.

Notary

Notaries are entities accredited by the Data Space, which perform validation based on objective evidence from a data space Trusted Data source, digitalising an assessment previously made.

LOTL (List of Trusted Lists)

List of qualified trust service providers in accordance with the eIDAS Regulation published by the Member States of the European Union and the European Economic Area (EU/EEA)

Verifiable Credential

A verifiable credential is a tamper-evident credential that has authorship that can be cryptographically verified. Verifiable credentials can be used to build verifiable presentations, which can also be cryptographically verified (ref. https://www.w3.org/TR/vc-data-model-2.0/#dfn-verifiable-credential )