3a - Onboarding of a New Dataspace Participant - Providers (data - application - infrastructure) & Consumers

Full ID:

ONPRO

Description:

To help understand the content of this document, readers should familiarize themselves with the key definitions and actors and the business process introduction containing the diagram legend.

The onboarding process for a new Applicant details the tasks and decisions required to onboard a new organisation to a Dataspace. Both Providers and Consumers can apply to a Dataspace and will be referred to as (Dataspace) Applicants from here on. Dataspace Applicants are assumed to be an organisation and not an individual person. The Applicant Representative, the person/people acting on behalf of the Applicant, applying to the dataspace is assumed to be a member of the Applicant organisation's directory.  

Applicants submit their onboarding requests to the Governance Authority. Upon approval, they set up the Simpl-Agent, a local gateway enabling interaction with the dataspace. As such installing the Simpl-Agent is a crucial step for onboarding to the dataspace. The Applicant Representative must install and configure the Simpl-Agent. After successful setup, the Applicant receives the necessary security credentials, completing the onboarding process and allowing participation in the dataspace. 

The actors involved in this process are the: Governance Authority, Applicant, and Applicant Representative.  

 Prerequisites for the business process: 

The following prerequisites must be met to enable the process to occur: 

  1. Dataspace description: The document(s) describing the dataspace’s objectives, candidature criteria and requirements applicable to an organisation for onboarding must be developed and made available to a potential applicant (e.g., website publication). 
     

Business Process Diagram & Steps 

This chapter presents a diagram visualizing the business process, labelled with specific steps. Each step is further detailed in the accompanying 'Step Description'. 

Figure 2: Diagram representing the Onboarding of a New Dataspace Participant - Providers (data - application - infrastructure) & Consumers.
Diagram representing the Onboarding of a New Dataspace Participant - Providers (data - application - infrastructure) & Consumers.


Steps Description: 

Below there is the description of the steps involved in this business process. Each step outlines the specific actions and decisions required to successfully complete the process: 

  1. Prepare & submit onboarding request: This initial step involves the prospective Applicant preparing a comprehensive application to participate to the dataspace, gathering the required information based on the documentation made available by the Governance Authority (see prerequisites 1). After the preparation of the onboarding request, the Applicant fills in and digitally signs the forms and any other documents that may be mandatory, and submits them to the Governance Authority for review. 
  2. Review onboarding request: After receiving the onboarding request, the Governance Authority starts the review of the process. It verifies the Applicant’s onboarding request against a predefined set of criteria and the alignment with the dataspace objectives (see prerequisite 1). The review process of the onboarding request can be either manually or automatically done by the Governance Authority. 
  3. Request Approved?: As an outcome of the review in step 2, the Governance Authority approves or rejects the request. If the request is approved, the process continues to agent deployment in step 4. In case deficiencies are found, the Applicant shall be allowed to address them and start over the process from Step 1 
  4. Agent deployment: If the application is approved, the ApplicantRepresentative downloads and installs the minimal set of modules from Simpl-Open that are required to have an operative Simpl-Open agent. The ApplicantRepresentative then deploys and configures the Simpl-Open modules on the Applicant's infrastructure to establish the necessary environment for operation within the dataspace. 
  5. Generate public/private keypair: The Applicant's agent generates a public/private key pair to enable encrypted communications and data integrity within the dataspace. The private key is securely stored in the agent. The applicant representative shares the public key with the Governance Authority to request signed security credentials.  
  6. Create & sign security credentials: The Governance Authority creates and signs digital security credentials (e.g., x.509 certificates) incorporating the Applicant's public key, which serves to verify that the security credentials are issued to the correct entity. 
  7. Send the security credentials: The Governance Authority sends the signed security credentials to the Applicant. The security credentials are essential to ensure secure operations within the dataspace. 
  8. Store & install security credentials: The Applicant Representative stores and installs the signed identity security credentials in its Simpl-Open Agent. After which the Applicant Representative initiates the verification request of the installed security credentials to the Governance Authority to verify if the secure connection is operational. 
  9. Verify security credentials: The Governance Authority verifies the received identity security credentials.  
  10. Passed Verification?: As an outcome of the review in step 9, if the Applicant passed the verification check, then the process moves to step 13 If the participant fails the verification check, then the process moves to step 11 
  11. Notify of failure: The applicant is notified of the failure by the Governance Authority. 
  12. Remediate issues: The Applicant is offered the possibility to correct issues or deficiencies discovered by the Governance Authority during the verification process. After the corrections are made, the applicant can return to step 9 to retry verification. 
  13. Notify of a successful verification result: The applicant is notified of its verification and is successfully onboarded onto the dataspace. 

Status: 

Proposed

Related to:

Reacties

User
Geplaatst door Luis Carlos BU… op ma, 25/03/2024 - 14:34

The Description of the high-level requirement should also include provision for the possible withdrawal of participants in Dataspaces

 

User
Geplaatst door Javier VALIÑO op di, 02/07/2024 - 15:12

Looking at the diagram, it seems it is following a centralised approach where the Governance Authority is issuing the security credentials.

Is there a plan to support decentralised approaches such as Verifiable Credentials/DIDs as described by Gaia-X (https://www.gaiax.es/sites/default/files/2023-04/Gaia-X_Architecture_Do… section 4,6)? 

Als antwoord op door Javier VALIÑO

User
Geplaatst door Rick Santbergen op ma, 15/07/2024 - 14:52

Hi Javier, the credential issued by the Dataspace Governance Authority only has the purpose of implementing a secure mTLS channel of communication between participant Agents (tier 2 agent-to-agent communication), which ensures the highest level of security. Besides that, all operations/functionalities such as signing a service offering, consuming a service offering, signing contracts, and giving consent, etc., will be following the decentralised approach (VC/DID) as described by Gaia-X.

User
Geplaatst door Mark Dietrich op do, 04/07/2024 - 14:06

As discussed in Simpl workshop -- process should reflect organisations' having individuals who are authorized to make an application (able to prove they have the authority), as well as the fact that different individuals will be involved at different points (e.g. the Rector of KU Leuven will not install software).