-
Notifications
You must be signed in to change notification settings - Fork 19
CSC API v2.2 - Architectures and protocols for remote signature applications #29
Copy link
Copy link
Open
Labels
Art 5a(23) ICFIntegrity & Core functionalities of EUDI WalletsIntegrity & Core functionalities of EUDI WalletsCIR (EU) 2024/2979Integrity and core functionalities - https://data.europa.eu/eli/reg_impl/2024/2979/ojIntegrity and core functionalities - https://data.europa.eu/eli/reg_impl/2024/2979/ojCat: Protocols & InteroperabilityFunctional requirements defining common standards ensuring seamless cross-border interoperability.Functional requirements defining common standards ensuring seamless cross-border interoperability.Cat: Relying PartiesFunctional requirements for relying parties on registration, auth, data requests, and handling.Functional requirements for relying parties on registration, auth, data requests, and handling.Cat: Wallet ProvidersFunctional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Functional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Domain: Cross DomainCommon enablers shared across domains, such as cryptographic primitives, transport security, etc.Common enablers shared across domains, such as cryptographic primitives, transport security, etc.Domain: Trust ServicesSTS underpinning trust infrastructure, including electronic signatures, timestamps, certificatesSTS underpinning trust infrastructure, including electronic signatures, timestamps, certificatesDomain: WalletCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsEssentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialFn: QESFunctional: Qualified Electronic Signature, both for the Wallet and TSPsFunctional: Qualified Electronic Signature, both for the Wallet and TSPsFnRAn STS that specifies Functional RequirementsAn STS that specifies Functional RequirementsRegulationStandards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.Standards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.gapThis ticket is about a gap identified in our analysis and needs to be scheduledThis ticket is about a gap identified in our analysis and needs to be scheduledsts: readyThe standard has a stable version publishedThe standard has a stable version publishedtest specificationSTS entry has linked functional conformance testing activities.STS entry has linked functional conformance testing activities.
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
Art 5a(23) ICFIntegrity & Core functionalities of EUDI WalletsIntegrity & Core functionalities of EUDI WalletsCIR (EU) 2024/2979Integrity and core functionalities - https://data.europa.eu/eli/reg_impl/2024/2979/ojIntegrity and core functionalities - https://data.europa.eu/eli/reg_impl/2024/2979/ojCat: Protocols & InteroperabilityFunctional requirements defining common standards ensuring seamless cross-border interoperability.Functional requirements defining common standards ensuring seamless cross-border interoperability.Cat: Relying PartiesFunctional requirements for relying parties on registration, auth, data requests, and handling.Functional requirements for relying parties on registration, auth, data requests, and handling.Cat: Wallet ProvidersFunctional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Functional requirements on core functions, security, UI, and lifecycle, managed by EUDIW Providers.Domain: Cross DomainCommon enablers shared across domains, such as cryptographic primitives, transport security, etc.Common enablers shared across domains, such as cryptographic primitives, transport security, etc.Domain: Trust ServicesSTS underpinning trust infrastructure, including electronic signatures, timestamps, certificatesSTS underpinning trust infrastructure, including electronic signatures, timestamps, certificatesDomain: WalletCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsCovers STSs specific to ARF and wallet operations such as credential formats, protocols, and APIsEssentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialEssential to guarantee interoperability, issuance, presentation, and verification of a credentialFn: QESFunctional: Qualified Electronic Signature, both for the Wallet and TSPsFunctional: Qualified Electronic Signature, both for the Wallet and TSPsFnRAn STS that specifies Functional RequirementsAn STS that specifies Functional RequirementsRegulationStandards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.Standards referenced or mandated in the Implementing Acts (IA/CIR); binding for implementation.gapThis ticket is about a gap identified in our analysis and needs to be scheduledThis ticket is about a gap identified in our analysis and needs to be scheduledsts: readyThe standard has a stable version publishedThe standard has a stable version publishedtest specificationSTS entry has linked functional conformance testing activities.STS entry has linked functional conformance testing activities.
Type
Projects
- StatusShow more project fields🏗 In progress
Formal name
CSC API v2.2 - Architectures and protocols for remote signature applications
Overview
When digital signatures are created within a device, the interfaces and functions are standardized, e.g. the API used by the application program to access the signature creation libraries and the interface to the smart card or similar device (if a device is used) holding the signing key.
When digital signatures move to the cloud, the functions needed to create a digital signature can be distributed across several service instances, each carrying out one or more steps in the signature creation process. The interfaces between such services are however until now not standardized.
The Cloud Signature Consortium aims to fill this gap in standardization by defining the architectural design, communication protocols, application programming interfaces, data structures, and technical requirements needed to establish interoperable solutions for cloud-based digital signatures. While these specifications are applicable in a wide variety of use cases with different security requirements, the fulfilment of requirements imposed by the eIDAS Regulaon of the EU is particularly addressed, supporting the creation of “advanced” or “qualified” electronic signatures and electronic seals in the cloud.
This document contains technical specifications that are intended for use by applications for creating digital signatures in the cloud and by a variety of applications consuming these services.
By implementing their services according to these specifications, service providers can ensure that services are applicable as parts of complete digital signature systems in the cloud in a plug and play manner. Existing standards and open specifications are considered by the consortium as far as applicable.
Work Plan
Current Version
EC Assessment Status
Forthcoming Version
Testing & Conformance
Updates
Alerts
There are no open alerts.
References
None.