hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.6.1.2 JSON related component
|
The element to request credentials information shall be the set of parameters specified in clause 8.6.1.1. Processing model The server shall process the components as indicated in the credentials/info description of the CSC standard [1]. The server shall process each component as indicated in the clause 8.6.1.1 of the present document if the child is not specified in any of the referenced CSC standard [1]. Otherwise, the server shall follow the processing model defined in the corresponding CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.6.1.3 XML related component
|
The element that shall be the main component for requesting certificate information retrieval shall be the root element of the message etsisig:InformationRequest. The etsisig:InformationRequest element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2. The dss2:KeySelector,child element of the etsisig:InformationRequest element shall be set in order to identify the signing credential whose information are needed to be returned as main output of the profile.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.6.2 Response message (I)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.6.2.1 Component for responding to credential information requests
|
The credential information response message resulting from one request of credential information, shall include the component for notifying the global result of the operation requested by the client application. The credential information response message may include one or more credential information elements as defined in clause 7.22. This message includes the following components. Table 44 Ref Component for Presence 7.22 returning signing credential information O 7.24 notifying operation result(s) M 7.28 returning credential authorization mode O 7.30 returning SCAL level required O ETSI ETSI TS 119 432 V1.2.1 (2020-10) 61
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.6.2.2 JSON related component
|
The response to the credential information retrieval request shall consist of the set of results specified in clause 8.6.2.1 and returned as in the response of the credentials/info method as specified in CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.6.2.3 XML related component
|
The element that shall be the main component for responding with certificate information retrieval shall be the root element of the message etsisig:InformationResponse. The etsisig:InformationResponse element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2. The ds:KeyInfo, child element of the etsisig: InformationResponse element will return the requested signing certificate and key information.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.7 Service information messages (J)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.7.1 Request message (J)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.7.1.1 Component for requesting service information
|
The message for requesting the service information shall contain the component for: 1) Identifying one or more protocols and/or profiles with which the request message is compliant. The first one of such components shall have the following URI as value, identifying the request message as one that has been built using the "service information" protocol specified in the present document: - http://uri.etsi.org/19432/v1.1.1/serviceinformationprotocol# NOTE: The protocol defined by the present document may be combined with other profiles to request additional features or functionality provided by the SCS as long as these profiles do not conflict with the requirements specified in the present document. This message includes the following components. Table 45 Ref Component for Presence 7.9 language selection O 7.15 protocol identifier M
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.7.1.2 JSON related component
|
The element to request service information shall be the set of parameters specified in clause 8.7.1.1. Processing model The server shall process the components as indicated in the info description of the CSC standard [1]. The server shall process each component as indicated in the clause 8.7.1.1 of the present document if the child is not specified in any of the referenced CSC standard [1]. Otherwise, the server shall follow the processing model defined in the corresponding CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.7.1.3 XML related component
|
The element that shall be the main component for requesting service information shall be the root element of the message etsisig:InformationRequest. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 62 The etsisig:InformationRequest element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2. The dsb:Language, child element of the etsisig:OptionalInputs element can be set for language and culture selection.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.7.2 Response message (K)
| |
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.7.2.1 Component for responding to service information requests
|
This profile includes the following components. Table 46 Ref Component for Presence 7.20 returning service information M
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.7.2.2 JSON related component
|
The response to service information request shall consist of the set of parameters specified in clause 8.7.2.1 and returned as in the response of the info method as specified in CSC standard [1].
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.7.2.3 XML related component
|
The element that shall be the main component for responding with service information shall be the root element of the message etsisig:InformationResponse. The etsisig:InformationResponse element is defined in XML Schema file "[XSDSIGCREATIONPROT]", whose location is detailed in clause A.2. The etsisig:ServiceInformation, child element of the etsisig:OptionalOutputs element will return the requested service information.
|
649cb38c17611a9ca3292f97ff124c8c
|
119 432
|
8.8 Component use summary
|
A = Profile for signature request B = Profile for signature response C = Profile for digital signature value request D = Profile for digital signature value response E = Profile for asynchronous processing F = Profile for signing certificates list request G = Profile for signing certificates list response H = Profile for certificate information retrieval request I = Profile for certificate information retrieval response J = Profile for service information request K = Profile for service information response ETSI ETSI TS 119 432 V1.2.1 (2020-10) 63 Table 47 Ref. Component for: A B C D E F G H I J K 7.2 asynchronous/synchronous operation mode selection O O 7.3 identification of the request O O M O O 7.4 credential authorization O O 7.5 defining optional data to be returned O O O 7.6 defining the validity period for asynchronous requests O O 7.7 service authentication O O O O O 7.8 identifying signature credentials C C C 7.9 language selection O O O O O O 7.10 contents from certificate info to be returned O O O 7.11 managing digital signatures transactions O O 7.12 service policy selection O O 7.13 signature creation policy selection O O 7.14 optional signature attributes/properties selection O 7.15 protocol identifier M M M M M M 7.16 requesting specific signature formats O 7.17 signer identification C 7.18 specifying response URL O O 7.19 submitting document(s) or hash(es) to be signed M M 7.20 returning service information M 7.21 returning signed documents or signatures O 7.22 returning signing certificate information O O O 7.23 returning the list of the signing certificate(s) O 7.24 notifying operation result(s) M M M M 7.25 service policy identification O O 7.26 identification of the response C C 7.27 signature creation policy identification O O 7.28 returning credential authorization mode O 7.29 returning DSV O 7.30 returning SCAL level required O ETSI ETSI TS 119 432 V1.2.1 (2020-10) 64 Annex A (normative): XML and JSON Schema files A.1 JSON Schema file location for "$schema" "http://uri.etsi.org/19432/v1.2.1/json#" The file 19432-schema.json is contained in archive ts_119432v010201p0.zip which accompanies the present document and available at https://forge.etsi.org/rep/esi/x19_432_sign_creation_protocol/raw/v1.2.1/19432-schema.json contains the definitions of elements and types defined within the JSON schema whose "$schema" value is "http://uri.etsi.org/19432/v1.2.1/json#". A.2 XML Schema file location for namespace http://uri.etsi.org/19432/v1.1.1# The files etsi-org-19432-xmlSchema-common.xsd at https://forge.etsi.org/rep/esi/x19_432_sign_creation_protocol/raw/v1.1.1/etsi-org-19432-xmlSchema-common.xsd, etsi-org-19432-xmlSchema-dsv-creation.xsd at https://forge.etsi.org/rep/esi/x19_432_sign_creation_protocol/raw/v1.1.1/etsi-org-19432-xmlSchema-dsv-creation.xsd, etsi-org-19432-xmlSchema-service-information.xsd at https://forge.etsi.org/rep/esi/x19_432_sign_creation_protocol/raw/v1.1.1/etsi-org-19432-xmlSchema-service- information.xsd and etsi-org-19432-xmlSchema-signature-creation.xsd at https://forge.etsi.org/rep/esi/x19_432_sign_creation_protocol/raw/v1.1.1/etsi-org-19432-xmlSchema-signature- creation.xsd contain the definitions of elements and types defined within the namespace whose URI value is http://uri.etsi.org/19432/v1.1.1#. The four files are contained in archive ts_119432v010201p0.zip which accompanies the present document. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 65 Annex B (informative): OpenAPI™ description file An OpenAPI 3.0 description file (19432-openapi.yaml), as defined by the OpenAPI Initiative (OAI) (https://www.openapis.org), is contained in archive ts_119432v010201p0.zip which accompanies the present document and is available at https://forge.etsi.org/rep/esi/x19_432_sign_creation_protocol/raw/v1.2.1/19432-openapi.yaml. It contains the JSON Schema definitions for every component and the description of every message defined within the protocol specified in the present document. ETSI ETSI TS 119 432 V1.2.1 (2020-10) 66 Annex C (informative): Bibliography • ETSI TS 119 441: "Electronic Signatures and Infrastructures (ESI); Policy requirements for TSP providing signature validation services". • ETSI TS 119 442: "Electronic signatures and infrastructures (ESI); Protocol profiles for trust service providers providing AdES digital signature validation services". • ETSI EN 319 122-2: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 2: Extended CAdES signatures". • ETSI EN 319 132-2: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 2: Extended XAdES signatures". • ETSI EN 319 142-2: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 2: Additional PAdES signatures profiles". ETSI ETSI TS 119 432 V1.2.1 (2020-10) 67 Annex D (informative): Change History Date Version Information about changes March 2019 1.1.1 Publication as ETSI TS 119 432 June 2020 1.1.2 CR#1 - Alignments with dss-core-v2.0-cs02 CR#2 - Correction of errors found in the 119 432 JSON schema CR#3 - Alignment with draft CSC API v2.0 ETSI ETSI TS 119 432 V1.2.1 (2020-10) 68 History Document history V1.1.1 March 2019 Publication V1.2.1 October 2020 Publication
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
1 Scope
|
The present document provides policy and security requirements for Trust Service Providers (TSPs) implementing a service component supporting AdES digital signature creation. This component contains a signature creation application and is thus called Signature Creation Application Service Component (SCASC). However, it is more than just the SCA. It contains service elements around which parts of the driving application as defined in ETSI TS 119 102-1 [2] and ETSI TS 119 101 [1] can be implemented. The present document does not give restrictions on whether something is covered within a signature creation application or outside, as long as it is done by the SCASC. The present document gives no restrictions on the type of TSP implementing such a service component. The present document aims at supporting the creation of digital signatures in European and other regulatory frameworks. NOTE 1: Specifically, but not exclusively, the present document is aimed at trust services, supporting the creation of digital signatures in accordance with the requirements of the Regulation (EU) No 910/2014 [i.1] for electronic signatures and electronic seals (both advanced and qualified). Annex B contains specific requirements for SCASC in the context of Regulation (EU) No 910/2014 which aim at providing best practice requirements for the creation of advanced electronic signatures and seals based on X.509 certificates. NOTE 2: Specifically, but not exclusively, digital signatures in the present document can be used to create electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.1]. The present document may be used by competent bodies as the basis for confirming that an organization is trustworthy in creating AdES digital signatures. NOTE 3: See ETSI EN 319 403 [i.6] for guidance on assessment of TSP processes and services. The SCASC has connections with external (trust) services that can be contacted for example for provisioning information to be included within the signature. The present document does not put requirements on the trust service policy applied by such external services. The present document does not specify any protocol used to access the SCASC or how the SCACS can contact an SSASC or an SCDev. NOTE 4: Protocols to contact a SCASC or a SSASC are defined in ETSI TS 119 432 [i.9]. The present document identifies specific controls needed to address specific risks associated with services providing AdES signature creation.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
2 References
| |
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 119 101: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for applications for signature creation and signature validation". ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 8 [2] ETSI TS 119 102-1 (V1.2.1): "Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation". [3] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [4] ETSI EN 319 122-2: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 2: Extended CAdES signatures". [5] ETSI EN 319 132-1: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures". [6] ETSI EN 319 132-2: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 2: Extended XAdES signatures". [7] ETSI EN 319 142-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures". [8] ETSI EN 319 142-2: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 2: Additional PAdES signatures profiles". [9] ETSI EN 319 401: "Electronic Signatures and Infrastructures (ESI); General Policy Requirements for Trust Service Providers".
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Regulation (EU) No 910/2014 of the European Parliament and of the Council on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. [i.2] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.3] ETSI TS 119 172-1: "Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 1: Building blocks and table of contents for human readable signature policy documents". [i.4] EN 419241-1: "Trustworthy Systems Supporting Server Signing; Part 1: General System Security Requirements", produced by CEN. [i.5] ETSI TS 119 312: "Electronic Signatures and Infrastructures (ESI); Cryptographic Suites". [i.6] ETSI EN 319 403: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment - Requirements for conformity assessment bodies assessing Trust Service Providers". [i.7] ETSI EN 319 411-1: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 1: General requirements". [i.8] ETSI TS 119 431-1: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers; Part 1: TSP service components operating a remote QSCD / SCDev". [i.9] ETSI TS 119 432: "Electronic Signatures and Infrastructures (ESI); Protocols for remote digital signature creation". ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 9 [i.10] IETF RFC 3647: "Internet X.509 Public Key Infrastructure - Certificate Policy and Certification Practices Framework". 3 Definition of terms, symbols, abbreviations and notations
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TR 119 001 [i.2] and the following apply: AdES (digital) signature: digital signature that is either a CAdES signature, or a PAdES signature or a XAdES signature digital signature: data appended to, or a cryptographic transformation of a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g. by the recipient digital signature value: result of the cryptographic transformation of a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g. by the recipient remote signature creation device: signature creation device used remotely from signer perspective and provides control of signing operation on the signer's behalf server signing application: application using a remote signature creation device to create a digital signature value on behalf of a signer server signing application service component: TSP service component employing a server signing application server signing application service provider: TSP operating a server signing application service component signature applicability rules: set of rules, applicable to one or more digital signatures, that defines the requirements for determination of whether a signature is fit for a particular business or legal purpose NOTE: Signature applicability rules can be implicit, or can be stated in a human readable document and/or in a machine processable from. ETSI TS 119 172-1 [i.3] can be used for this purpose. signature creation application: application within the signature creation system that creates the AdES digital signature and relies on the SCDev to create a digital signature value NOTE: The SCDev can be managed by the SSASC. signature creation application service component: TSP service component employing a signature creation application signature creation application service provider: TSP operating a signature creation application service component signature creation constraint: criteria used when creating a digital signature signature creation device: configured software or hardware used to implement the signature creation data and to create a digital signature value signature creation policy: set of signature creation constraints processed or to be processed by the SCA signature creation service: TSP service implementing a signature creation application and/or a server signing application signature creation service provider: service provider offering a signature creation service NOTE: As in EN 419 241-1 [i.4]. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 10
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
3.2 Symbols
|
Void.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.2] and the following apply: CA Certification Authority DTBSR Data To Be Signed Representation OID Object IDentifier QES Qualified Electronic Signature or Qualified Electronic Seal SCA Signature Creation Application SCASC Signature Creation Application Service Component SCASP Signature Creation Application Service Provider SCDev Signature Creation Device SD Signer's Document SLA Service-Level Agreement SSASC Server Signing Application Service Component SSASP Server Signing Application Service Provider TSA Time-Stamping Authority URI Uniform Resource Identifier
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
3.4 Notations
|
The requirements identified in the present document include: a) requirements applicable to any TSP conforming to the present document. Such requirements are indicated by clauses without any additional marking; b) requirements applicable under certain conditions. Such requirements are indicated by clauses marked by "[CONDITIONAL]". The requirements in the present document are identified as follows: <the 3 letters identifying the elements of services > - < the clause number> - <2 digit number - incremental> The elements of services are: • OVR: General requirement (requirement applicable to more than 1 component) • ASI: AdES signing interface The management of the requirement identifiers for subsequent editions of the present document is as follows: • When a requirement is inserted at the end of a clause, the 2 digit number above is incremented to the next available digit. • When a requirement is inserted between two existing requirements, capital letters appended to the previous requirement identifier are used to distinguish new requirements. • The requirement identifier for a deleted requirements is left and completed with "VOID". • The requirement identifier for a modified requirement is left void and the modified requirement is identified by capital letter(s) appended to the initial requirement number. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 11
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
4 General concepts
| |
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
4.1 General policy requirements concepts
|
The present document is structured in line with ETSI EN 319 401 [9]. It incorporates ETSI EN 319 401 [9] requirements by reference and adds requirements relevant for a SCASP. See ETSI EN 319 401 [9], clause 4 for guidance for guidance on general policy requirements. 4.2 Signature creation application service component applicable documentation
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
4.2.1 Signature creation application service component practice statement
|
The Signature Creation Application Service Provider (SCASP) develops, implements, enforces, and updates a SCASC practice statement which is a trust service practice statement such as defined in ETSI EN 319 401 [9], instantiated for a signature creation application service component. See clause 6.1. The SCASC practice statement describes how the SCASP operates its service and is owned by the SCASP. The SCASC practice is tailored to the organizational structure, operating procedures, facilities, and computing environment of a TSP. The recipients of the practice statement can be auditors, subscribers and relying parties. NOTE: The presence of some elements is mandatory in the SCASC practice statement as requested in the present document, however the present document places no restriction on the form of the SCASC practice statement; it can be included in a general TSP practice statement document that covers other services delivered by that TSP or it can be a standalone document. Annex A provides a recommended table of content. The present document provides requirements identified as necessary to support a high-level SCASC policy, to be endorsed by a SCASP and reflected in its practice statement.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
4.2.2 Signature creation application service component policy
|
A SCASC policy describes what is offered and can contain diverse information beyond the scope of the present document to indicate the applicability of the service. A SCASC policy is defined independently of the specific details of the specific operating environment of a SSASP. The recipients of the service policy can be auditors, subscribers and relying parties. The present document can be referred by such a SCASC policy to provide information about the level of the service. SCASPs conforming to the present document's normative requirements except those defined in annex B may use in its documentation the following specific OID: itu-t(0) identified-organization(4) etsi(0) CREATION SERVICE-policies(19431) ades (2) policy-identifiers(1) main (1) SCASPs conforming to the present document's normative requirements including those defined in annex B may use in its documentation the following specific OID: itu-t(0) identified-organization(4) etsi(0) CREATION SERVICE-policies(19431) ades (2) policy-identifiers(1) eu-advanced- x509 (2) A SCASC policy is not necessarily part of the SCASP's documentation (as per ETSI EN 319 401 [9] a practice statement and general terms and conditions are sufficient); e.g. a SCASC policy can be shared by a community and not owned by the SCASP. Also, the present document does not put constraints on the form of the SCASC policies; a SCASC policy can be a stand-alone document or be provided as part of the practice statements and/or the general terms and conditions. The present document does not put any limitation on the content of the SCASC policies but it is requested that the SCASP provides minimal information about the service it offers (see clauses 6.1 and 6.2). ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 12
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
4.2.3 Terms and conditions
|
In addition to the SCASC practice statement and, when issued by the SCASP, the SCASC policy, the SCASP also issues terms and conditions, see clause 6.2. Terms and conditions can cover a broad range of commercial terms or technical terms that are not necessarily communicated to the customer, etc. The terms and conditions are specific to a SCASP. The recipients of the terms and conditions can be the subscribers and the relying parties. NOTE: The presence of some elements is mandatory in the terms and conditions as requested in the present document, however the present document places no restriction on the form of terms and conditions; it can be a standalone document for a public audience, or it can be split over subscriber's agreement(s) and information to relying parties. The form and content of the terms and conditions can also depend on national regulations.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
4.2.4 Other documents associated with signature creation
|
Besides the description of the practices employed by the SCASP to offer the AdES digital signature creation service, it is important to document the criteria under which the signatures are created and, beyond this, can then be determined as fitting a certain business need. Two documents can be used for these purposes: • A signature creation policy which is the set of signature creation constraints processed by the SCA. A signature creation policy can be identified by means of an OID. • Signature applicability rules that can be structured as per ETSI TS 119 172-1 [i.3] and can include a signature creation policy containing the signature creation constraints to be applied by the SCA, as well as other criteria showing the applicability of the created signature so certain business needs. NOTE: The use of signature applicability rules is outside the scope of the present document but can be applied as an extension to the signature creation service as covered by the present document. The SCASC practice statement, the signature creation policy and the signature applicability rules are different types of documentation; the SCASC practices statement describe how the SCASP operates its service, while the signature creation policy states the constraints to be processed by a SCA when creating a signature. Going beyond the scope of a signature creation policy, the signature applicability rules state the rules and assumptions used by a user to decide whether a signature created according to these rules is fit for purpose. The owner of the SCASC practice statement is a SCASP, while the owner of the signature applicability rules is usually the signatory.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
4.3 Architecture
|
A TSP service component supporting AdES digital signature creation (SCASC) receives the document(s) and/or hash(es) of document(s) to be signed and optionally some signing parameters, collects all necessary information to create the signature, prepares the Data To Be Signed Representation (DTBSR) and sends this to the SCDev. The SCDev can be either in the user's environment or managed by a remote Server Signing Application Service Component (SSASC) as described in ETSI TS 119 431-1 [i.8]. For the purpose of the present document, it is assumed that the SCDev handles the authentication and the agreement to sign with the user and returns the digital signature value, without going into details if this is done by the SCDev itself or the component managing the SCDev. The authorization to use the signing key within the SCDev can go through the SCASC but can also be done directly by communication between the signer and the SCDev. The digital signature value is included by the SCASC into the digital signature. NOTE: The SCASC represents the signature creation application in EN 419241-1 [i.4]. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 13 Figure 1: Relations of the TSP service component for AdES digital signature creation
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
5 Risk assessment
|
OVR-5-01: The requirements specified in ETSI EN 319 401 [9], clause 5 shall apply.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
6 Policies and practices
| |
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
6.1 Trust service practice statement
|
OVR-6.1-01:The requirements specified in ETSI EN 319 401 [9], clause 6.1 shall apply. In addition, the following particular requirements apply: OVR-6.1-02: [CONDITIONAL] When the SCASC supports the inclusion of time-stamp tokens in the AdES digital signature, the SCASC practice statement shall list which TSA are used. OVR-6.1-03: The SCASC practice statement shall specify all the supported signature creation polices. OVR-6.1-04: The SCASC practice statement shall specify all the supported signature formats. OVR-6.1-05: The SCASC practice statement shall specify all the supported signature classes. NOTE: ETSI TS 119 102-1 [2] describes different signature classes. OVR-6.1-06: The SCASP shall identify in the SCASC practice statements the obligations of all external organizations supporting its services including the applicable policies and practices.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
6.2 Terms and Conditions
|
OVR-6.2-01: The requirements specified in ETSI EN 319 401 [9], clause 6.2 shall apply. In addition, the following particular requirements apply: OVR-6.2-02: To specify the trust service policy being applied, the SCASC terms and conditions shall list or make reference to (e.g. through OIDs), and briefly describe, the supported SCASC policies it conforms to. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 14 OVR-6.2-03: To specify the trust service policy being applied, the SCASC terms and conditions may use the OIDs defined in clause 4.2.2. OVR-6.2-03A: [Conditional] If the SCASC terms and conditions reference a trust service policy using an OID other than the ones defined in clause 4.2.2, then the referenced trust service policy shall comply with requirements in clause 9. OVR-6.2-04: The main OID, as defined in clause 4.2.2, shall only be used in relation with an SCASC if the SCASC conforms to the normative requirements in the main part of the present standard (excluding annex B). OVR-6.2-05: The eu-advanced-x509 OID, as defined in clause 4.2.2, shall only be used in relation with an SCASC if the SCASC conforms to the normative requirements in the main part of the present standard and the ones in annex B. OVR-6.2-06: The terms and conditions shall indicate the rights and obligations of the SCASP and the signer. OVR-6.2-07: The terms and conditions shall describe the options supported by the service. At least: a) the supported signature formats; EXAMPLE: CAdES [3], [4], XAdES [5], [6] or PAdES [7], [8]. b) the supported signature parameters; c) if the to be signed document can be provided only as a hash; and d) the supported Signature Creation Devices (SCDev) in the user's environment or the supported SSASCs creating the digital signature value for the signer. OVR-6.2-08: The terms and conditions shall include Service-Level Agreement (SLA) elements for the availability of the service and when applicable, other SLA information such as response times. OVR-6.2-09: The terms and conditions shall provide a notice that the SLA can be affected by the practices, policies and SLAs of other TSPs, not under the control of the SCASP like the CA issuing the certificate used for the signature or a TSA used for a time-stamp. OVR-6.2-10: The terms and conditions shall explain how the SCASP processes personal data.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
6.3 Information security policy
|
OVR-6.3-01: The requirements specified in ETSI EN 319 401 [9], clause 6.3 shall apply. In addition, the following particular requirement apply: OVR-6.3-02: The security policy should document the security and privacy controls implemented to protect personal data. NOTE: If the SCASP has access to the data-to-be-signed, then this can contain confidential information as well as personal data. 7 Signature creation application service management and operation
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.1 Internal organization
|
OVR-7.1-01: The requirements specified in ETSI EN 319 401 [9], clause 7.1 shall apply. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 15
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.2 Human resources
|
OVR-7.2-01: The requirements specified in ETSI EN 319 401 [9], clause 7.2 shall apply.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.3 Asset management
|
OVR-7.3-01: The requirements specified in ETSI EN 319 401 [9], clause 7.3 shall apply.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.4 Access control
|
OVR-7.4-01: The requirements specified in ETSI EN 319 401 [9], clause 7.4 shall apply.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.5 Cryptographic controls
|
OVR-7.5-01: The requirements specified in ETSI EN 319 401 [9], clause 7.5 shall apply.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.6 Physical and environmental security
|
OVR-7.6-01: The requirements specified in ETSI EN 319 401 [9], clause 7.6 shall apply. In addition the following particular requirement apply: OVR-7.6-02: The following requirement specified in ETSI TS 119 101 [1], clause 5.2 shall apply to the SCA: GSM 1.4.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.7 Operation security
|
OVR-7.7-01: The requirements specified in ETSI EN 319 401 [9], clause 7.7 shall apply. In addition, the following particular requirements apply: OVR-7.7-02: The following requirements specified in ETSI TS 119 101 [1], clause 5.2 should apply to the SCA: GSM 1.2 and GSM 1.3. OVR-7.7-03: The following requirements specified in ETSI TS 119 101 [1], clause 5.2 shall apply to the SCA: GSM 2.4. OVR-7.7-04: The SCASC shall implement all mandatory requirements from ETSI TS 119 101 [1] referenced above regardless of whether the requirement is imposed on the DA or the SCA.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.8 Network security
|
OVR-7.8-01: The requirements specified in ETSI EN 319 401 [9], clause 7.8 shall apply.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.9 Incident management
|
OVR-7.9-01: The requirements specified in ETSI EN 319 401 [9], clause 7.9 shall apply. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 16
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.10 Collection of evidence
|
OVR-7.10-01: The requirements specified in ETSI EN 319 401 [9], clause 7.10 shall apply. In addition the following particular requirements apply: OVR-7.10-02: Any AdES digital signature creation operation shall be logged, together with identification of the subscriber when this information is known. OVR-7.10-03: Event logs shall be marked with the time of the event. OVR-7.10-04: The frequency of processing, the retention period, the protection, the back-up procedures of the collection system, the archiving procedures and the vulnerability assessment of the event logs shall be documented in the SCASC practice statement. OVR-7.10-05: The implementation of requirements OVR-7.10.1 and OVR-7.10.2 shall take the applicable privacy requirements into account. OVR-7.10-06: Event logs should include the type of the event, the event success or failure, and an identifier of the person and/or component at the origin for such an event.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.11 Business continuity management
|
OVR-7.11-01: The requirements specified in ETSI EN 319 401 [9], clause 7.11 shall apply. In addition, in order to provide business continuity as specified in the terms and conditions the following particular requirements apply: OVR-7.11-02: Measures should be implemented to avoid interruptions of the service due to intentional or unintentional behaviour of users or third parties. OVR-7.11-03: [CONDITIONAL] When adding time-stamps to the signature, the SLA of the SCASP should take the SLA of the corresponding TSA into account.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.12 Termination and termination plans
|
OVR-7.12-01: The requirements specified in ETSI EN 319 401 [9], clause 7.12 shall apply.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
7.13 Compliance and legal requirements
|
OVR-7.13-01: The requirements specified in ETSI EN 319 401 [9], clause 7.13 shall apply. In addition, the following particular requirements apply: OVR-7.13-02: When personal data is processed by a third party, if needed by the law, an appropriate agreement shall be made with third party processors of personal data in order to ensure that they do comply with the legal requirements, including the implementation of technical, organizational and legal measures to protect the personal data. NOTE 1: The data to be signed is to be considered as personal data. OVR-7.13-03: The SCASC shall not store the SD after processing when not necessary. NOTE 2: If the SCASP works in combination of a preservation service there can be a need to keep such data. OVR-7.13-04: The SCASP shall have the overall responsibility for meeting the requirements defined in clauses 5 to 8 even when some or all of its functionalities are undertaken by sub-contractors. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 17 8 Signature creation application service component technical requirements
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
8.1 Interface
|
ASI-8.1-01: [CONDITONAL] When the SCASC has a machine accessible interface to contact its service, it should use the protocol defined in ETSI TS 119 432 [i.9]. ASI-8.1-02: The connection between the SCASC and the SCDev used for creation of the digital signature value shall be secured. ASI-8.1-03: [CONDITIONAL] When the SCASC presents the document to the signer, it shall describe in its SCASC practice statement how it guarantees that What You See Is What You Sign (WYSIWYS). ASI-8-1-04: [CONDITIONAL] When the SCASC presents the document to the signer in an interpreted way, the SCASC practice statement shall clearly state how it interprets specific data. EXAMPLE: The document to be signed is XML format, and the practice statement states which software is used for the presentation or which rules are followed to present the different XML tags. ASI-8.1-05: [CONDITIONAL] When the SCASC presents the document to the signer, the SCASC practice statement or the terms and conditions shall state which content types can be correctly presented. ASI-8.1-06: [CONDITIONAL] When the SCASC presents the document to the signer, the interface shall warn the signer if it cannot accurately present all parts of the SD according to the data content type. ASI-8.1-07: [CONDITIONAL] When the SCASC provides a graphical user interface to the client the requirements UI 1 and UI 2 from ETSI TS 119 101 [1] should apply. ASI-8.1-08: [CONDITIONAL] When the SCASC presents the document to the signer, it shall have a workflow where it is clear to the signer that the signer consents to the signing of the document. ASI-8.1-09: [CONDITIONAL] When the SCASC presents the document to the signer, SCP 13 and SCP 47 of ETSI TS 119 101 [1] shall apply. ASI-8.1-10: [CONDITIONAL] When the SCASC presents the document to the signer, the SCASC should allow to download the document to be signed. ASI-8.1-11: [CONDITIONAL] When the SCASC presents the document to the signer, the SCASC should log for how long the document was presented to the signer. ASI-8.1-12: [CONDITIONAL] When the SCASC presents the document to the signer and the document was downloaded, the SCASC should log such an event.
|
d86c5459bf5f4537ffa4ea5784f295e0
|
119 431-2
|
8.2 AdES digital signature creation
|
OVR-8.2-01: The SCASC shall guarantee the integrity and confidentiality of the received information. OVR-8.2-02: The cryptographic algorithms used should be selected from algorithms recommended by ETSI TS 119 312 [i.5]. NOTE 1: Cryptographic suites recommendations defined in ETSI TS 119 312 [i.5] can be superseded by national recommendations. OVR-8.2-03: The cryptographic algorithms applied shall be as defined in signature creation policy. OVR-8.2-04: SCP 14, SCP 31, SCP 37 and SCP 61 of ETSI TS 119 101 [1] shall apply. OVR-8.2-05: The SCASC shall inform the signer of the commitment type. NOTE 2: This information can be given within the signature policy. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 18 OVR-8.2-06: The SCASC should include the signing certificate chain into the signature. OVR-8.2-07: The signer shall be able to know which signature creation policy will be applied. OVR-8.2-08: The signer shall be able to know which signature creation policy was applied when creating a specific the signature. EXAMPLE 1: The information on which signature creation policy will or was applied for a specific signature can be known from the user account of the signer. EXAMPLE 2: The signature creation policy can be added as a signed attribute to the signature. EXAMPLE 3: The SCASP has only one signature creation policy in force at each time, and from the time of signature it is clear which version applies. OVR-8.2-08A: The SCASC should provide the signature to the signer. OVR-8.2-09: [CONDITIONAL] If the SCASC has access to the signed data, it should provide the signed data together with the signature to the signer. NOTE 3: In case the signature is enveloped in or enveloping the signed data, OVR-8.2-09 follows directly from OVR-8.2-08A. 9 Framework for definition of signature creation application service component policy built on a trust service policy defined in the present document NOTE: The TSP can use directly the trust service policies identified in clause 4.2.2, or the TSP can reference a trust service policy that is based on the policies identified in clause 4.2.2 but adds additional requirements or additional constraints to the requirements of the present document. The latter case is described as the SCASC policy being built on a trust service policy defined in the present document. OVR-9-01: Void. OVR-9-01A: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document, the SCASC policy shall identify which of the trust service policies defined in the present document it adopts as the basis. OVR-9-02: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document; the policy shall identify any variances it chooses to apply. OVR-9-03: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document; subscribers shall be informed, as part of implementing the terms and conditions, of the ways in which the specific policy adds to or further constrains the requirements of the policy as defined in the present document. OVR-9-04: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document; there shall be a body (e.g. a policy management authority) with final authority and responsibility for specifying and approving the policy. OVR-9-05: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document; a risk assessment should be carried out to evaluate business requirements and determine the security requirements to be included in the policy for the stated community and applicability. OVR-9-06: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document; the policy shall be approved and modified in accordance with a defined review process, including responsibilities for maintaining the policy. OVR-9-07: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document; a defined review process shall exist to ensure that the policy is supported by the practices statements. OVR-9-08: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document; the TSP should make available the policies supported by the TSP to its user community. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 19 OVR-9-09: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document; revisions to policies supported by the TSP should be made available to subscribers. OVR-9-10: [CONDITIONAL] When building a SCASC policy on a trust service policy defined in the present document; a unique object identifier shall be obtained for the policy (e.g. OID or URI). ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 20 Annex A (informative): Table of contents for SCASC practice statement 1. Introduction 1.1 Overview 1.1.1 TSP identification 1.1.2 Supported signature creation application service component policy/policies (formal OID/URI identification) 1.2 Signature creation application service component environment 1.2.1 SCASC actors 1.2.3 Service architecture 1.3 Definitions and abbreviations 1.3.1 Definitions 1.3.2 Abbreviations 1.4 Policies and practices 1.4.1 Organization administrating the TSP documentation 1.4.2 Contact person 1.4.3 TSP (public) documentation applicability This clause describes the set of documents related to the SCASC, their applicability, and position of the present practice statement within the documentation, their distribution points. At a minimum the following documents exist and need a short description: • the present practice statement (formal OID/URI identification should be used) • the terms and conditions • the service policy (can be referred) one or more of the above documents identify the supported signature creation policy/policies (with formal OID/URI identification). The supported signature creation policy/policies are generally detailed in the SCASC service policy/policies. • risk assessment and Information security policy NOTE: The description of any business (application) domain or any transactional context can be described in a "signature applicability rules" document. There is no obligation for a TSP to support and publish signature applicability rules. 2. Trust Service management and operation This clause may be common to all services offered by the TSP - except for CA services where the table of content described by IETF RFC 3647 [i.10] should be applied. (Either the same clause is reproduced for each service practice statement, in which case, because every service policy and security requirements add elements specific to the services, such requirements need to be addressed in addition, OR there is a common clause that is referred to from each service practice statement). ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 21 2.1 Internal organization 2.1.1 Organization reliability (This clause identifies the obligations of all external organizations supporting the TSP services including the applicable policies and practices (per ETSI EN 319 401 [9]) 2.1.2 Segregation of duties 2.2 Human resources 2.3 Asset management 2.3.1 General requirements 2.3.2 Media handling 2.4 Access control 2.5 Cryptographic controls 2.6 Physical and environmental security 2.7 Operation security 2.8 Network security 2.9 Incident management 2.10 Collection of evidence 2.11 Business continuity management 2.12 TSP termination and termination plans 2.13 Compliance 3. Signature creation application service component technical requirements 3.1 Interfaces This clause contains requirements, control objectives and controls in connection with clause 8.1 in ETSI TS 119 431-2 (the present document). 3.2 AdES digital signature creation This clause contains requirements, control objectives and controls in connection with clause 8.2 in ETSI TS 119 431-2 (the present document). ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 22 Annex B (normative): EU specific requirements related to Regulation (EU) No 910/2014 for creation of advanced electronic signatures and seals based on X.509 certificates NOTE: This clause aims at providing best practices for the creation of advanced electronic signatures/seals based on X.509 certificates. OVR-B.1-01: [CONDITONAL] Where the SCASC is used to create an advanced electronic signature, the signing certificate shall identify the signatory. OVR-B.1-02: [CONDITONAL] Where the SCASC is used to create an advanced electronic seal, the signing certificate shall identify the creator of the seal. OVR-B.1-03: The signing certificate shall be contained in the created AdES signature. ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 23 Annex C (informative): Mapping to advance electronic signatures or seals as by Regulation (EU) No 910/2014 Table C.1 maps the requirements from the present document with the requirements on advanced electronic signatures or seals as specified directly by Regulation (EU) No 910/2014 [i.1], Tables 1 and 2 or indirectly via requirements on valid QES as specified by Regulation (EU) No 910/2014 [i.1], Table 3. Table C.1: Mapping of the requirements in the present document to requirements for advanced electronic signatures as defined by Regulation (EU) No 910/2014 Regulation (EU) No 910/2014 Applicable requirements Article 26 Requirements for advanced electronic signatures "An advanced electronic signature shall meet the following requirements: (a) it is uniquely linked to the signatory; OVR-B.1-01 OVR-8.2-04 referencing from ETSI TS 119 101 [1] SCP 37: "The SCA shall protect the reference to or copy of the signing certificate within the signature from undetected replacement after the signature has been created." (b) it is capable of identifying the signatory; OVR-B.1-03 (c) it is created using electronic signature creation data that the signatory can, with a high level of confidence, use under his sole control; and The sole control is out of scope of the present document. If a SSASC is used, this is covered in ETSI TS 119 431-1 [i.8]. See note. (d) it is linked to the data signed therewith in such a way that any subsequent change in the data is detectable." OVR-8.2-02 The cryptographic algorithms used should be selected from algorithms recommended by ETSI TS 119 312 [i.5]. NOTE: The SSASC can limit the list of supported SCDev in its terms and conditions (OVR-6.2-05). Table C.2: Mapping of the requirements in the present document to requirements for advanced electronic seals as defined by Regulation (EU) No 910/2014 Regulation (EU) No 910/2014 Applicable requirements Article 36 Requirements for advanced electronic seals "An advanced electronic seal shall meet the following requirements: (a) it is uniquely linked to the creator of the seal; OVR-B.1-02 OVR-8.2-04 referencing from ETSI TS 119 101 [1] SCP 37 (b) it is capable of identifying the creator of the seal; OVR-B.1-03 (c) it is created using electronic seal creation data that the creator of the seal can, with a high level of confidence under its control, use for electronic seal creation; and The sole control is out of scope of the present document. If a SSASC is used, this is covered in ETSI TS 119 431-1 [i.8]. See note. (d) it is linked to the data to which it relates in such a way that any subsequent change in the data is detectable." OVR-8.2-04 referencing from ETSI TS 119 101 [1] SCP 14 NOTE: The SSASC can limit the list of supported SCDev in its terms and conditions (OVR-6.2-05). ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 24 Table C.3: Mapping of the requirements in the present document to requirements that have to be fulfilled for a valid advanced electronic signature/seal as defined by Regulation (EU) No 910/2014 Regulation (EU) No 910/2014 Applicable requirements Article 32.1 Requirements for the validation of qualified electronic signatures "1. The process for the validation of a qualified electronic signature shall confirm the validity of a qualified electronic signature provided that: (a) the certificate that supports the signature was, at the time of signing, a qualified certificate for electronic signature complying with Annex I; Not applicable, specific to the qualified case (b) the qualified certificate was issued by a qualified trust service provider and was valid at the time of signing; Not applicable, specific to the qualified case (c) the signature validation data corresponds to the data provided to the relying party; Not applicable, this is the responsibility of the CA and the SSASC (d) the unique set of data representing the signatory in the certificate is correctly provided to the relying party; Not applicable, this is the responsibility of the CA (e) the use of any pseudonym is clearly indicated to the relying party if a pseudonym was used at the time of signing; Not applicable, this is the responsibility of the CA (f) the electronic signature was created by a qualified electronic signature creation device; Not applicable, specific to the qualified case (g) the integrity of the signed data has not been compromised; OVR-8.2-02 (h) the requirements provided for in Article 26 were met at the time of signing." See table C.1 ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 25 Annex D (informative): Change history Date Version Information about changes December 2018 1.1.1 Publication April 2023 1.1.2 Implementation of • CR#1: clarification of chapter 9 service component policy built on the present document Mai 2023 1.1.3 Minor editorial changes after discussion during ESI#80 ETSI ETSI TS 119 431-2 V1.2.1 (2023-06) 26 History Document history V1.1.1 December 2018 Publication V1.2.1 June 2023 Publication
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
1 Scope
|
The present document specifies generally applicable policy and security requirements for Trust Service Providers (TSPs) operating a remote Signature Creation Device (SCDev). Specific requirements apply when the device is a remote QSCD as defined in Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. The service consists of a server signing application and a QSCD / SCDev. The term used in the present document is Server Signing Application Service (SSAS). NOTE 1: Regulation (EU) 2024/1183 [i.11] (eIDASv2) defines the management of remote electronic signature/seal creation devices as a trust service. In addition, it introduces the qualified trust service for the management of remote qualified electronic signature/seal creation devices. The policy and security requirements are defined in terms of requirements for creation, maintenance, life-cycle management and use of signing keys used to create digital signatures. The present document is aimed to be used by independent bodies as the basis for a conformity assessment that a TSP can be trusted for operating a remote QSCD / SCDev. [i.1]. The present document supports European and other regulatory frameworks. NOTE 2: Specifically, but not exclusively, the present document is aimed at qualified and non-qualified trust service managing remote qualified and non-qualified electronic signature/seal creation devices supporting electronic signatures and electronic seals (both advanced and qualified) in accordance with the requirements of Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. Annex A contains requirements specific for an SSAS in the context of Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. The present document does neither specify how fulfilment of the requirements can be assessed by an independent conformity assessment body, nor requirements for information to be made available to such independent assessors, or requirements on such assessors. NOTE 3: See ETSI EN 319 403 [i.3] for guidance on assessment of a TSP's processes and services. NOTE 4: The present document references ETSI EN 319 401 [1] for general policy requirements common to all TSP services covered by ETSI standards. The present document does not specify protocols used to access the SSAS. NOTE 5: Protocols for remote digital signature creation are defined in ETSI TS 119 432 [i.4]. The present document identifies specific controls needed to address risks associated with services operating remote QSCD / SCDev.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
2 References
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 8 The following referenced documents are necessary for the application of the present document. [1] ETSI EN 319 401: "Electronic Signatures and Trust Infrastructures (ESI); General Policy Requirements for Trust Service Providers". [2] ETSI EN 319 411-1: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 1: General requirements". [3] EN 419241-1: "Trustworthy Systems Supporting Server Signing - Part 1: General System Security Requirements", (produced by CEN). [4] EN 419241-2: " Trustworthy Systems Supporting Server Signing - Part 2: Protection profile for QSCD for Server Signing", (produced by CEN). [5] EN 419221-5: "Protection Profiles for TSP Cryptographic Modules - Part 5: Cryptographic Module for Trust Services", (produced by CEN). [6] ETSI TS 119 461: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for trust service components for identity proofing of trust service subjects".
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. [i.2] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.3] ETSI EN 319 403: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Part 1: Requirements for conformity assessment bodies assessing Trust Service Providers". [i.4] ETSI TS 119 432: "Electronic Signatures and Infrastructures (ESI); Protocols for remote digital signature creation". [i.5] IETF RFC 3647: "Internet X.509 Public Key Infrastructure - Certificate Policy and Certification Practices Framework". [i.6] ISO/IEC 15408: "Information technology — Security techniques — Evaluation criteria for IT security". [i.7] ISO/IEC 18014-2: "Information technology — Security techniques — Time-stamping services — Part 2: Mechanisms producing independent tokens". [i.8] Void. [i.9] Void. [i.10] ETSI TS 119 431-2: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers; Part 2: TSP service components supporting AdES digital signature creation". ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 9 [i.11] Regulation (EU) 2024/1183 of the European Parliament and of the Council of 11 April 2024 amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity Framework. [i.12] Commission Implementing Decision (EU) 2016/650 of 25 April 2016 laying down standards for the security assessment of qualified signature and seal creation devices pursuant to Articles 30(3) and 39(2) of Regulation (EU) No 910/2014 of the European Parliament and of the Council on electronic identification and trust services for electronic transactions in the internal market (Text with EEA relevance). 3 Definition of terms, symbols, abbreviations and notations
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TR 119 001 [i.2] and the following apply: NOTE: Where a definition is copied from a referenced document this is indicated by inclusion of the reference identifier number at the end of the definition or in a note. authentication: provision of assurance in the claimed identity of an entity NOTE: As defined in ISO/IEC 18014-2 [i.7]. digital signature value: result of the cryptographic transformation of a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g. by the recipient electronic identification (eID): process of using person identification data in electronic form uniquely representing either a natural or legal person, or a natural person representing a legal person NOTE: As defined in Regulation (EU) No 910/2014 [i.1]. electronic identification means: material and/or immaterial unit containing person identification data and which is used for authentication for an online service NOTE: As defined in Regulation (EU) No 910/2014 [i.1]. electronic identification means reference: data used in the SSAS as a reference to an electronic identification means in order to authenticate the signer EXAMPLE: When the eID means uses asymmetric keys, the public key can be the reference. When a signed assertion is generated after a successful authentication of the signer, the assertion signer id and the user id can be the reference. When the eID means uses a secret key (e.g. one time password generator) the secret key can be the reference. one-time signing key: signing key bound, certified, used and disposed based on a single authorization, linked to a single session signing DTBS/R(s) NOTE 1: The definition is slightly different from the one in EN 419241-2 [4] to allow the usage of pre-generated signing keys. NOTE 2: Contrary to general signing keys, which may be used in several signing sessions. person identification data: set of data enabling the identity of a natural or legal person, or a natural person representing a legal person to be established. NOTE: As defined in Regulation (EU) No 910/2014 [i.1]. Qualified electronic Signature/seal Creation Device (QSCD): As specified in Regulation (EU) No 910/2014 [i.1]. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 10 Remote QSCD: As specified in Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. remote signature creation device: signature creation device used remotely from signer perspective and provides control of signing operation on the signer's behalf Server Signing Application Service (SSAS): trust service consisting of a server signing application and a QSCD / SCDev to create a digital signature value on behalf of a signer Server Signing Application Service Provider (SSASP): TSP operating a server signing application service component Signature Creation device (SCDev): configured software or hardware used to implement the signature creation data and to create a digital signature value trust service: electronic service that enhances trust and confidence in electronic transactions Trust Service Provider (TSP): entity which provides one or more trust service
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
3.2 Symbols
|
Void.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: CA Certificate Authority CID Commission Implementing Decision DTBS/R Data To Be Signed Representation eID electronic IDentification EUDI wallet European Digital Identity wallet EUSPv2 EU SSAS Policy LSP Lightweight SSAS Policy NSP Normalized SSAS Policy OID Object IDentifier PIN Personal Identification Number QSCD Qualified electronic Signature/Seal Creation Device SAD Signature Activation Data SAM Signature Activation Module SAP Signature Activation Protocol SCDev Signature Creation Device SP SSAS Policy SSAS Server Signing Application Service SSASP Server Signing Application Service Provider TSP Trust Service Provider URI Uniform Resource Identifier
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
3.4 Notations
|
The requirements identified in the present document include: a) requirements applicable to any SSAS policies. Such requirements are indicated by clauses without any additional marking; b) requirements applicable under certain conditions. Such requirements are indicated by clauses marked by "[CONDITIONAL]"; c) requirements that include several choices which ought to be selected according to the applicable situation. Such requirements are indicated by clauses marked by "[CHOICE]"; ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 11 d) requirements applicable to the services offered under the applicable SSAS policy. Such requirements are indicated by clauses marked by the applicable SSAS policy as follows: - "[LSP]", "[NSP]" and "[EUSPv2]". The requirements in the present document are identified as follows: • <3 letters service component> - < the clause number> - <2 digit number - incremental> The SSAS service components are: • OVR: General requirement (requirement applicable to more than 1 service component) • GEN: Signing Key Generation Service • LNK: Certificate/eID means Linking Service • SIG: Signature Activation Service • DEL: Signing Key Deletion Service • EID: eID Means Provision (optional) The management of the requirement identifiers throughout subsequent editions of the present document is as follows: • When a requirement is inserted at the end of a clause, the 2 digit number above is incremented to the next available digit. • When a requirement is inserted between two existing requirements, capital letters appended to the previous requirement identifier are used to distinguish a new requirement. • The requirement identifier for deleted requirements are left and completed with "Void". • The requirement identifier for modified requirement are left void and the modified requirement is identified by capital letter(s) appended to the initial requirement number.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
4 General concepts
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
4.1 General policy requirements concepts
|
The present document is structured broadly in line with ETSI EN 319 411-1 [2] to assist TSPs in applying these requirements to their own policy and practice statement documentation. The present document incorporates EN 419241-1 [3] requirements by reference. EN 419241-1 [3] defines levels of assurance for sole control. The term "sole control" does not mean that the requirements are only applicable to electronic signatures as defined in Regulation (EU) No 910/2014 [i.1]. The requirements may be applied mutatis mutandis to electronic seals. In other words, the reader may replace the term "sole control" with "control" as explained in EN 419241-1 [3] clause 5.3. NOTE 1: Any applicable and referenced requirements on the Trustworthy System Supporting Server Signing (TW4S) in EN 419241-1 [3] is a requirement on the SSAS. The present document incorporates ETSI EN 319 401 [1] requirements by reference and adds requirements relevant for a SSASP. See ETSI EN 319 401 [1], clause 4 and IETF RFC 3647 [i.5], clauses 3.1 and 3.4 for guidance. The requirements are indicated in terms of the security objectives followed by more specific requirements for controls to meet those objectives where considered necessary to provide the necessary confidence that those objectives will be met. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 12 NOTE 2: The details of controls required to meet an objective is a balance between achieving the necessary confidence whilst minimizing the restrictions on the techniques that a TSP can employ in operating signing devices. In some cases, reference is made to other more general standards which can be used as a source of more detailed control requirements. Due to these factors the specificity of the requirements given under a given topic can vary. The present document includes the provision of services for key generation, certificate linking, eID means linking, signature activation, key deletion and device provisioning (see clause 4.4).
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
4.2 Void
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
4.3 SSAS applicable documentation
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
4.3.1 SSAS practice statement
|
The Server Signing Application Service Provider (SSASP) develops, implements, enforces, and updates a SSAS practice statement, which is a trust service practice statement as defined in ETSI EN 319 401 [1], instantiated for a SSAS. See clause 6.1. The SSAS practice statement describes how the SSASP operates its service and is owned by the SSASP. The SSAS practice is tailored to the organizational structure, operating procedures, facilities, and computing environment of a TSP. The recipients of the practice statement can be auditors, subscribers and relying parties. NOTE: The presence of some elements is mandatory in the SSAS practice statement as requested in the present document, however the present document places no restriction on the form of the SSAS practice statement; it can be included in a general TSP practice statement document that covers other services delivered by that TSP or be a standalone document. The present document provides requirements identified as necessary for SSAS policies defined in clause 4.3.2, to be endorsed by a SSASP and reflected in its practice statement.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
4.3.2 SSAS policy
|
A SSAS Policy (SP) describes what is offered and can contain diverse information beyond the scope of the present document to indicate the applicability of the SSAS. A SP is defined independently of the specific details of the specific operating environment of a SSASP. The recipients of the SP can be auditors, subscribers and relying parties. The present document defines three SPs: 1) A Lightweight SSAS Policy (LSP) offering a quality of service less onerous than the NSP (requiring less demanding policy requirements) for use where a risk assessment does not justify the additional burden of meeting all requirements of the NSP (e.g. use of a signature activation module). 2) A Normalized SSAS Policy (NSP) which meets general recognized best practice for TSPs operating a remote SCDev used in support of any type of transaction. 3) An EU SSAS v2 Policy (EUSPv2) which offers the same quality as that offered by the NSP but with specific requirements from the Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1] related to remote QSCD management. NOTE: EUSPv2 specific requirements are defined in Annex A. A SP is not necessarily part of the SSASP's documentation (as per ETSI EN 319 401 [1] a practice statement and general terms and conditions are sufficient); e.g. a SP can be shared by a community and not owned by the SSASP. Also, the present document does not put constraints on the form of the SP; a SP can be a stand-alone document or be provided as part of the practice statement and/or the general terms and conditions. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 13
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
4.3.3 Terms and conditions
|
In addition to, or as part of, the SCP and the SSAS practice statement, a TSP issues terms and conditions. Terms and conditions can cover a broad range of commercial terms or technical terms. The terms and conditions are specific to a SSASP. The recipients of the terms and conditions are subscribers and relying parties. NOTE: The presence of some elements is mandatory in the terms and conditions as requested in the present document, however the present document places no restriction on the form of terms and conditions; it can be a standalone document for a public audience, or it can be split over subscriber's agreement(s) and information to relying parties. The form and content of the terms and conditions can also depend on national regulations.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
4.4 SSAS component services
|
NOTE 1: The present document does not mandate any subdivision of the services of a TSP. Requirements are stated in subsequent clauses. The SSAS services are broken down in the present document into the following component services for the purposes of classifying requirements: • Signing key generation service: generates signing keys in the remote device. The proof of possession of generated signing keys are passed to the registration service of the TSP issuing the associated certificate. • Certificate linking service: links the certificates generated by the certificate generation service of a TSP with the corresponding signing keys. • eID means / identity linking service: links either an eID means references or an identity with the corresponding signing keys in order to provide sole control. The second possibility is only applicable in case of a one-time signing key where it is assured that the identity in the certificate is the same as the one of the signer. The service can be used to support requirement REG-6.3.1-01 in ETSI EN 319 411-1 [2] for a TSP issuing certificates. EXAMPLE 1: By providing an assertion of the authentication of the signer that is linked to the private key. • Signature activation service: verifies the signature activation data and activates the corresponding signing key in order to create a digital signature. • Signing key deletion service: destroys signing keys in a way that ensures that the signing keys cannot be used anymore. • eID means provision service (optional): prepares and provides or makes eID means available to the signers. EXAMPLE 2: A service which generates the authentication key and distributes the key to the subject of the certificate (this includes "soft" keys i.e. keys protected by software environment). A service which prepares the authentication device and enabling codes, and distributes them to the subject of the certificate (this includes keys protected by hardware environment). This subdivision of services is only for the purposes of clarification of policy requirements and places no restrictions on any subdivision of an implementation of the TSP's services. Figure 1 illustrates the interrelationships between the service components of the present document and relations with external components of the TSP issuing the signing certificates. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 14 Figure 1: Illustration of subdivision of SSAS components Figure 2 illustrates the interrelationships between the services of the present document and relations with an authentication process delegated to an external party. Figure 2: Illustration of subdivision of SSAS components with delegated authentication ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 15 Figure 3: Illustration of subdivision of SSAS components for one-time signing keys with identity proofing without usage of eID means NOTE 2: In the case of a one-time signing key, the key is deleted directly after the usage, not based on a revocation. The CA can still provide a revocation service and certification status service, but they are not linked to the (Q)SCD management anymore. NOTE 3: Figures 1, 2 and 3 are for illustrative purposes and do not show a processing flow. Clause 6 specifies the specific requirements for each of the services. 5 General provisions on practice statement and policies
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
5.1 Practice statement requirements
|
OVR-5.1-01: The general requirements specified in ETSI EN 319 401 [1], clause 6.1 shall apply. In addition, the following particular requirements apply: NOTE 1: A TSP can document practices relating to specific SSAS policy requirements separate from the main practice statement document. OVR-5.1-02: The TSP's practice statement shall include the signature algorithms and parameters applied, the algorithms applied for key pair generation and any other algorithms and parameters that are critical to the security of the SSAS operation. OVR-5.1-03: The TSP shall publicly disclose its practice statement through an online means that is available on a 24×7 basis. NOTE 2: The TSP is not obliged to disclose any aspects containing sensitive information. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 16
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
5.2 SP name and identification
|
SSASPs following the present document can claim conformance to the present document via the following specific trust service policy OID: a) LSP: Lightweight SSAS Policy itu-t(0) identified-organization(4) etsi(0) SIGNATURE CREATION SERVICE-policies(19431) ops (1) policy-identifiers(1) lightweight (1) b) NSP: Normalized SSAS Policy itu-t(0) identified-organization(4) etsi(0) SIGNATURE CREATION SERVICE-policies(19431) ops(1) policy-identifiers(1) normalized (2) NOTE: Annex A defines an additional SSAS policy with specific requirements related to Regulation (EU) No 910/2014 [i.1]. OVR-5.2-01: If any changes are made to a SP as described in clause 4.3.2 which affects the applicability then the policy identifier should be changed.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
5.3 Participants
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
5.3.1 SSASP
|
OVR-5.3.1-01: The SSASP may make use of other parties to provide parts of the service, however, the SSASP always maintains overall responsibility and shall ensure that the policy requirements identified in the present document are met. NOTE: If the external party uses an eID means issued under a notified scheme that is included in the list published by the Commission pursuant to Article 9 of Regulation (EU) No 910/2014 [i.1], there is no need to demonstrate the conformance to the required level, conformance to the regulatory requirements can be assumed.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
5.3.2 Subscriber and signer
|
In the framework of the present policies, the signer associated to the signing key can be: • a natural person; • a natural person identified in association with a legal person; • a legal person (that can be an organization or a unit or a department identified in association with an organization); or • a device or system operated by or on behalf of a natural or legal person. NOTE: The present document does not place any specific restrictions on the legal representation implied by an electronic signature or seal created using the present document. The relationship between the signer and the subscriber is equivalent to the relationship between subject and subscriber as described in ETSI EN 319 411-1 [2], clause 5.4.2.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6 Trust Service Providers practice
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.1 Publication and repository responsibilities
|
OVR-6.1-01: The TSP shall make available to subscribers and relying parties the applicable SPs, practice statements and terms and conditions regarding the use of signing keys. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 17 OVR-6.1-02: The applicable terms and conditions shall be readily identifiable for a given signing key or for the associated certificate. OVR-6.1-03: The information identified in OVR-6.1-01 and OVR-6.1-02 above shall be available 24 hours per day, 7 days per week. Upon system failure, service or other factors which are not under the control of the TSP, the TSP shall apply best endeavours to ensure that this information service is not unavailable for longer than a maximum period of time as denoted in the SSAS practice statement. OVR-6.1-04: The information identified in OVR-6.1-01 above should be publicly and internationally available.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.2 Signing key initialization
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.2.1 Signing key generation
|
GEN-6.2.1-01 [LSP]: Clause SRG_KM.1.1 of EN 419241-1 [3], specifying signing keys environment, shall apply. GEN-6.2.1-02 [NSP]: Clause SRA_SKM.1.1 of EN 419241-1 [3], specifying signing keys environment, shall apply. GEN-6.2.1-02A [NSP]: Signer's signing key shall be generated and used in a SCDev certified conformant to EN 419221-5 [5]. GEN-6.2.1-03: Clause SRG_KM.1.2 of EN 419241-1 [3], specifying cryptographic algorithms and key lengths, shall apply. GEN-6.2.1-04: Clause SRG_KM.1.3 of EN 419241-1 [3], specifying key protection, shall apply. GEN-6.2.1-05: Clause SRG_KM.1.4 of EN 419241-1 [3], specifying device initialization, shall apply. GEN-6.2.1-06: Clause SRC_SKS.1.1 of EN 419241-1 [3], specifying algorithm parameters, shall apply. GEN-6.2.1-07: Clause SRC_SKS.1.3 of EN 419241-1 [3], specifying time of generation, shall apply. GEN-6.2.1-08 [CONDITIONAL]: If the SSAS and the certificate generation service are managed separately, then the SSAS shall support the requirement defined in clause REG-6.3.1-01 of ETSI EN 319 411-1 [2]. EXAMPLE: By providing an assertion of the authentication of the signer that is linked to the private key. GEN-6.2.1-09 [CONDITIONAL]: In case of a one-time signing key, the key shall be bound to exactly one signature session.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.2.2 eID means or identity linking
|
NOTE 1: The signing key is either linked to an eID means which is linked to the identity or directly to the identity. The latter is only possible in a process using a one-time signing key. LNK-6.2.2-00 [CONDITIONAL]: In case a one-time signing key is used, the key and the authentication may be linked directly to the identity instead of the linking to the eID means. LNK-6.2.2-01: Void. LNK-6.2.2-01A [LSP]: Clause SRC_SA.1.1 of EN 419241-1 [3], specifying enrolment, shall apply. LNK-6.2.2-02 [NSP]: Void. LNK-6.2.2-02A [NSP] [CONDITIONAL]: If the signer is a natural person, the identity proofing and verification shall be as specified in clause A.1.2 of EN 419241-1 [3], for assurance level substantial or higher. LNK-6.2.2-02B [NSP] [CONDITIONAL]: If the signer is a legal person, the identity proofing and verification shall be as specified in clause A.1.3 of EN 419241-1 [3], for assurance level substantial or higher. LNK-6.2.2-02C [NSP]: The application and registration during enrolment of the signer shall be as specified in clause A.1.1 of EN 419241-1 [3]. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 18 LNK-6.2.2-02D [NSP] [CONDITIONAL]: In case the authentication is linked to an eID means, the electronic identification means characteristics and design shall be as specified in clause A.2.1 of EN 419241-1 [3], for assurance level substantial or higher. LNK-6.2.2-02E [NSP] [CONDITIONAL]: In case the authentication is linked to an eID means, the authentication mechanism shall be as specified in clause A.2.2 of EN 419241-1 [3], for assurance level substantial or higher. LNK-6.2.2-03: Void. LNK-6.2.2-03A [CONDITIONAL]: In case the authentication is linked to an eID means, the SSASP shall link signing keys with the appropriate signer's eID means reference. LNK-6.2.2-03B [CONDITIONAL]: In case the authentication is linked directly to the identity, the SSASP shall link the one-time signing key with the specific identity. LNK-6.2.2-04: The SSASP may generate eID means reference and provide the corresponding eID means to the signer (see clause 6.2.4). LNK-6.2.2-05: The SSASP shall ensure that the person identification data linked to the eID means reference or the identity is the same as the one linked to the subject of the associated certificate. NOTE 2: When the eID means reference is provided by the TSP issuing certificates registration service, the conformance to this requirement can be assumed. LNK-6.2.2-06: The signer's eID means reference may be provided by an authorized (external) party. LNK-6.2.2-07: Void. LNK-6.2.2-07A [LSP] [CONDITIONAL]: If all or part of the authentication process is delegated to an external party the SSASP shall ensure the external party meets the requirements specified in LNK-6.2.2-01A and LNK-6.2.2-03A or LNK-6.2.2-03B. NOTE 3: If the external party uses an eID means issued under a notified scheme that is included in the list published by the Commission pursuant to Article 9 of Regulation (EU) No 910/2014 [i.1] or an EUDI wallet as defined in article 5a in Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1] and which correspond to the needed level of assurance, there is no need to demonstrate the conformance to the required level, conformance to the regulatory requirements can be assumed. LNK-6.2.2-08 [NSP] [CONDITIONAL]: If all or part of the authentication process is delegated to an external party the SSASP shall ensure that the external party meets the requirements specified in LNK-6.2.2-02A, LNK-6.2.2-02B, LNK-6.2.2-02C, LNK-6.2.2-02D, LNK-6.2.2-02E and LNK-6.2.2-03A or LNK-6.2.2-03B. LNK-6.2.2-08A [NSP] [CONDITIONAL]: If all of the authentication process is delegated to an external party the SSASP shall ensure that the secret key material used to authenticate the delegated party to the SAM shall reside in a certified cryptographic module consistent with the requirement as defined in SRG_KM.1.1 of EN 419241-1 [3]. EXAMPLE 1: The authentication of the delegated party can be done by using a signed assertion where the key material resides in a certified cryptographic module. EXAMPLE 2: In case the authentication is linked directly to the identity, the external party can be an identity service provider to whom the authentication process is delegated. In that case the identity service provider is authenticated using the key material. NOTE 4: A delegation takes place if the authentication process is done outside of the qualified trust service. LNK-6.2.2-09 [NSP] [CONDITIONAL]: If all or part of the authentication process is delegated to an external party the SSASP shall ensure that: • the external party fulfils all the relevant requirements of the present document and the requirements for registration according to the applicable regulatory requirements; or NOTE 5: In the context of the European Union, the applicable regulatory requirements are defined in Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. • the authentication process delegated to the external party uses an eID means issued under a notified scheme in accordance with the applicable regulatory requirements. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 19 NOTE 6: In the context of the European Union, the list of electronic identification means, issued under notified schemes, is published by the European Commission pursuant to Article 9 of Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. NOTE 7: The EUDI wallet as defined in article 5a in Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1] respects the requirements of an electronic identification means of level high. LNK-6.2.2-10: Void. LNK-6.2.2-10A: The SSASP shall protect the integrity of links between signer's signing key and its eID means reference if this is used or the provided identity otherwise.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.2.3 Certificate linking
|
LNK-6.2.3-01: Clause SRC_SKS.1.2 of EN 419241-1 [3], specifying certificate linking, shall apply to the SSAS. LNK-6.2.3-02: Clause SRC_SKS.1.4 of EN 419241-1 [3], specifying certificate linking, shall apply to the SSAS. LNK-6.2.3-03: Clause SRC_SKS.1.5 of EN 419241-1 [3], specifying links protection, shall apply to the SSAS.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.2.4 eID means provision
|
EID-6.2.4-01 [CONDITIONAL]: If the SSASP provides the signer's eID means, the eID means shall be securely passed to the signer. EID-6.2.4-02 [CONDITIONAL]: If the SSASP personalizes the signer's eID means with an associated user activation data (e.g. PIN code), the activation data shall be securely prepared and distributed separately from the signer's eID means.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.3 Signing key life-cycle operational requirements
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.3.1 Signature activation
|
SIG-6.3.1-01: Clause SRC_SA.1.2 of EN 419241-1 [3], specifying authentication, shall apply. SIG-6.3.1-02: Clause SRC_SA.1.3 of EN 419241-1 [3], specifying protocol security, shall apply. SIG-6.3.1-03: Clause SRC_SA.1.4 of EN 419241-1 [3], specifying access control, shall apply. SIG-6.3.1-04: Clause SRC_SA.1.5 of EN 419241-1 [3], specifying signing key control, shall apply. SIG-6.3.1-05 [NSP]: Clause SRA_SKM.2.1 of EN 419241-1 [3], specifying signing key activation, shall apply. SIG-6.3.1-06 [NSP]: Clause SRA_SAP.1.2 of EN 419241-1 [3], specifying protocol security, shall apply. SIG-6.3.1-07 [NSP]: Clause SRA_SKM.2.5 of EN 419241-1 [3], specifying signing key control, shall apply. SIG-6.3.1-08: The SSASP should ensure that the public key certificate is valid before using the corresponding signing key. NOTE 1: valid = not expired not revoked not suspended, can be met by applying DEL-6.3.2-01 if suspension is not used. SIG-6.3.1-09: Signing keys shall be usable in only those cases for which the signer's consent has been obtained. SIG-6.3.1-10: Clause SRC_DSC.1.1 of EN 419241-1 [3], specifying signature creation's algorithm parameters, shall apply. SIG-6.3.1-11 [CONDITIONAL]: In case the authentication is linked directly to the identity, the SAD shall contain the unique identifier of the signature session which shall be uniquely linked to the SSAS. SIG-6.3.1-12 [CONDITIONAL]: In case the authentication is linked directly to the identity, the SAD shall contain the unique identifier of the identity verification process. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 20 SIG-6.3.1-13 [CONDITIONAL]: In case the authentication is linked directly to the identity, the signature session shall be linked: 1) either exactly to one SAD which contains the references of all documents that shall be signed within this session; 2) or to multiple SAD values if and only if multiple consecutive signatures are applied to the same document, where each signature covers the previous ones. EXAMPLE 1: In PAdES each new signature covers the previous ones. NOTE 2: The unique identifier of the signature session can be used to identify the "default or selected" signing key in the SAD as requested in SRA_SAP.2.3 of EN 419241-1 [3]. NOTE 3: The unique identifier of the identity verification process can be used to identify the authenticated signer in the SAD as requested in SRA_SAP.2.3 of EN 419241-1 [3]. SIG-6.3.1-14 [CONDITIONAL]: In case the authentication is linked directly to the identity, the signature session shall end at most 2 hours after the end of the identity verification process. NOTE 4: The identity verification process includes not only the interaction with the subject of the identity verification, but also all processing needed to have a verified result in the end. NOTE 5: In case the authentication is linked to an eID, then identity verification of the eID link can be used for longer periods of time, because the authentication factors allow to guarantee a strong link to the identity. SIG-6.3.1-15 [NSP] [CONDITIONAL]: In case the signer is a natural person and the authentication is linked directly to the identity, the SAP shall include an explicit action (not just a checkbox) of the signer to approve the authorization to sign the content of the specific documents referenced in the SAD. SIG-6.3.1-16 [NSP] [CONDITIONAL]: In case the signer is a legal person and the authentication is linked directly to the identity, the SAP shall include an explicit action (not just a checkbox) of the natural person identified during the identity verification process and which is allowed to sign in the name of the legal person to approve the authorization to confirm the origin and integrity of the specific documents referenced in the SAD. EXAMPLE 2: An explicit action can be scrolling to the end of the document before clicking on an acceptance button or typing "I agree to sign this contract".
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.3.2 Signing key deletion
|
DEL-6.3.2-01: Clause SRG_KM.7.1 of EN 419241-1 [3] shall apply. If the public key certificate is revoked, the corresponding signing key shall be destroyed. DEL-6.3.2-02: The SSASP shall destroy a signing key when requested by the signer. DEL-6.3.2-03: Clause SRG_KM.7.2 of EN 419241-1 [3], specifying session management, shall apply. DEL-6.3.2-04: Clause SRG_KM.7.3 of EN 419241-1 [3], specifying key backup deletion, shall apply. DEL-6.3.2-05 [CONDITIONAL]: In case of a one-time signing key, the key shall be deleted immediately after the end of the signature session.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.3.3 Signing key backup and recovery
|
GEN-6.3.3-01: Clause SRG_KM.2.1 of EN 419241-1 [3], specifying key backup, shall apply. GEN-6.3.3-02: Clause SRG_KM.2.2 of EN 419241-1 [3], specifying backup protection, shall apply. GEN-6.3.3-03: Clause SRG_KM.2.3 of EN 419241-1 [3], specifying backup controls, shall apply. GEN-6.3.3-04: The number of duplicated datasets shall not exceed the minimum needed to ensure continuity of the service. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 21
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4 Facility, management, and operational controls
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4.1 General
|
OVR-6.4.1-01: The requirements identified in ETSI EN 319 401 [1], clauses 5, 6.3 and 7.3 shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4.2 Physical security controls
|
OVR-6.4.2-01: The requirements identified in ETSI EN 319 401 [1], clause 7.6 shall apply. In addition, the following particular requirements apply: OVR-6.4.2-02: The requirements identified in ETSI EN 319 411-1 [2], clause OVR-6.4.2-02 to OVR-6.4.2-10 shall apply mutatis mutandis to signing key generation and activation management services.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4.3 Procedural controls
|
OVR-6.4.3-01: Void. OVR-6.4.3-01A: The requirements REQ-7.4-03X, REQ-7.4-04X and REQ-7.4-07X to REQ-7.4-12X in ETSI EN 319 401 [1] shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4.4 Personnel controls
|
OVR-6.4.4-01: The requirements identified in ETSI EN 319 401 [1], clause 7.2 shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4.5 Audit logging procedures
|
OVR-6.4.5-01: The requirements identified in ETSI EN 319 401 [1], clause 7.10 shall apply. OVR-6.4.5-02: All security events shall be logged, including changes relating to the security policy, system start-up and shutdown, system crashes and hardware failures, firewall and router activities and SSAS system access attempts. OVR-6.4.5-03: Clause SRG_AA.1 of EN 419241-1 [3], specifying audit data generation, shall apply. OVR-6.4.5-04: Clause SRG_AA.2 of EN 419241-1 [3], specifying audit data availability, shall apply. OVR-6.4.5-05: Clause SRG_AA.3 of EN 419241-1 [3], specifying audit data parameters, shall apply. OVR-6.4.5-06: Clause SRG_AA.7 of EN 419241-1 [3], specifying audit data integrity, shall apply. OVR-6.4.5-07: Clause SRG_AA.8 of EN 419241-1 [3], specifying audit data timing, shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4.6 Records archival
|
OVR-6.4.6-01: The SSASP shall retain the audit data records for at least seven years after any certificate based on these records ceases to be valid and within the constraint of applicable legislation.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4.7 Key changeover
|
No policy requirement.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4.8 Compromise and disaster recovery
|
OVR-6.4.8-01: The requirements identified in ETSI EN 319 401 [1], clauses 7.9 and 7.11 shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.4.9 SSASP service termination
|
OVR-6.4.9-01: The requirements identified in ETSI EN 319 401 [1], clause 7.12 shall apply. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 22
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.5 Technical security controls
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.5.1 Systems and security management
|
OVR-6.5.1-01: The requirements identified in EN 419241-1 [3], clause SRG_M.1 shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.5.2 Systems and operations
|
OVR-6.5.2-01: The requirements identified in EN 419241-1 [3], clause SRG_SO.1 shall apply. OVR-6.5.2-02: The requirements identified in EN 419241-1 [3], clause SRG_SO.2 shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.5.3 Computer security controls
|
OVR-6.5.3-01: Void. OVR-6.5.3-01A: The requirements REQ-7.4-01, REQ-7.4-02X, REQ-7.4-05X, REQ-7.4-06X and REQ-7.4-13X in ETSI EN 319 401 [1] shall apply. NOTE: Requirements for the trustworthy systems can be ensured using, for example, systems conforming to EN 419241-1 [3] or to a suitable protection profile (or profiles), defined in accordance with ISO/IEC 15408 [i.6]. OVR-6.5.3-02: Clause SRG_AA.6.1 of EN 419241-1 [3], regarding system monitoring shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.5.4 Life cycle security controls
|
OVR-6.5.4-01: The requirements identified in ETSI EN 319 401 [1], clause 7.7 and 7.14 shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.5.5 Network security controls
|
OVR-6.5.5-01: The requirements identified in ETSI EN 319 401 [1], clause 7.8 shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.6 Compliance audit and other assessment
|
NOTE: See ETSI EN 319 403 [i.3].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.