hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7 Other business and legal matters
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.1 Fees
|
These policy requirements are not meant to imply any restrictions on charging for TSP's services.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.2 Financial responsibility
|
OVR-6.7.2-01: Void. NOTE: Financial responsibility is covered in clause 6.8.1 of the present document by OVR-6.8.1-01.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.3 Confidentiality of business information
|
No policy requirement.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.4 Privacy of personal information
|
OVR-6.7.4-01: The requirement REQ 7.13-05 identified in ETSI EN 319 401 [1] shall apply. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 23
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.5 Intellectual property rights
|
No policy requirement.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.6 Representations and warranties
|
NOTE 1: Representations and warranties is covered in clause 6.5.4 of the present document by OVR-6.5.4-01 which covers also REQ-7.14.3-01X and REQ-7.14.3-02X identified in ETSI EN 319 401 [1]. NOTE 2: The SSASP has the responsibility for conformance with the procedures prescribed in this policy, even when the SSASP's functionality is undertaken by outsourcers.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.7 Disclaimers of warranties
|
See clause 6.7.6.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.8 Limitations of liability
|
Limitations on liability are covered in the terms and conditions as per clause 6.8.4.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.9 Indemnities
|
No policy requirement.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.10 Term and termination
|
No policy requirement.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.11 Individual notices and communications with participants
|
No policy requirement.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.12 Amendments
|
No policy requirement.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.13 Dispute resolution procedures
|
OVR-6.7.13-01: Void. NOTE: Dispute resolution procedures is covered in clause 6.8.1 and 6.8.1 of the present document by OVR-6.8.1-01 and OVR-6.8.4-04.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.14 Governing law
|
Not in the scope of the present document.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.15 Compliance with applicable law
|
OVR-6.7.15-01: The requirements REQ-7.13-01 and REQ-7.13-02 identified in ETSI EN 319 401 [1] shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.7.16 Miscellaneous provisions
|
No policy requirement. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 24
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.8 Other provisions
| |
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.8.1 Organizational
|
OVR-6.8.1-01: The requirements identified in ETSI EN 319 401 [1], clause 7.1 shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.8.2 Additional testing
|
No policy requirement.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.8.3 Disabilities
|
OVR-6.8.3-01: The requirements REQ-7.13-03 and REQ-7.13-04 identified in ETSI EN 319 401 [1] shall apply.
|
2fcce4f84960c8aea93744ec912c9575
|
119 431-1
|
6.8.4 Terms and conditions
|
OVR-6.8.4-01: The requirements identified in ETSI EN 319 401 [1], clause 6.2 shall apply. 7 Framework for definition of server signing application service policy built on the present document OVR-7-01 [CONDITIONAL]: When building a SP from requirements defined in the present document, the policy shall incorporate, or further constrain, all the requirements identified in clauses 5 and 6. OVR-7-02 [CONDITIONAL]: When building a SP from requirements defined in the present document, the policy shall identify any variances it chooses to apply. OVR-7-03 [CONDITIONAL]: When building a SP from requirements 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-7-04 [CONDITIONAL]: When building a SP from requirements 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-7-05 [CONDITIONAL]: When building a SP from requirements 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-7-06 [CONDITIONAL]: When building a SP from requirements defined in the present document, the policy should be approved and modified in accordance with a defined review process, including responsibilities for maintaining the policy. OVR-7-07 [CONDITIONAL]: When building a SP from requirements defined in the present document, a defined review process should exist to ensure that the policy is supported by the practices statements. OVR-7-08 [CONDITIONAL]: When building a SP from requirements defined in the present document, the TSP should make available the policies supported by the TSP to its user community. OVR-7-09 [CONDITIONAL]: When building a SP from requirements defined in the present document, revisions to policies supported by the TSP should be made available to subscribers. OVR-7-10 [CONDITIONAL]: When building a SP from requirements 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-1 V1.3.1 (2024-12) 25 Annex A (normative): Specific requirements related to Regulation (EU) 2024/1183 A.1 SSASP as a Qualified TSP The present annex specifies generally applicable policy and security requirements for a Qualified TSP managing a remote QSCD. OVR-A.1-01: Void. A.2 Policy name and identification SSASPs following the present document can claim conformance to the present document via the following specific trust service policy OID: • EUSPv2: EU SSAS Policy itu-t(0) identified-organization(4) etsi(0) SIGNATURE CREATION SERVICE-policies(19431) ops (1) policy-identifiers(1) eu-remote-qscd-v2 (4) A.3 General requirements OVR-A.3-01 [EUSPv2]: All requirements specified for [NSP] shall apply. OVR-A.3-02 [EUSPv2]: The TSP's practice statement shall include the reference to the certification that the QSCD employed against the requirements of Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1], annex II. NOTE: CID (EU) 2016/650 [i.12] lays 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. However, it was published before the publication of EN 419241-1 [3] and EN 419241-2 [4] which are not taken into account. OVR-A.3-03 [EUSPv2]: The SSASP shall comply with any requirements identified in the certification report of the specific remote qualified electronic signature creation device. A.4 Signing key generation GEN-A.4-01 [EUSPv2]: Signer's signing key shall be generated in a QSCD. GEN-A.4-02 [EUSPv2]: The QSCD shall be operated in its configuration as described in the appropriate certification guidance documentation or in an equivalent configuration which achieves the same security objective. A.5 Signature activation SIG-A.5-01 [EUSPv2]: Signer's signing key shall be used in a QSCD. SIG-A.5-02 [EUSPv2]: The QSCD shall be operated in its configuration as described in the appropriate certification guidance documentation or in an equivalent configuration which achieves the same security objective. SIG-A.5-03 [EUSPv2]: Clause SRA_SAP.1.3 of EN 419241-1 [3], specifying cryptographic strength, shall apply. SIG-A.5-04 [EUSPv2]: Clause SRA_SAP.1.4 of EN 419241-1 [3], specifying threats mitigation, shall apply. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 26 SIG-A.5-05 [EUSPv2]: Clause SRA_SAP.1.5 of EN 419241-1 [3], specifying environment protection, shall apply. SIG-A.5-06 [EUSPv2]: Clause SRA_SAP.1.6 of EN 419241-1 [3], specifying protection against tampering, shall apply. SIG-A.5-07 [EUSPv2]: Clause SRA_SAP.1.7 of EN 419241-1 [3], specifying protection against attacker, shall apply. SIG-A.5-08 [EUSPv2]: The SAM should be certified to be conformant to EN 419241-2 [4]. SIG-A.5-09 [EUSPv2] [CONDITIONAL]: In case the authentication is linked directly to the identity, the signature session shall end at most 30 minutes after the end of the identity verification process. A.6 Signature activation data management SIG-A.6-01 [EUSPv2]: Clause SRA_SAP.2.1 of EN 419241-1 [3], specifying signature activation data format, shall apply. SIG-A.6-02 [EUSPv2]: Clause SRA_SAP.2.2 of EN 419241-1 [3], specifying signature activation data collection and generation, shall apply. SIG-A.6-03 [EUSPv2]: Clause SRA_SAP.2.3 of EN 419241-1 [3], specifying signature activation data parameters, shall apply. SIG-A.6-04 [EUSPv2]: Clause SRA_SAP.2.4 of EN 419241-1 [3], specifying signature activation data usage, shall apply. SIG-A.6-05 [EUSPv2]: Clause SRA_SAP.2.5 of EN 419241-1 [3], specifying signature activation data destination, shall apply. SIG-A.6-06 [EUSPv2]: Void. SIG-A.6-06A [EUSPv2]: Clause SRA_SAP.2.6 of EN 419241-1 [3], specifying signature activation data collection and protection, shall apply. SIG-A.6-07 [EUSPv2] [CONDITIONAL]: If the signer is a natural person, clause SRA_SAP.2.7 of EN 419241-1 [3], specifying signature activation data submission under sole control, shall apply. SIG-A.6-07A [EUSPv2] [CONDITIONAL]: If the signer is a legal person, clause SRA_SAP.2.7 of EN 419241-1 [3], specifying signature activation data submission shall apply where "sole control" is replaced by "control". SIG-A.6-08 [EUSPv2]: Clause SRA_SAP.2.8 of EN 419241-1 [3], specifying signature activation data protection after activation, shall apply. A.7 eID means linking LNK-A.7-01 [EUSPv2]: The identity proofing of the signer shall fulfil the requirements of extended Level of Identity Proofing (LoIP) as defined in ETSI TS 119 461 [6]. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 27 Annex B (informative): Regulation and EU SSAS policy mapping B.1 Void Table B.1: Void Table B.2: Void B.2 Regulation (EU) 2024/1183 Table B.3 identifies how the security controls objectives and other parts of the EU SSAS policy (EUSPv2) defined in the present document address the requirement of TSP managing remote QSCD as defined in Regulation (EU) 2024/1183 [i.11] in the context of electronic signatures or seals. Table B.3: Electronic signature context Article 29 Requirements for qualified electronic signature creation devices EUv2 SSAS policy reference "1a. Generating or managing electronic signature creation data or duplicating such signature creation data for back-up purposes shall be carried out only on behalf of the signatory, at the request of the signatory, and by a qualified trust service provider providing a qualified trust service for the management of a remote qualified electronic signature creation device." SIG-A.6-01: signature activation data format. SIG-A.6-02: signature activation data collection and generation. SIG-A.6-03: signature activation data parameters. SIG-A.6-04: signature activation data usage. SIG-A.6-05: signature activation data destination. SIG-A.6-06A: signature activation data collection and protection. SIG-A.6-07: signature activation data submission under sole control. SIG-A.6-08: signature activation data protection after activation. SIG-A.7-01: eID means linking. Article 29a Requirements for a qualified service for the management of remote qualified electronic signature creation devices EUv2 SSAS policy reference "1. The management of remote qualified electronic signature creation devices as a qualified service shall be carried out only by a qualified trust service provider that: (a) generates or manages electronic signature creation data on behalf of the signatory;" GEN-A.4-01, GEN-A.4-02, SIG-A.5-01 to SIG-A.5-08, SIG-A.6-01 to SIG-A.6-08 "(b) notwithstanding point (1)(d) of Annex II, duplicates the electronic signature creation data for back-up purposes only, provided that the following requirements are met: (i) the security of the duplicated datasets must be at the same level as for the original datasets; (ii) the number of duplicated datasets must not exceed the minimum needed to ensure continuity of the service;" GEN-6.3.3-02: backup protection. GEN-6.3.3-04: backup minimum datasets. "(c) complies with any requirements identified in the certification report of the specific remote qualified electronic signature creation device issued pursuant to Article 30." GEN-A.3-03, GEN-A.4-02, SIG-A.5-02 ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 28 Article 39 EUv2 SSAS policy reference Article 29 shall apply mutatis mutandis to requirements for qualified electronic seal creation devices. SIG-A.6-01: signature activation data format. SIG-A.6-02: signature activation data collection and generation. SIG-A.6-03: signature activation data parameters. SIG-A.6-04: signature activation data usage. SIG-A.6-05: signature activation data destination. SIG-A.6-06A: signature activation data collection and protection. SIG-A.6-07A: signature activation data submission under sole control. SIG-A.6-08: signature activation data protection after activation. SIG-A.7-01: eID means linking. Article 39a Requirements for a qualified service for the management of remote qualified electronic seal creation devices EUv2 SSAS policy reference "Article 29a shall apply mutatis mutandis to a qualified service for the management of remote qualified electronic seal creation devices." GEN-A.4-01, GEN-A.4-02, SIG-A.5-01 to SIG-A.5-08, SIG-A.6-01 to SIG-A.6-08 GEN-6.3.3-02: backup protection. GEN-6.3.3-04: backup minimum datasets. GEN-A.3-03, GEN-A.4-02, SIG-A.5-02 ANNEX II Requirements for qualified electronic signature creation devices EUv2 SSAS policy reference "1. Qualified electronic signature creation devices shall ensure, by appropriate technical and procedural means, that at least: (a) the confidentiality of the electronic signature creation data used for electronic signature creation is reasonably assured; (b) the electronic signature creation data used for electronic signature creation can practically occur only once; (c) the electronic signature creation data used for electronic signature creation cannot, with reasonable assurance, be derived and the electronic signature is reliably protected against forgery using currently available technology; (d) the electronic signature creation data used for electronic signature creation can be reliably protected by the legitimate signatory against use by others." GEN-A.4-01: signing keys generated in a QSCD. GEN-A.4-02: QSCD configuration and operation. "2. Qualified electronic signature creation devices shall not alter the data to be signed or prevent such data from being presented to the signatory prior to signing." SIG-A.5-01: signing keys used in a QSCD. SIG-A.5-02: QSCD configuration and operation. ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 29 Annex C (informative): Scope of remote signing standards C.1 Scope of remote signing standards Figure C.1 illustrates the different standards applicable for a remote signature creation service. Figure C.1: Scope of standards on the different remote signing components ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 30 Annex D (informative): Change history Date Version Information about changes February 2021 V1.1.2 CR #1 minor changes to clarify the requirements February 2024 V1.2.2 Draft to align with eIDASv2 September 2024 V1.2.3 CR #1 Several small corrections found when reviewing the document CR #2 Removing the mention of service component CR #4 Changes of identity proofing requirements CR #5 Alignment with latest version of ETSI EN 319 401 October 2024 V1.2.4 CR#3 no mandatory authorization for one-time signing keys Some minor corrections November 2024 V1.2.5 Some minor changes. The requirement including SAM (LNK-6.2.2-08A) is limited to NSP and above ETSI ETSI TS 119 431-1 V1.3.1 (2024-12) 31 History Document history V1.1.1 December 2018 Publication V1.2.1 May 2021 Publication V1.3.1 December 2024 Publication
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
1 Scope
|
The present document specifies policy and security requirements for the issuance, maintenance and life-cycle management of S/MIME certificates as defined in the S/MIME Baseline Requirements (SBR) [1] in the context of the ETSI Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates series. An S/MIME certificate for the purposes of the present document can be identified by the existence of an Extended Key Usage (EKU) for id-kp-emailProtection (OID: 1.3.6.1.5.5.7.3.4) and the inclusion of an email address (in the form of an rfc822Name or an otherName of type id-on-SmtpUTF8Mailbox) in the subjectAltName extension. These policy and security requirements support reference certificate policies for the issuance, maintenance and life- cycle management of S/MIME certificates issued to mailboxes (containing only an email address), natural persons (including natural persons associated with a legal person) and to legal persons, respectively. The present document does not specify how the requirements identified can be assessed by an independent party, including requirements for information to be made available to such independent assessors, or requirements on such assessors. NOTE 1: See ETSI EN 319 403-1 [i.1] for guidance on assessment of TSP's processes and services, expanded as relevant by ETSI TS 119 403-2 [i.2] for additional requirements for publicly-trusted certificates, and by ETSI TS 119 403-3 [i.3] for additional requirements for EU qualified TSPs. NOTE 2: The present document integrates all the policy requirements of the CA/Browser Forum S/MIME Baseline Requirements (SBR) [1] with ETSI EN 319 411-1 [2] for the [LCP], [NCP], and/or [NCP+] certificate policies, and with ETSI EN 319 411-2 [3] for the [QCP-l], [QCP-n], [QCP-l-qscd], and/or [QCP-n-qscd] certificate policies.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
2 References
| |
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
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] CA/Browser Forum: "Baseline Requirements for the Issuance and Management of Publicly- Trusted S/MIME Certificates" (S/MIME Baseline Requirements (SBR)). [2] ETSI EN 319 411-1: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers issuing certificates; Part 1: General requirements". [3] ETSI EN 319 411-2: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers issuing certificates; Part 2: Requirements for trust service providers issuing EU qualified certificates ". ETSI ETSI TS 119 411-6 V1.1.1 (2023-08) 6
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
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] ETSI EN 319 403-1: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Part 1: Requirements for conformity assessment bodies assessing Trust Service Providers". [i.2] ETSI TS 119 403-2: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Part 2: Additional requirements for Conformity Assessment Bodies auditing Trust Service Providers that issue Publicly-Trusted Certificates". [i.3] ETSI TS 119 403-3: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Part 3: Additional requirements for conformity assessment bodies assessing EU qualified trust service providers". [i.4] IETF RFC 3647: "Internet X.509 Public Key Infrastructure - Certificate Policy and Certification Practices Framework". 3 Definition of terms, symbols, abbreviations and notation
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
3.1 Terms
|
For the purposes of the present document, the terms given in the S/MIME Baseline Requirements (SBR) [1] and ETSI EN 319 411-1 [2] apply.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
3.2 Symbols
|
Void.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in the S/MIME Baseline Requirements (SBR) [1], ETSI EN 319 411-1 [2] and ETSI EN 319 411-2 [3] apply.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
3.4 Notation
|
The requirements identified in the present document include: a) requirements applicable to any Certificate Policy. 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 411-6 V1.1.1 (2023-08) 7 d) requirements applicable to the services offered under the applicable Certificate Policy. Such requirements are indicated by clauses marked by the applicable Certificate Policy as follows "[LCP]", "[NCP]", "[NCP+]", "[QCP-l]", "[QCP-n]", "[QCP-l-qscd]", and/or "[QCP-n-qscd]". Each requirement is identified as follows: <3 letters service component> - < the clause number> - <2 digit number – incremental>. The service components are: • OVR: General requirement (requirement applicable to more than 1 component). • GEN: Certificate Generation Services. • REG: Registration Services. • REV: Revocation Services. • DIS: Dissemination Services. • SDP: Subject Device Provisioning. • CSS: Certificate Status Service. 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 deleted requirements is left and completed with "Void". • The requirement identifier for modified requirement is left void and the modified requirement is identified by capital letter(s) appended to the initial requirement number.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4 General concepts
| |
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4.1 General policy requirements concepts
|
ETSI EN 319 411-1 [2], clause 4.1 applies.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4.2 Certificate Policy and Certification Practice Statement
| |
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4.2.1 Certification Practice Statement
|
The explanations identified in ETSI EN 319 411-1 [2], clause 4.2.1 apply.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4.2.2 Certification Policy
| |
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4.2.2.1 Certificate Policy General Concepts
|
The explanations identified in ETSI EN 319 411-1 [2], clause 4.2.2 apply. The intent of the present document is to define requirements so that a TSP issuing S/MIME certificates that assert the policy identifiers described in ETSI EN 319 411-1 [2] and ETSI EN 319 411-2 [3] may also appropriately assert the policy identifiers described in the S/MIME Baseline Requirements (SBR) [1]. ETSI ETSI TS 119 411-6 V1.1.1 (2023-08) 8 Clause 5.2 specifies how these policy identifiers can be combined in the certificatePolicies extension. Clause 6 specifies a framework for other certificate policies which enhance or further constrain these policies.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4.2.2.2 ETSI Defined Policies
|
The present document specifies how a TSP can issue S/MIME certificates that are based on the following policy requirements specified in ETSI EN 319 411-1 [2]: 1) requirements of the Lightweight Certificate Policy (LCP); 2) requirements of the Normalized Certificate Policy (NCP); and 3) requirements of the enhanced Normalized Certificate Policy (NCP+). In addition, the present document specifies how a TSP can issue S/MIME certificates that are based on the following policy requirements specified ETSI EN 319 411-2 [3]: 4) requirements for EU qualified certificates issued to natural persons (QCP-n); 5) requirements for EU qualified certificates issued to legal persons (QCP-l); 6) requirements for EU qualified certificates issued to natural persons where the private key related to the certified public key resides on a QSCD (QCP-n-qscd); and 7) requirements for EU qualified certificates issued to legal persons where the private key related to the certified public key resides on a QSCD (QCP-n-qscd).
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4.2.2.3 SBR Defined Policies
|
The S/MIME Baseline Requirements (SBR) [1], clause 1.2 defines 12 S/MIME certificate policies that can be combined with the certificate policies defined in clause 4.2.2.1 of the present document: 1) requirements for Mailbox-validated - Legacy; 2) requirements for Mailbox-validated - Multipurpose; 3) requirements for Mailbox-validated - Strict; 4) requirements for Organization-validated - Legacy; 5) requirements for Organization-validated - Multipurpose; 6) requirements for Organization-validated - Strict; 7) requirements for Sponsor-validated - Legacy; 8) requirements for Sponsor-validated - Multipurpose; 9) requirements for Sponsor-validated - Strict; 10) requirements for Individual-validated - Legacy; 11) requirements for Individual-validated - Multipurpose; and 12) requirements for Individual-validated - Strict. Use of the SBR certificate policies requires the TSP to follow the full and latest version of the SBR. As a consequence, for compliance with the SBR the TSP is required to augment the policy requirements defined in the present document with any additional requirements specific to the SBR policy. It is recognized that further updates of the SBR may occur after the publication of the present document. In case of conflicting requirements between latest version of the SBR and the present document, it is requested that this is brought to the attention of ETSI TC ESI and the CA/Browser Forum. ETSI TC ESI will endeavour to monitor revisions to the SBR and reference the latest version within the revision cycle of the present document. ETSI ETSI TS 119 411-6 V1.1.1 (2023-08) 9
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4.2.3 Terms and conditions and PKI disclosure statement
|
The guidelines identified in ETSI EN 319 411-1 [2], clause 4.2.3 apply.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
4.3 Certification services
|
The guidelines identified in ETSI EN 319 411-1 [2], clause 4.3 apply. 5 General provisions on Certification Practice Statement and Certificate Policies
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
5.1 General requirements
|
OVR-5.1-01: [LCP] or [NCP] or [NCP+]: All the applicable requirements for the certification policy supported, as identified in ETSI EN 319 411-1 [2], shall be applied. OVR-5.1-02: [QCP-n] or [QCP-l] or [QCP-n-qscd] or [QCP-l-qscd]: All the applicable requirements for the certification policy supported, as identified in ETSI EN 319 411-2 [3], shall be applied. OVR-5.1-03: All the applicable requirements for the certification policy supported, as identified in the S/MIME Baseline Requirements (SBR) [1], shall be applied. OVR-5.1-04: In case of conflict between any requirement in the current version of the present document, the latest version of the SBR takes precedence, unless a requirement in ETSI EN 319 411-1 [2] or ETSI EN 319 411-2 [3] is more stringent, in which case it remains applicable. OVR-5.1-05: [QCP-n] or [QCP-l] or [QCP-n-qscd] or [QCP-l-qscd]: In the case of Qualified certificates, the requirements of the applicable regulation shall be met.
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
5.2 Certificate Policy name and identification
|
As described in IETF RFC 3647 [i.4], clause 3.3 certificates include a Certificate Policy identifier which can be used by relying parties in determining the certificates suitability and trustworthiness for a particular application. Including one or more of the policy identifiers defined below in an S/MIME certificate indicates that the certificate is issued and managed according to the present document for that policy: • The policy identifiers for [LCP], [NCP], and [NCP+] are described in ETSI EN 319 411-1 [2], clause 5.3. • The policy identifiers for [QCP-n], [QCP-l], [QCP-n-qscd], and [QCP-l-qscd] are described in ETSI EN 319 411-2 [3], clause 5.3. • The SBR policy identifiers are described in the S/MIME Baseline Requirements (SBR) [1], clause 7.1.6.1. For convenience, the policy identifiers are identified in an informative Annex A to the present document. OVR-5.2-01: The policy requirements, including policy identifiers, for the SBR Mailbox-validated policies shall only be used in combination with the [LCP] policy requirements. OVR-5.2-02: The policy requirements, including policy identifiers, for the SBR Organization-validated policies shall only be used in combination with the [LCP] or [NCP] or [NCP+] or [QCP-l] or [QCP-l-qscd] policy requirements. OVR-5.2-03: The policy requirements, including policy identifiers, for the SBR Sponsor-validated policies shall only be used in combination with the [LCP] or [NCP] or [NCP+] or [QCP-n] or [QCP-n-qscd] policy requirements. OVR-5.2-04: The policy requirements, including policy identifiers, for the SBR Individual-validated policies shall only be used in combination with the [NCP] or [NCP+] or [QCP-n] or [QCP-n-qscd] policy requirements. ETSI ETSI TS 119 411-6 V1.1.1 (2023-08) 10 6 Framework for the definition of other certificate policies built on the present document
|
8563d7390b4309a5bb6ce5352080826a
|
119 411-6
|
6.1 Certificate Policy management
|
OVR-6.1-01: [LCP] or [NCP] or [NCP+]: The requirements identified in ETSI EN 319 411-1 [2], clause 7 shall apply. OVR-6.1-02: [QCP-n], [QCP-l], [QCP-n-qscd], and [QCP-l-qscd]: The requirements identified in ETSI EN 319 411-2 [3], clause 7 shall apply. OVR-6.1-03: The Certificate Policy shall incorporate, or further constrain, all the requirements identified in clause 5 of the present document, as appropriate to the usage, building on the requirements of the appropriate certificate policies as referenced in the present document. ETSI ETSI TS 119 411-6 V1.1.1 (2023-08) 11 Annex A (informative): Policy identifiers for S/MIME certificates A.1 ETSI Defined Certificate Policies The policy identifiers for the ETSI certificate policies described in clause 5.2 of the present document are: a) [LCP] Lightweight Certificate Policy itu-t(0) identified-organization(4) etsi(0) other-certificate-policies(2042) policy- identifiers(1) lcp (3) b) [NCP] Normalized Certificate Policy itu-t(0) identified-organization(4) etsi(0) other-certificate-policies(2042) policy- identifiers(1) ncp (1) c) [NCP+] Normalized Certificate Policy requiring a secure cryptographic device itu-t(0) identified-organization(4) etsi(0) other-certificate-policies(2042) policy- identifiers(1) ncpplus (2) d) [QCP-n] Certificate Policy for EU qualified certificates issued to natural persons; itu-t(0) identified-organization(4) etsi(0) qualified-certificate-policies(194112) policy- identifiers(1) qcp-natural (0) e) [QCP-l] Certificate Policy for EU qualified certificates issued to legal persons; itu-t(0) identified-organization(4) etsi(0) qualified-certificate-policies(194112) policy- identifiers(1) qcp-legal (1) f) [QCP-n-qscd] Certificate Policy for EU qualified certificates issued to natural persons where the private key related to the certified public key reside on a QSCD; itu-t(0) identified-organization(4) etsi(0) qualified-certificate-policies(194112) policy- identifiers(1) qcp-natural-qscd (2) g) [QCP-l-qscd] Certificate Policy for EU qualified certificates issued to legal persons where the private key related to the certified public key reside on a QSCD; itu-t(0) identified-organization(4) etsi(0) qualified-certificate-policies(194112) policy- identifiers(1) qcp-legal-qscd (3) A.2 SBR Defined Certificate Policies The policy identifiers for the SBR certificate policies described in clause 7.1.6.1 of the S/MIME Baseline Requirements (SBR) [1] are: a) Mailbox-validated - Legacy joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) mailbox-validated (1) legacy (1) b) Mailbox-validated - Multipurpose joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) mailbox-validated (1) multipurpose (2) c) Mailbox-validated - Strict joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) mailbox-validated (1) strict (3) ETSI ETSI TS 119 411-6 V1.1.1 (2023-08) 12 d) Organization-validated - Legacy joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) organization-validated (2) legacy (1) e) Organization-validated - Multipurpose joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) organization-validated (2) multipurpose (2) f) Organization-validated - Strict joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) organization-validated (2) strict (3) g) Sponsor-validated - Legacy joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) sponsor-validated (3) legacy (1) h) Sponsor-validated - Multipurpose joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) sponsor-validated (3) multipurpose (2) i) Sponsor-validated - Strict joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) sponsor-validated (3) strict (3) j) Individual-validated - Legacy joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) individual-validated (4) legacy (1) k) Individual-validated - Multipurpose joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) individual-validated (4) multipurpose (2) l) Individual-validated - Strict joint-iso-itu-t(2) international-organizations(23) ca-browser-forum(140) certificate- policies(1) smime-baseline(5) individual-validated (4) strict (3) ETSI ETSI TS 119 411-6 V1.1.1 (2023-08) 13 History Document history V1.1.1 August 2023 Publication
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
1 Scope
|
The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to ASiC baseline containers as specified in ETSI EN 319 162-1 [1]. The test suites are defined with four different layers reflecting the four different levels of ASiC baseline containers. • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. • Test suites also cover augmentation of ASiC baseline containers and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
2 References
| |
45af1b1409bbda0a110c81957181a4b1
|
119 164-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 http://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 EN 319 162-1: "Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC); Part 1: Building blocks and ASiC baseline containers". [2] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [3] ETSI EN 319 132-1: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures". [4] ETSI TS 119 124-2: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of CAdES baseline signatures". [5] ETSI TS 119 134-2: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of XAdES baseline signatures". [6] ISO/IEC 21320-1: "Information technology -- Document Container File -- Part 1: Core". ETSI ETSI TS 119 164-2 V2.1.1 (2016-06) 6
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-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] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.2] ETSI TR 119 164-1: "Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Conformance and Interoperability; Part 1: Overview". [i.3] ETSI EN 319 102-1: "Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation". [i.4] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [i.5] ETSI EN 319 132-1: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures".
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
3 Definitions and abbreviations
| |
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.1] and the following apply: negative test case: test case either for a container including signature(s) that are not CAdES baseline signatures [i.4] or XAdES baseline signatures [i.5], or for a signature whose validation according to ETSI EN 319 102-1 [i.3] would not result in TOTAL_PASSED
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.1] and the following apply: BCS Baseline Container Structure BSC Baseline Syntactical Conformance STV Signature Time-stamp token Value TC Test Case 4 ASiC baseline container interoperability test specification overview This clause describes the overall approach used to specify test suites for ASiC baseline containers interoperability testing. ETSI EN 319 162-1 [1] defines different forms and, for each, four levels of ASiC baseline containers. ETSI ETSI TS 119 164-2 V2.1.1 (2016-06) 7 The test suites are defined with different forms and layers reflecting the ASiC baseline containers specified in [1] and, for the signature test suites, reference to the appropriate CAdES test suites ETSI TS 119 124-2 [4] and XAdES test suites ETSI TS 119 134-2 [5] is made: • Testing ASiC-S and ASiC-E containers interoperability between applications claiming B-B level conformance. • Testing ASiC-S and ASiC-E containers interoperability between applications claiming B-T level conformance. • Testing ASiC-S and ASiC-E containers interoperability between applications claiming B-LT level conformance. • Testing ASiC-S and ASiC-E containers interoperability between applications claiming B-LTA level conformance. • Testing augmentation of ASiC containers from B-T level to B-LTA level. • Negative test cases for ASiC-S and ASiC-E baseline containers: - ASiC B-B level containers test cases. - ASiC B-T level containers test cases. - ASiC B-LTA level containers test cases. 5 Test suite for testing interoperability of ASiC-S baseline containers
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
5.1 Introduction to testing ASiC-S baseline containers
|
In clause 5 all the ASiC-S test cases necessary for testing conformance to each baseline level are specified. In clause 5.2 the test cases common to all ASiC-S forms and levels are specified. In clauses 5.3 and 5.4 the test cases for each level are specified.
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
5.2 Test cases common to all ASiC-S forms and levels
|
The test cases common to all ASiC-S baseline containers are specified in Table 1. Table 1: Test cases common to all ASiC-S baseline containers TC ID Description Pass criteria Interop. Level ASiC-S/BCS/1 This test case tests if the container ZIP format is correct. The container content shall comply with ISO/IEC 21320-1 [6] and be successfully extracted. Baseline Container Structure ASiC-S/BCS/2 Verify if the container format is identifiable. The container extension shall be ".asics". Baseline Container Structure ASiC-S/BCS/3 mimetype is set appropriately. Prerequisites: • ASiC-S/BCS/1 and ASiC-S/BCS/2 passed; • mimetype is present. mimetype value shall comply with ASiC [1], clauses 4.3.3.1, point 2) b) and A.1. Baseline Container Structure ASiC-S/BCS/4 This test case tests that a signature is present in the container. A META-INF folder in the root folder shall be present and contain one signature.p7s file (ASiC [1], clause 4.3.3.2 item 3b) or signatures.xml file (ASiC [1], clause 4.3.3.2, item 3c). Baseline Container Structure ASiC-S/BCS/5 Presence of the signed file. A single file, in addition to the optional mimetype, shall be present in the root folder. Baseline Container Structure ETSI ETSI TS 119 164-2 V2.1.1 (2016-06) 8 5.3 Test cases for ASiC-S baseline containers with CAdES signatures
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
5.3.1 Positive test cases
|
The test cases for ASiC-S with CAdES containers shall be as specified in Table 2. The test cases specified in clause 5.1 and the presence of signature.p7s file ASiC [1], clause 4.3.3.2 item 3b) are a prerequisite. Table 2: Test cases for all ASiC-S baseline container levels with CAdES signatures TC ID Description Pass criteria ASiC-S/CBB This group of test cases tests a set of ASiC-S container including each a signature created according to all the CAdES/BB/* test cases defined in the Test suites for testing interoperability of CAdES baseline signatures ETSI TS 119 124-2 [4], clause 5. All the CAdES/BB/* test cases in ASiC- S/CBB shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 5. ASiC-S/CBT This group of test cases tests a set of ASiC-S container including each a signature created according to all the CAdES/BT/* test cases defined in the Test suites for testing interoperability of CAdES baseline signatures ETSI TS 119 124-2 [4], clause 6. All the CAdES/BT/* test cases in ASiC- S/CBT shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 6. ASiC-S/CBLT This group of test cases tests a set of ASiC-S container including each a signature created according to all the CAdES/BLT/* test cases defined in the Test suites for testing interoperability of CAdES baseline signatures ETSI TS 119 124-2 [4], clause 7. All the CAdES/BLT/* test cases in ASiC- S/CBLT shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 7. ASiC-S/CBLTA This group of test cases tests a set of ASiC-S container including each a signature created according to all the CAdES/BLTA/* test cases defined in the Test suites for testing interoperability of CAdES baseline signatures ETSI TS 119 124-2 [4], clause 8. All the CAdES/BLTA/* test cases in ASiC-S/CBLTA shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 8. 5.3.2 Negative test cases for ASiC-S baseline containers with CAdES signatures The test cases in this clause are specified in table 3 and have been defined according to ETSI TS 119 124-2 [4], clause 10. Table 3: Negative test cases for all ASiC-S baseline container levels with CAdES signatures TC ID Description Pass criteria ASiC-S/CBBN This group of negative test cases tests a set of ASiC-S container including each a signature created according to all the CAdES/BBN/* test cases defined in the Test suites for testing interoperability of CAdES baseline signatures ETSI TS 119 124-2 [4], clause 10.2. All the CAdES/BB/* test cases in ASiC- S/CBB shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 10.2. ASiC-S/CBTN This group of test cases tests a set of ASiC-S container including each a signature created according to all the CAdES/BTN/* test cases defined in the Test suites for testing interoperability of CAdES baseline signatures ETSI TS 119 124-2 [4], clause 10.3. All the CAdES/BT/* test cases in ASiC- S/CBT shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 10.3. ASiC- S/CBLTAN This group of test cases tests a set of ASiC-S container including each a signature created according to all the CAdES/BLTAN/* test cases defined in the Test suites for testing interoperability of CAdES baseline signatures ETSI TS 119 124-2 [4], clause 10.4. All the CAdES/BLTA/* test cases in ASiC- S/CBLTA shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 10.4. ETSI ETSI TS 119 164-2 V2.1.1 (2016-06) 9 5.4 Test cases for ASiC-S baseline containers with XAdES signatures
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
5.4.1 Positive test cases
|
The test cases for ASiC-S with XAdES containers shall be as specified in Table 4. The test cases specified in clause 5.2 and the presence of signatures.xml file ASiC [1], clause 4.3.3.2 item 3c) are a prerequisite. Table 4: Test cases for all ASiC-S baseline container levels with XAdES signatures TC ID Description Pass criteria ASiC-S/XBB This group of test cases tests a set of ASiC-S container including each a signature created according to all the XAdES/BB/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 134-2 [5], clause 5 signing one data object. Test cases where more than one data object is signed shall not be included. All the XAdES/BB/* test cases in ASiC-S/XBB shall be passed according to the criteria specified in ETSI TS 119 134-2 [5], clause 5. ASiC-S/XBT This group of test cases tests a set of ASiC-S container including each a signature created according to all the XAdES/BT/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 134-2 [5], clause 6 signing one data object. Test cases where more than one data object is signed shall not be included. All the XAdES/BT/* test cases in ASiC-S/XBT shall be passed according to the criteria specified in ETSI TS 119 134-2 [5], clause 6. ASiC-S/XBLT This group of test cases tests a set of ASiC-S container including each a signature created according to all the XAdES/BB/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 134-2 [5], clause 7 signing one data object. Test cases where more than one data object is signed shall not be included. All the XAdES/BLT/* test cases in ASiC-S/XBLT shall be passed according to the criteria specified in ETSI TS 119 134-2 [5], clause 7. ASiC-S/XBLTA This group of test cases tests a set of ASiC-S container including each a signature created according to all the XAdES/BLTA/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 134-2 [5], clause 8 signing one data object. Test cases where more than one data object is signed shall not be included. All the XAdES/BLTA/* test cases in ASiC-S/XBLTA shall be passed according to the criteria specified in ETSI TS 119 134-2 [5], clause 8. 5.4.2 Negative test cases for ASiC-S baseline containers with XAdES signatures The test cases in this clause are specified in table 5 and have been defined according to ETSI TS 119 134-2 [5], clause 11. ETSI ETSI TS 119 164-2 V2.1.1 (2016-06) 10 Table 5: Negative test cases for all ASiC-S baseline container levels with XAdES signatures TC ID Description Pass criteria ASiC-S/XBBN This group of negative test cases tests a set of ASiC-S container including each a signature created according to all the XAdES/BBN/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 124-2 [4], clause 10.2. All the XAdES/BB/* test cases in ASiC-S/CBB shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 10.2. ASiC-S/XBTN This group of test cases tests a set of ASiC-S container including each a signature created according to all the XAdES/BTN/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 124-2 [4], clause 10.3. All the XAdES/BT/* test cases in ASiC-S/CBT shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 10.3. ASiC- S/XBLTAN This group of test cases tests a set of ASiC-S container including each a signature created according to all the XAdES/BLTAN/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 124-2 [4], clause 10.4. All the XAdES/BLTA/* test cases in ASiC-S/CBLTA shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 10.4. 6 Test suite for testing interoperability of ASiC-E baseline containers
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
6.1 Introduction to testing ASiC-E baseline containers
|
In clause 6 all the ASiC-E test cases necessary for testing conformance to each baseline level are specified. In clause 6.2 the test cases common to all ASiC-E forms and levels are specified. In clauses 6.2 and 6.3 the test cases for each level are specified. NOTE: Only a single baseline container type is defined for ASiC-E in the current version of ASiC [1]. The present document is already structured to accommodate additional baseline containers in case they will be added.
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
6.2 Test cases common to all ASiC-E forms and levels
|
The test cases common to all ASiC-E baseline containers are specified in Table 6. Table 6: Test cases common to all ASiC-E baseline containers for testing the Container Structure TC ID Description Pass criteria ASiC-E/BCS/1 This test case tests if the container ZIP format is correct. The container content shall comply with ISO/IEC 21320-1 [6] and be successfully extracted. ASiC-E/BCS/2 Verify if the container format is identifiable. The container extension shall be ".asice" ASiC-E/BCS/3 mimetype is set appropriately. Prerequisites: • ASiC-E/BCS/1 and ASiC-E/BCS/2 passed; • mimetype is present. mimetype value shall comply with ASiC [1], clauses 4.4.3.1, item 2) and A.1. ASiC-E/BCS/4 Test if signature metadata is present. META-INF folder in the root folder contains one or more *signatures*.xml file. ASiC-E/BCS/5 Presence of the signed file. One or more files, in addition to the optional mimetype, shall be present in the container outside of the META-INF folder. ETSI ETSI TS 119 164-2 V2.1.1 (2016-06) 11 6.3 Test cases for ASiC-E baseline containers with XAdES signatures
|
45af1b1409bbda0a110c81957181a4b1
|
119 164-2
|
6.3.1 Positive test cases
|
The test cases for ASiC-E with XAdES containers are specified in Table 7 in relation to the syntactical conformance of the container and in Table 6 for the conformance of the XAdES signatures. The test cases specified in clause 6.2 are a prerequisite. Table 7: Test cases for testing the syntactical conformance of ASiC-E baseline containers with XAdES signatures TC ID Description Pass criteria ASiC-E/BSC/X1 Test if XAdES signature files are conformant. META-INF folder in the root folder contains one or more *signatures*.xml whose content shall be compliant with ASiC [1], clause 4.4.3.2, item 2 and item 3a. ASiC-E/BSC/X2 Test if data objects referenced in XAdES signature files are present. XAdES signature present in one or more *signatures*.xml files shall reference only data objects present in the container. ASiC-E/BSC/X3 Test if manifest.xml is conformant. META-INF/ manifest.xml shall be present and compliant with ASiC [1], clause 4.4.3.2, item 5b. ASiC-E/BSC/X4 Test if mime types present in manifest.xml file are coherent with referenced objects. All media types associated to files referenced by manifest.xml file shall be coherent with the media type of the referenced objects. The test cases specified in Table 7 shall be repeated with different input containers including at least one with a single signature file and one with more than one. Table 8 specifies the test cases for the signatures of ASiC-E baseline containers with XAdES signatures. The containers used to perform the test shall include: a) one or more XAdES signatures signing one file present in the container, and/or b) one or more XAdES signatures signing two files present in the container. Different XAdES signatures may be present in the same container they shall be of the same baseline level and shall be created according to the test suites for testing interoperability of XAdES baseline signatures specified in ETSI TS 119 134-2 [5] using signatures as described in the item a) above for the test cases that require the signature of single data object and as per item b) for test cases requiring the signature of two data objects and according to the requirements present in Table 8. Table 8: Test cases for testing the signatures of ASiC-E baseline containers with XAdES signatures TC ID Description Pass criteria ASiC-E/XBB This group of test cases tests the signatures present in one or more ASiC-E containers with XAdES signatures that shall be created according to the XAdES/BB/* test cases defined in ETSI TS 119 134-2 [5], clause 5. All the XAdES/BB/* test cases in ASiC-S/XBB shall be passed according to the criteria specified in ETSI TS 119 134-2 [5], clause 5. ASiC-E/XBT This group of test cases tests the signatures present in one or more ASiC-E containers with XAdES signatures that shall be created according to the XAdES/BB/* test cases defined in ETSI TS 119 134-2 [5], clause 6. All the XAdES/BT/* test cases in ASiC-S/XBT shall be passed according to the criteria specified in ETSI TS 119 134-2 [5], clause 6. ASiC-E/XBLT This group of test cases tests the signatures present in one or more ASiC-E containers with XAdES signatures that shall be created according to the XAdES/BB/* test cases defined in ETSI TS 119 134-2 [5], clause 7. All the XAdES/BLT/* test cases in ASiC-S/XBLT shall be passed according to the criteria specified in ETSI TS 119 134-2 [5], clause 7. ETSI ETSI TS 119 164-2 V2.1.1 (2016-06) 12 TC ID Description Pass criteria ASiC-E/XBLTA This group of test cases tests the signatures present in one or more ASiC-E containers with XAdES signatures that shall be created according to the XAdES/BB/* test cases defined in ETSI TS 119 134-2 [5], clause 8. All the XAdES/BLTA/* test cases in ASiC-S/XBLTA shall be passed according to the criteria specified in ETSI TS 119 134-2 [5], clause 8. For each baseline level (a row of Table 8) one or more containers shall include all the signatures needed to have a full coverage of all the test cases defined for that level. 6.3.2 Negative test cases for ASiC-E baseline containers with XAdES signatures The test cases in this clause are specified in table 9 and have been defined according to ETSI TS 119 134-2 [5], clause 10. Table 9: Negative test cases for all ASiC-E baseline container levels with XAdES signatures TC ID Description Pass criteria ASiC-E/XBBN This group of negative test cases tests a set of ASiC-E container including each a signature created according to all the XAdES/BBN/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 124-2 [4], clause 10.2. All the XAdES/BB/* test cases in ASiC-E/CBB shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 10.2. ASiC-E/XBTN This group of test cases tests a set of ASiC-E container including each a signature created according to all the XAdES/BTN/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 124-2 [4], clause 10.3. All the XAdES/BT/* test cases in ASiC-E/CBT shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 10.3. ASiC- E/XBLTAN This group of test cases tests a set of ASiC-E container including each a signature created according to all the XAdES/BLTAN/* test cases defined in the Test suites for testing interoperability of XAdES baseline signatures ETSI TS 119 124-2 [4], clause 10.4. All the XAdES/BLTA/* test cases in ASiC-E/CBLTA shall be passed according to the criteria specified in ETSI TS 119 124-2 [4], clause 10.4. 7 Test-suite for augmentation of ASiC baseline containers Augmentation tests cases can be performed according to clause 9 of ETSI TS 119 124-2 [4] for containers including CAdES signatures and to clause 9 of ETSI TS 119 134-2 [5] for containers including XAdES signatures. To perform this test ASiC baseline containers conformant to B-T level as generated for the test case ASiC-S/CBT, ASiC-S/XBT or ASiC-E/XBT that include B-T level baseline signatures shall be augmented to B-LTA level baseline signatures according the test cases specified in ETSI TS 119 124-2 [4], clause 9 table 5 for CAdES signatures or specified in ETSI TS 119 134-2 [5], clause 9 table 6 for XAdES signatures, specifying which properties are required to augment the B-T level baseline signatures. ETSI ETSI TS 119 164-2 V2.1.1 (2016-06) 13 Annex A (informative): Bibliography • OASIS "Test Assertions Guidelines Version 1.0", Committee Specification Draft 06/Public Review Draft 03, 15 August 2011. • ETSI EN 319 162-2: "Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC); Part 2: Additional ASiC containers". ETSI ETSI TS 119 164-2 V2.1.1 (2016-06) 14 History Document history V1.1.1 March 2012 Publication V2.1.1 June 2016 Publication
|
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
1 Scope
|
The present document defines specific supplementary requirements for the application of ETSI EN 319 403 [1] aimed at conformity assessments (audits) of qualified trust service providers (QTSPs) and the qualified trust services (QTSs) they provide, as well as of trust service providers, without qualified status, intending to start providing qualified trust services, against the requirements of Regulation (EU) No 910/2014 [i.1] assuming the use of ETSI policy requirement standards but not precluding use of other specifications. In particular, the present document defines requirements for conformity assessment reports, including their content.
|
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
2 References
| |
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
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 EN 319 403: "Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment - Requirements for conformity assessment bodies assessing Trust Service Providers". [2] ETSI TS 119 612 (V2.1.1): "Electronic Signatures and Infrastructures (ESI); Trusted Lists". [3] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile".
|
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
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. NOTE: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG. [i.2] Commission Implementing Decision (EU) 2015/1505 of 8 September 2015 laying down technical specifications and formats relating to trusted lists pursuant to Article 22(5) 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. NOTE: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32015D1505. ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 7 [i.3] EC Regulation No 765/2008 of the European Parliament and of the Council of 9 July 2008 setting out the requirements for accreditation and market surveillance relating to the marketing of products and repealing Regulation (EEC) No 339/93. [i.4] CA/Browser Forum: "Baseline Requirements for the Issuance and Management of Publicly- Trusted Certificates". [i.5] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.6] ISO/IEC 17021-1: "Conformity assessment -- Requirements for bodies providing audit and certification of management systems -- Part 1: Requirements". [i.7] ISO/IEC 27006: "Information technology -- Security techniques -- Requirements for bodies providing audit and certification of information security management systems". [i.8] Commission Implementing Regulation (EU) 2015/806 of 22 May 2015 laying down specifications relating to the form of the EU trust mark for qualified trust services. NOTE: http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2015.128.01.0013.01.ENG. [i.9] ENISA: "Guidelines on initiation of qualified trust services; Technical guidelines on trust services", December 2017. ISBN: 978-92-9204-189-2. NOTE: https://www.enisa.europa.eu/publications/tsp-initiation. [i.10] ETSI EN 319 401: "Electronic Signatures and Infrastructures (ESI); General Policy Requirements for Trust Service Providers". [i.11] 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.12] ETSI EN 319 411-2: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 2: Requirements for trust service providers issuing EU qualified certificates". [i.13] ETSI EN 319 412-2: "Electronic Signatures and Infrastructures (ESI); Certificate Profiles; Part 2: Certificate profile for certificates issued to natural persons". [i.14] ETSI EN 319 412-3: "Electronic Signatures and Infrastructures (ESI); Certificate Profiles; Part 3: Certificate profile for certificates issued to legal persons". [i.15] ETSI EN 319 412-4: "Electronic Signatures and Infrastructures (ESI); Certificate Profiles; Part 4: Certificate profile for web site certificates". [i.16] ETSI EN 319 412-5: "Electronic Signatures and Infrastructures (ESI); Certificate Profiles; Part 5: QCStatements". [i.17] ETSI EN 319 421: "Electronic Signatures and Infrastructures (ESI); Policy and Security Requirements for Trust Service Providers issuing Time-Stamps". [i.18] ETSI EN 319 422: "Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp token profiles". [i.19] ETSI TS 119 441: "Electronic Signatures and Infrastructures (ESI); Policy requirements for TSP providing signature validation services". [i.20] ETSI TS 119 442: "Electronic Signatures and Infrastructures (ESI); Protocol profiles for trust service providers providing AdES digital signature validation services". [i.21] ETSI EN 319 102-1: "Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation". [i.22] ETSI TS 119 102-2: "Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 2: Signature Validation Report". ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 8 [i.23] ETSI TS 119 172-4: "Electronic Signatures and Infrastructures (ESI); Signature policies; Part 4: Signature validation policy for European qualified electronic signatures/seals using trusted lists". [i.24] ETSI TS 119 511: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers providing long-term preservation of digital signatures or unsigned data using signature techniques". [i.25] ETSI TS 119 512: "Electronic Signatures and Infrastructures (ESI); Protocols for trust service providers providing long-term preservation of digital signatures or unsigned data using signature techniques". [i.26] ETSI EN 319 521: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Electronic Registered Delivery Service Providers". [i.27] ETSI EN 319 522 (all parts): "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services". [i.28] ETSI EN 319 531: "Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Registered Electronic Mail Service Providers". [i.29] ETSI EN 319 532 (all parts): "Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services". [i.30] ISO/IEC 17065: "Conformity assessment -- Requirements for bodies certifying products, processes and services". [i.31] CEN EN 419 221-5: "Protection Profiles for TSP Cryptographic Modules - Part 5: Cryptographic Module for Trust Services". [i.32] CEN EN 419 241-1: "Trustworthy Systems Supporting Server Signing - Part 1: Security Requirements for Trustworthy Systems Supporting Server Signing". [i.33] CEN EN 419 241-2: "Trustworthy Systems Supporting Server Signing - Part 2: Protection Profile for QSCD for Server Signing". [i.34] 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.35] 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". [i.36] ETSI TS 119 432: "Electronic Signatures and Infrastructures (ESI); Protocols for remote digital signature creation". 3 Definition of terms, symbols, abbreviations and notations
|
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TR 119 001 [i.5] apply.
|
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
3.2 Symbols
|
Void. ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 9
|
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.5] and the following apply: CAB Conformity Assessment Body CAR Conformity Assessment Report CID Commission Implementing Decision HSM Hardware Security Module NAB National Accreditation Body PEM Privacy-Enhanced electronic Mail QTSP/QTS Qualified Trust Service Provider and the Qualified Trust Service it provides SB Supervisory Body
|
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
3.4 Notations
|
The requirements in the present document are identified as follows: <3 letters identifying the section title> - <the clause number> - <2-digit number - incremental> 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-digits 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 deleted requirements are kept and completed with "VOID". • The requirement identifier for modified requirement are kept void and the modified requirement is identified by capital letter(s) appended to the initial requirement number. 4 Requirements for CABs assessing QTSP/QTSs against requirements of Regulation (EU) No 910/2014
|
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
4.1 Conformity assessment scheme
|
CAS-4.1-01: The conformity assessment scheme for which a CAB is accredited to assess QTSP/QTSs against the requirements of Regulation (EU) No 910/2014 [i.1] in accordance with Regulation (EC) No 765/2008 [i.3] shall be defined in a way that such accreditation ensures the accredited CAB is competent to carry out conformity assessment of a QTSP/QTS against the requirements of Regulation (EU) No 910/2014 [i.1]. In particular: CAS-4.1-02: The conformity assessment scheme shall, with the aim of confirming that the assessed QTSP/QTS fulfils the applicable requirements from Regulation (EU) No 910/2014 [i.1], include: a) requirements on the CAB, including on the auditing rules under which the CAB will carry out its conformity assessment and on the effective set of criteria, meeting at least requirements from ETSI EN 319 403 [1]; and NOTE: This de facto implies the CAB being compliant with ETSI EN 319 403 [1], hence with ISO/IEC 17065 [i.30], to be a certification body and the conformity assessment scheme to be a certification scheme [i.30]. b) control objectives and controls against which the CAB will assess a QTSP/QTS against the applicable requirements of Regulation (EU) No 910/2014 [i.1]. ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 10 CAS-4.1-03: The resulting conformity assessment report shall meet the requirements of clause 4.2 of the present document.
|
a7aacacb9d7e1206e04c01d4c7215e6d
|
119 403-3
|
4.2 Conformity assessment report
|
CAR-4.2-01: The Conformity Assessment Report (CAR) shall bear a clear certification decision conformant to clause 7.6 of ETSI EN 319 403 [1], confirming - if such is the case - that the assessed QTSP/QTS meet all the applicable requirements of Regulation (EU) No 910/2014 [i.1]. CAR-4.2-02: The CAR shall provide sufficient details to demonstrate that the assessed QTSP/QTS fulfil all the applicable requirements laid down in Regulation (EU) No 910/2014 [i.1]. NOTE 1: Those details and information demonstrating QTSP/QTS compliance with Regulation (EU) No 910/2014 [i.1] requirements can be included by reference to other reports, e.g. such as audit reports against technical standards, which contain detailed and herewith sufficient information for the SB to judge the QTSP/QTS conformity to the Regulation. On top of that the SB can be pointed to the security documentation of the QTSP, like the security concept, its declaration of practices and/or of policies, etc., as it can be referenced in the CAR. In particular: CAR-4.2-03: The CAR shall identify the name of the CAB, and where applicable its registration number, as stated in the official records, its official postal address and its electronic address. CAR-4.2-04: The CAR shall identify: a) the name of the NAB having accredited the CAB; b) the link, on the official website of the NAB, to the accreditation certificate issued by the NAB to the CAB; and c) when not mentioned in the accreditation certificate: i) the scheme under which the CAB has been accredited in the context of Regulation (EU) No 765/2008 [i.3]; and EXAMPLE 1: Such a scheme can be ISO/IEC 17065 [i.30] being completed by ETSI EN 319 403 [1]. ii) the conformity assessment (certification) scheme for which the CAB has been accredited to conduct conformity assessment of QTSP/QTSs against the requirements laid down in Regulation (EU) No 910/2014 [i.1]. CAR-4.2-05: The complete CAR shall be considered as part of the certification documentation specified in clause 7.7 of ETSI EN 319 403 [1]. CAR-4.2-06: The CAR shall include the accredited conformity assessment (certification) scheme document (or set of documents) or a link to the location from where that document (or set of documents) is available. CAR-4.2-07: The CAR shall bear EU qualified electronic signature(s) identifying the name and title of the CAB responsible person(s) having authorized the certification decision. CAR-4.2-08: The CAR shall be dedicated to one and only one QTSP, in particular: a) the CAR shall identify the name of the assessed QTSP, and where applicable its registration number, as stated in the official records, its official postal address and its electronic address; and b) when applicable, the CAR shall identify this same information of all subsidiaries, affiliated legal entities and (sub)contractors that are operating trust service components in scope of the provision of (Q)TS by the QTSP, and hence in scope of the certification decision. NOTE 2: QTSPs can make use of third parties, whether (Q)TSPs or not, to operate part or all of the service components of the QTS they provide. In this situation, the QTSP remains the final entity responsible and liable for the QTS it provides and needs to document and ensure correct implementation of those service components against its declared practices and policies as well as against Regulation (EU) No 910/2014 [i.1]. ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 11 CAR-4.2-09: The CAR shall identify, in accordance with clause 5.5.3 of ETSI TS 119 612 (V2.1.1) [2], the service digital identity(ies) per type of QTS for which the CAR confirms the conformity with the requirements of Regulation (EU) No 910/2014 [i.1] providing at least: a) the Subject Key Identifier as defined in IETF RFC 5280 [3]; b) the Base64 PEM representation of the associated X.509v3 digital certificate; c) when applicable, an indication whether specific sets or subsets of end-entity certificates issued by or under the service digital identity are excluded from the certification decision and on the basis of which criteria they can be identified; EXAMPLE 2: Such criteria can be a list of certificate policy identifiers to match with the content of the CertificatePolicy certificate extension as defined in IETF RFC 5280 [3] or other criteria as defined in clause 5.5.9.2.2 of ETSI TS 119 612 (V2.1.1) [2]. d) an indication whether the service digital identity relates to an end-entity or a certification authority, clarifying whether an issuing, intermediate or root; and e) an indication on how the service digital identity is used in the context of the corresponding QTS. EXAMPLE 3: The private key corresponding to the service digital identity can be used to digitally sign (qualified) certificates, qualified electronic time stamps, evidences in the context of qualified electronic registered delivery, in the context of qualified validation of qualified electronic signatures or seals, or in the context of qualified preservation of qualified electronic signatures or seals. CAR-4.2-10: In line with CAR-4.2-09, per type of QTS and for all service digital identities identified in CAR-4.2-09, the CAR shall provide a detailed description of the PKI functional hierarchy with the purpose to allow identification of the service entry(ies) to be listed in the applicable national trusted list in accordance with CID (EU) 2015/1505 [i.2], including at least: a) the illustration of the PKI hierarchy identifying the root certification authority(ies), the intermediate certification authority(ies), the issuing certification authority(ies) and the certification paths between them; b) the identification of each certification authority illustrated in point a) through the Subject Key Identifier as defined in IETF RFC 5280 [3]; c) for each of the issuing CAs identified in point b), the list of the different (policy) sets of certificates such a CA is issuing, with for each set: i) a criteria that unambiguously identifies the certificates of the set, being either a list of certificate policy identifiers to match with the content of the CertificatePolicy certificate extension as defined in IETF RFC 5280 [3] or other criteria as defined in clause 5.5.9.2.2 of ETSI TS 119 612 (V2.1.1) [2]; ii) an indication whether the certificates of the set are either qualified or non-qualified; iii) an indication whether the certificates of the set are either for electronic signatures, or for electronic seals, or for web site authentication or for none of these purposes and, in particular in this latter case, for which other purposes they are aimed to be used. CAR-4.2-11: Pursuant the conclusions of the conformity assessment, the CAR shall provide an indication of the corresponding content of the applicable national trusted list [i.1] and [i.2], which reflects the result of the assessment. CAR-4.2-12: In line with CAR-4.2-10, the CAR shall include an exhaustive list of third parties (e.g. subcontractors) which provide/operate QTS components or service components by indicating their name, as identified in CAR-4.2-08 b), together with the location of the sites where the corresponding component services are operated. CAR-4.2-13: The CAR shall detail, in line with CAR-4.2-12, which of these third parties and which sites have been subject to the audit and to which extent. ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 12 CAR-4.2-14: The CAR shall identify the exhaustive list of public and QTSP internal documents, including versioning, which have been part of the scope of the audit, including at least: a) the following public documents: i) the declaration of the practices used by the QTSP to provide the assessed QTS; ii) the QTS policy(ies), i.e. the set of rules that indicates the applicability of the QTS to a particular community and/or class of application with common security requirements; iii) the terms and conditions related to subscriber agreements; b) the following internal documents: i) the termination plan referred to in Article 24.2.(i) of Regulation (EU) No 910/2014 [i.1]; ii) the documentation related to the assessment of risks aimed at supporting the demonstration of the requirements of Article 19.1 of [i.1]; iii) a security and personal data breach notification plan aimed to support demonstration of the requirement of Article 19.2 of [i.1]; and iv) the list of all internal documents supporting the declaration of the practices used by the QTSP to provide the assessed QTS under the corresponding QTS policy(ies); and c) the following public or internal documents: i) memorandum and Articles of Association of the assessed QTSP; ii) evidence that the assessed QTSP, in accordance with national law, maintains sufficient financial resources and/or has obtained appropriate liability insurance with regards to the provision of the QTS; EXAMPLE 4: Evidences can include a copy of the profit and loss account and balance sheets for the last three years for which accounts have been closed, appropriate statements from banks and/or liability insurance statements. iii) the list of standards on the one side with which operations are claimed to be compliant and on the other side with which operations are audited, evaluated, certified or assessed to be compliant together with details about the underlying audit, evaluation, certification or assessment scheme; iv) the list of QSCDs and their certification related information when the (Q)TSP delivers such devices to its users; and v) the list of devices used by the (Q)TSP as trustworthy devices (e.g. HSMs) to protect its own keys, and their certification related information, when the (Q)TSP uses such devices to secure the processes supporting the QTS it provides or aim to provide. CAR-4.2-15: The CAR shall identify, for each stage of the audit (e.g. documentation audit and implementation audit including onsite inspections), the period during which the audit has been conducted (elapsed time) and the effort in man-days engaged by the CAB to conduct the audit. CAR-4.2-16: The CAR shall provide, for each of the following requirements of Regulation (EU) No 910/2014 [i.1], an assessment report, with an indication of the non-conformities and their level of criticality, on the fulfilment by the assessed QTSP/QTS of the identified requirement, and/or when appropriate, on the existence of proper procedures and management system for handling this requirement: a) General requirements for QTSPs and for each type of QTS provided with an indication of the relevant articles of the eIDAS Regulation: i) Article 5 regarding data processing and protection: 1) As the assessment of that requirement can be seen as a duplication of point (j) of Article 24.2 of Regulation (EU) No 910/2014 [i.1], reference may be made to the report on the assessment of compliance with point (j) of Article 24.2 (see below). ii) Articles 13.2 and 13.3 regarding liability and burden of the proof; ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 13 iii) Article 15 regarding accessibility for person with disabilities; iv) Article 19.1 regarding risk based security due diligence; v) Article 19.2 regarding security and personal data breach notification; vi) Article 20.1 regarding completion and internal procedures for completing at least 2-yearly audits and timely submission of the results to the competent SB; vii) Article 23 on the correct use of the EU trust mark for qualified trust services, including provisions from CIR (EU) 2015/806 [i.8]; viii) points (a) to (j) of Article 24.2. (b) Additional specific requirements for the applicable type of QTS: i) Provision of qualified certificates for electronic signatures: 1) points (a) to (d) of Article 24.1; 2) Article 24.2.(k); 3) Article 24.3; 4) Article 24.4; 5) Article 28.1 (including Annex I); 6) Article 28.2; 7) Article 28.3; 8) Article 28.4; 9) Article 28.5. ii) Provision of qualified certificates for electronic seals: 1) points (a) to (d) of Article 24.1; 2) Article 24.2.(k); 3) Article 24.3; 4) Article 24.4; 5) Article 38.1 (including Annex III); 6) Article 38.2; 7) Article 38.3; 8) Article 38.4; 9) Article 38.5. iii) Provision of qualified certificates for website authentication: 1) points (a) to (d) of Article 24.1; 2) Article 24.2.(k); 3) Article 24.3; 4) Article 24.4; 5) Article 45.1 (including Annex IV). iv) Qualified validation service for qualified electronic signatures: Article 32.1, Article 32.2, Article 33.1; ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 14 v) Qualified validation service for qualified electronic seals: Article 40; vi) Qualified preservation service for qualified electronic signatures: Article 34.1; vii) Qualified preservation service for qualified electronic seals: Article 40; viii) Qualified electronic time stamps: Article 42.1; ix) Qualified electronic registered delivery services: Article 44.1. CAR-4.2-17: The CAR shall, referring to CAR-4.2-16, identify in the corresponding specific requirement report the detailed audit controls and control objectives that have been conducted during the audit with an indication of each non-conformity and their level of criticality or include a reference to separately available audit reports in which such information is included, provided such separated reports are issued by CABs, when applicable, accredited under Article 3.18 of Regulation (EU) No 910/2014 [i.1] and are endorsed by the CAB issuing the CAR. NOTE 3: Including reference to separately available audit reports allows CARs to be built upon separated "module-conformity-reports" with regard to well-defined parts of trust services that can be reused by CABs provided such separated reports are issued by CABs accredited under Article 3(18) of Regulation (EU) No 910/2014 [i.1] and are endorsed by the CAB issuing the CAR. CAR-4.2-18: The CAR shall include the scope, the description and the results of a significant set of test or production samples and their assessment for all relevant and applicable types of outputs from the assessed QTS. EXAMPLE 5: Providing a single signed or sealed validation report for the validation of a single qualified electronic signature or seal is not likely to be considered as a significant set of test or production samples. The provision and assessment of a test plan including a significant set of positive and negative test cases for signatures/seals together with generated validation reports and their assessment can be an example of a significant set of samples. CAR-4.2-19: In addition to the certification statement referred to in CAR-4.2-01, the CAR shall include, when applicable and when the conformity of the assessed QTSP/QTS is additionally certified as compliant against a specific standard or publicly available specifications, the report on the fulfilment by the QTSP and by the implementation of its QTS against such standard or specifications that has been conducted during the audit, with an indication of the non- conformities and their level of criticality. NOTE 4: With regards to CAR-4.2-16, CAR-4.2-17 and CAR-4.2-19, pending non-conformities are only acceptable in line with clause 7.6 b) of ETSI EN 319 403 [1]. CAR-4.2-20: The CAR shall indicate: a) by when, when applicable, the next surveillance audit has to be conducted at the latest; and b) by when the next compliance audit has to be conducted at the latest. CAR-4.2-21: The CAR shall indicate, in line with clause 7.6 b) of ETSI EN 319 403 [1], under which circumstances a CAB accredited under Article 3.18 of Regulation (EU) No 910/2014 [i.1] has to be involved in reassessing the assessed QTSP/QTS in addition to the planned audits. CAR-4.2-22: The CAR shall contain an explicit declaration stating that the certification documents, including the CAR, are also intended for the use by SBs as defined in Regulation (EU) No 910/2014 [i.1]. ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 15 Annex A (informative): QTSP/QTS conformity assessment against Regulation (EU) No 910/2014 A.1 Overview Conformity Assessment Bodies (CABs) aiming to assess qualified trust service providers and the qualified trust services they provide (QTSP/QTSs) against the requirements of Regulation (EU) No 910/2014 [i.1] are required by Article 3.18 of this Regulation to be accredited in accordance with Regulation (EC) No 765/2008 [i.3] in a way that such accreditation ensures the accredited CABs are competent to carry out conformity assessment of a QTSP/QTS against the requirements of the eIDAS Regulation [i.1]. The sole certificate of conformity of a QTSP/QTS against any standard is not sufficient to confirm that QTSP/QTS fulfils the requirements laid down in Regulation (EU) No 910/2014 [i.1] as required by Article 20.1 and Article 21.1 of this Regulation. No secondary legislation has been adopted yet to refer to any standard whose compliance would lead to the presumption of compliance with a sub-set of those requirements. Regulation (EU) No 910/2014 [i.1] does not even foresee such secondary legislation for all the requirements applicable to QTSP/QTSs. It is however assumed that the demonstration of QTSP/QTS compliance with specific international or European standards will facilitate demonstrating and certifying QTSP/QTS compliance with the applicable requirements of Regulation (EU) No 910/2014 [i.1]. In particular, CEN, CENELEC and ETSI have published a wide set of standards with that objective. The following table A.1 provides the list of relevant standards whose compliance is aimed to facilitate demonstration of compliance with requirements from [i.1]. Table A.1: Standards available in support of Regulation (EU) No 910/2014 [i.1] Qualified trust service in Regulation (EU) No 910/2014 [i.1] Standards Provision of qualified certificates for electronic signatures ETSI EN 319 411-2 [i.12] (requiring compliance with ETSI EN 319 401 [i.10], ETSI EN 319 411-1 [i.11], ETSI EN 319 412-2 [i.13], ETSI EN 319 412-5 [i.16]) Provision of qualified certificates for electronic seals ETSI EN 319 411-2 [i.12] (requiring compliance with ETSI EN 319 401 [i.10], ETSI EN 319 411-1 [i.11], ETSI EN 319 412-3 [i.14], ETSI EN 319 412-5 [i.16]) Provision of qualified certificates for website authentication ETSI EN 319 411-2 [i.12] (requiring compliance with ETSI EN 319 401 [i.10], ETSI EN 319 411-1 [i.11], ETSI EN 319 412-4 [i.15], ETSI EN 319 412-5 [i.16]) Provision of qualified time stamps ETSI EN 319 421 [i.17] (requiring compliance with ETSI EN 319 401 [i.10]), ETSI EN 319 422 [i.18] Qualified validation service for qualified electronic signatures ETSI TS 119 441 [i.19] (requiring compliance with ETSI EN 319 401 [i.10]), ETSI TS 119 442 [i.20], ETSI EN 319 102-1 [i.21], ETSI TS 119 102-2 [i.22] ETSI TS 119 172-4 [i.23] Qualified validation service for qualified electronic seals ETSI TS 119 441 [i.19] (requiring compliance with ETSI EN 319 401 [i.10]), ETSI TS 119 442 [i.20], ETSI EN 319 102-1 [i.21], ETSI TS 119 102-2 [i.22] ETSI TS 119 172-4 [i.23] Qualified preservation service for qualified electronic signatures ETSI EN 319 401 [i.10], ETSI TS 119 511 [i.24], ETSI TS 119 512 [i.25] Qualified preservation service for qualified electronic seals ETSI EN 319 401 [i.10], ETSI TS 119 511 [i.24], ETSI TS 119 512 [i.25] Qualified electronic registered delivery services ETSI EN 319 401 [i.10], ETSI EN 319 521 [i.26], ETSI EN 319 522 [i.27] ETSI EN 319 531 [i.28], ETSI EN 319 532 [i.29] ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 16 In order to meet Article 3.18 of Regulation (EU) No 910/2014 [i.1], CABs need to be accredited to carry out conformity assessment of a QTSP/QTS against the requirements of [i.1] on the basis of a conformity assessment scheme that includes requirements on CABs, requirements on the auditing rules under which CABs will carry out their conformity assessment and the effective set of criteria, control objectives and controls against which it will assess a QTSP/QTS with the aim of confirming that it fulfils the eIDAS Regulation [i.1] requirements. Such eIDAS compliant conformity assessment scheme can be defined by the CAB itself, by a competent EU MS supervisory body, or by any other body possessing the necessary technical competence. CABs need to make sure that the resulting conformity assessment report to be submitted by the assessed QTSP to the supervisory body, whether in the context of a 2-yearly regular audit (Article 20.1 of [i.1]) and potential associated surveillance audit(s) (see clause 4.5 of ETSI EN 319 403 [1]), an ad hoc audit (Article 20.2 of [i.1]) or an initiation audit (Article 21.1 of [i.1]) is such that it confirms - if such is the case - that the assessed (Q)TSP/(Q)TS fulfil all the applicable QTSP/QTS requirements of the eIDAS Regulation [i.1]. Since it is ultimately the competent supervisory body to which the CAR is notified by the assessed QTSP that will take the decision to grant or not the qualified status to the assessed QTSP/QTS, the notified CAR needs to contain sufficient information to demonstrate, in detail to the SB, that the assessed QTSP/QTS fulfils the requirements laid down in the eIDAS Regulation [i.1] and consequently deserves to be granted the qualified status. In the context of a QTSP generating or managing electronic signature creation data on behalf of the signatory as part of the requirements of Annex II of Regulation (EU) No 910/2014 [i.1], an additional list of standards can be of support: • CEN EN 419 221-5 [i.31]; • CEN EN 419 241-1 [i.32]; • CEN EN 419 241-2 [i.33]; • ETSI TS 119 431-1 [i.34]; • ETSI TS 119 431-2 [i.35]; • ETSI TS 119 432 [i.36]. ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 17 Annex B (informative): Bibliography • ENISA: "Guidelines on supervision of qualified trust services; Technical guidelines on trust services", December 2017. ISBN: 978-92-9204-190-8. NOTE: Available at https://www.enisa.europa.eu/publications/tsp-supervision. • ENISA: "Guidelines on termination of qualified trust services; Technical guidelines on trust services", December 2017. ISBN: 978-92-9204-244-8. NOTE: Available at https://www.enisa.europa.eu/publications/tsp-termination. ETSI ETSI TS 119 403-3 V1.1.1 (2019-03) 18 History Document history V1.1.1 March 2019 Publication
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
1 Scope
|
The present document defines the set of checks to be performed for testing conformance in the provision of Electronic Registered Delivery Services against the specific technical requirements defined in ETSI EN 319 522-3 [3], ETSI EN 319 522-4-1 [4] and ETSI EN 319 522-4-2 [5]. More specifically, the present document defines test assertions for testing conformance regarding: 1) The structure and contents of ERDS evidence as defined in ETSI EN 319 522-3 [3] (clause 6). 2) The structure and contents of new metadata defined in ETSI EN 319 522-3 [3] (clause 7). 3) The construction of AS4 ERDS messages (clause 8). 4) The generation of digital signatures in ERDS messages and ERDS evidence (clause 9). 5) Some aspects of the Common Service Interface (clause 10). 6) Relevant aspects of the provision of the service, namely: the generation of ERDS evidence following certain events and the security measures in the relevant interfaces defined in ETSI EN 319 522-1 [1] (clause 11). The present document does not define test assertions for testing conformance in the provision of Electronic Registered Delivery Services against technical requirements defined outside of any of the parts of ETSI EN 319 522 [1] to [6], namely, requirements for: AS4 [15], Business Document Metadata Service Location Version 1.0 (BDXL) [17], Service Metadata Publishing (SMP) Version 1.0 (SMP) [18] and digital signatures that are defined in their respective specifications.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
2 References
| |
71110a50b9eefbc38d87c6747ddad15a
|
119 524-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 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 EN 319 522-1: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 1: Framework and Architecture". [2] ETSI EN 319 522-2: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 2: Semantic contents". [3] ETSI EN 319 522-3: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 3: Formats". [4] ETSI EN 319 522-4-1: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 4: Bindings; Sub-part 1: Message delivery bindings". [5] ETSI EN 319 522-4-2: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 4: Bindings; Sub-part 2: Evidence and identification bindings". [6] ETSI EN 319 522-4-3: "Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 4: Bindings; Sub-part 3: Capability/requirements bindings". [7] OASIS Standard: "Test Assertions Model Version 1.0". ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 8 [8] CEF eIDAS Technical Sub-group (Version 1.2 - October 2019): "eIDAS SAML Attribute profile". [9] ETSI TS 119 134-4: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 4: Testing Conformance of XAdES baseline signatures". [10] ETSI EN 319 132-1: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures". [11] W3C® Recommendation 11 April 2013: "XML Signature Syntax and Processing Version 1.1". [12] IETF RFC 5035: "Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility". [13] W3C® Recommendation 28 October 2004: "XML Schema Part 2: Datatypes Second Edition". [14] ETSI TS 119 134-5: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures - Testing Conformance and Interoperability; Part 5: Testing Conformance of extended XAdES signatures". [15] OASIS Standard (January 2013): "AS4 Profile of ebMS 3.0 Version 1.0". [16] ETSI TS 119 312: "Electronic Signatures and Infrastructures (ESI); Cryptographic Suites". [17] OASIS Standard (August 2017): "Business Document Metadata Service Location Version 1.0". [18] OASIS Standard (August 2017): "Service Metadata Publishing (SMP) Version 1.0". [19] IETF RFC 3061 (February 2001): "A URN Namespace of Object Identifiers".
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-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] OASIS Standard: "Web Services Security X.509 Certificate Token Profile 1.1. OASIS Standard incorporating Approved Errata", 1 November 2006. [i.2] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [i.3] ETSI EN 319 142-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures". [i.4] 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.5] ETSI TS 119 612: "Electronic Signatures and Infrastructures (ESI); Trusted Lists".
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
3 Definition of terms, symbols and abbreviations
| |
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI EN 319 522-3 [3] apply. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 9
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
3.2 Symbols
|
Void.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AS4 Applicability Statement 4 BDXL Business Document Metadata Service Location CA Certification Authority CSI Common Service Interface DNS Domain Name Service ERD Electronic Registered Delivery ERDS Electronic Registered Delivery Service ERDSP Electronic Registered Delivery Service Provider EU European Union HTTP Hypertext Transfer Protocol IETF Internet Engineering Task Force MEPI Message and Evidence Push Interface MERI Message and Evidence Retrieval Interface MSI Message Submission Interface NID Namespace Identifier NSS Namespace Specific String OASIS Organization for the Advancement of Structured Information Standards QERDS Qualified Electronic Registered Delivery Service RFC Request for Comments RI Relay Interface SAML Security Assertion Markup Language S-ERDS Sender's ERDS SMP Service Metadata Publishing SOAP Simple Object Access Protocol TA Test Assertion UA User Agent URI Uniform Resource Identifier URL Universal Resource Locator URN Universal Resource Name XML eXtensible Mark-up Language
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
4 Overview
|
The present clause describes the main aspects of the technical approach used for specifying the whole set of tests to be performed for testing conformance to ERDS evidence and metadata defined in ETSI EN 319 522-3 [3]. In order to test conformance against the aforementioned specification, several types of tests are identified, namely: 1) Tests on the contents that are directly derived from the XML Schema referenced and copied in ETSI EN 319 522-3 [3]. 2) Tests on the contents that are not directly derived from the XML Schema referenced and copied in ETSI EN 319 522-3 [3] and that in consequence may not be tested by a XML Schema validator tool. 3) Tests on values of specific elements and/or attributes that cannot be tested by a XML Schema validator tool. 4) Tests on interrelationship between different components. Tests are defined as test assertions following the work produced by OASIS in "Test Assertions Model Version 1.0" [7]. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 10 For each component of the ERDS evidence and AS4 metadata defined in in ETSI EN 319 522-3 [3] the present document defines a number of test assertions corresponding to the requirements specified in the aforementioned specification. ETSI EN 319 522-3 [3] defines requirements for ERDS evidence formats and also for AS4 metadata components. For the purpose of identifying the whole set of test assertions required for testing conformance against ETSI EN 319 522-3 [3], the present document classifies the whole set of requirements specified in ETSI EN 319 522-3 [3] in the following groups. Each test assertion includes: 1) Unique identifier for further referencing. The identifiers of the assertions start with a code identifying the set of requirements the assertion corresponds to. 2) Reference to the Normative source for the test. 3) The Target of the assertion. In the normative part, this field identifies services whose technical implementation conforms to the requirements specified in ETSI ENs 319 522 [1] to [6]. 4) Prerequisite (optional) is, according to [7] "a logical expression (similar to a Predicate) which further qualifies the Target for undergoing the core test (expressed by the Predicate) that addresses the Normative Statement". It is used for building test assertions corresponding to requirements that are imposed under certain conditions. 5) Predicate fully and unambiguously defining the assertion to be tested by tools claiming conformance to the present document. 6) Prescription level: three levels are defined: mandatory, preferred and permitted, whose semantics is to be interpreted as described in clause 3.1.2 of [7]. 7) Tag: If assigned to test assertions it allows their categorization and grouping. Table 1 shows the prefixes used to refer to specific elements in the ERDS Evidence and AS4 metadata components associated to the URIs of the corresponding namespaces. Table 1: Prefixes used Namespace's URI Namespace's prefix http://uri.etsi.org/19522/v1# erds (or none) http://www.w3.org/2001/XMLSchema xs http://www.w3.org/2000/09/xmldsig# ds urn:oasis:names:tc:SAML:2.0:assertion saml 5 Test assertions for components that are used in metadata and in ERDS evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.1 Introduction
|
The next clauses define the set of test assertions for testing conformance of components that appear in both ERDS Evidence and XML metadata against ETSI EN 319 522-3 [3]. For each component, the two first test assertions are the ones is one that mandate to check that the inner structure of this element matches with the content model for that element in the XML Schema, i.e.: 1) that it contains only the children that are allowed, and that their order and cardinalities are correct; and 2) that it contains only the permitted attributes. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 11 Within the predicates for testing the inner structure of an XML element in terms of its children, the present document uses the following principles: 1) The order in listing the names of the children elements shall correspond with the order these children shall appear within the content of the checked element. 2) The description of the content model in terms of children elements uses the following special characters: - Children elements groups may be defined enclosing their names between round brackets (). - || indicate logical exclusive OR. - & indicates logical AND. - ! indicates logical NOT. 3) The cardinalities of each child element shall be indicated as follows: - Absence of indication indicates that the child element shall appear once at that position. - ? indicates that the child element/group of children elements may have 0 or 1 occurrences at that position. - * indicates that the child element/group of children elements may have 0, 1, or more than 1 occurrences at that position. - + indicates that the child element/group of children elements may have 1, or more than 1 occurrences at that position. EXAMPLE 1: The third test assertion (the one with code ERDS/EVIDENCE/EVENT_REASONS/TA_03) in clause 6.5 defines the following predicate for testing the XML children of the EventReason element as follows: "The content of EventReason element child of EventReasons element: Code Details?". This means that it has to be checked that: 1) there are 1 or 2 children; 2) that the first child element is always Code; and 3) that if there is a second element it has to be the Details child element. EXAMPLE 2: The second test assertion (the one with code ERDS/EVIDENCE/ROOT/TA_02) in clause 6.2 defines the following predicate for testing the attributes that do not declare namespaces within the Evidence element: "The set of attributes (leaving apart the attributes declaring namespaces) of the Evidence XML element, is as follows: version Id?". This means that it has to be checked that: 1) there are 1 or 2 attributes (leaving apart the ones that declare namespaces); 2) that version attribute is present; and 3) that if there is another attribute it has to be the Id attribute.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.2 Test assertions for instances auxiliary types
| |
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.2.1 Introduction
|
Clause 5.2 defines test assertions for the following auxiliary types that are used in both ERDS evidence and in ERDS metadata: • NonEmptyURIType, NonEmptyAttributedURIType; • NonEmptyMultiLangURIType NonEmptyStringType; • NonEmptyMultiLangURIListType; and ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 12 • AttributedNonEmptyStringType.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.2.2 Test assertions for instances of NonEmptyURIType type
|
ERDS/NON_EMPTY_URI/TA_01 TA Id ERDS/NON_EMPTY_URI/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate Instances of NonEmptyURIType type do not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_URI/TA_02 TA Id ERDS/NON_EMPTY_URI/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate Instances of NonEmptyURIType type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_URI/TA_03 TA Id ERDS/NON_EMPTY_URI/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate The value of an instance of NonEmptyURIType type is a valid URI reference Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_URI/TA_04 TA Id ERDS/NON_EMPTY_URI/TA_04 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate The value of an instance of NonEmptyURIType type is not an empty string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.2.3 Test assertions for instances of NonEmptyAttributedURIType type
|
ERDS/NON_EMPTY_ATTR_URI/TA_01 TA Id ERDS/NON_EMPTY_ATTR_URI/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate Instances of NonEmptyAttributedURIType type do not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_ATTR_URI/TA_02 TA Id ERDS/NON_EMPTY_ATTR_URI/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate The set of attributes (leaving apart the attributes declaring namespaces) of Instances of NonEmptyAttributedURIType type, is as follows: xml:lang scheme? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 13 ERDS/NON_EMPTY_ATTR_URI/TA_03 TA Id ERDS/NON_EMPTY_ATTR_URI/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate The value of an instance of NonEmptyAttributedURIType type is a valid URI reference Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_ATTR_URI/TA_04 TA Id ERDS/NON_EMPTY_ATTR_URI/TA_04 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate The value of an instance of NonEmptyAttributedURIType type is not an empty string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.2.4 Test assertions for instances of NonEmptyMultiLangURIType type
|
ERDS/NON_EMPTY_MULT_LANG_URI/TA_01 TA Id ERDS/NON_EMPTY_MULT_LANG_URI/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate Instances of NonEmptyMultiLangURIType type do not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_MULT_LANG_URI/TA_02 TA Id ERDS/NON_EMPTY_MULT_LANG_URI/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate The set of attributes (leaving apart the attributes declaring namespaces) of instances of NonEmptyMultiLangURIType type, is as follows: xml:lang Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_MULT_LANG_URI/TA_03 TA Id ERDS/NON_EMPTY_MULT_LANG_URI/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate The value of an instance of NonEmptyMultiLangURIType type is a valid URI reference Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_MULT_LANG_URI/TA_04 TA Id ERDS/NON_EMPTY_MULT_LANG_URI/TA_04 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate The value of an instance of NonEmptyMultiLangURIType type is not an empty string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 14 5.2.5 Test assertions for instances of NonEmptyMultiLangURIListType type ERDS/NON_EMPTY_MUL_TLANG_URI_LIST/TA_01 TA Id ERDS/NON_EMPTY_MULT_LANG_URI_LIST/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate The content of instances of NonEmptyMultiLangURIListType type, in terms of XML children element is as follows: URI+ Instances of type do not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_MUL_TLANG_URI_LIST/TA_02 TA Id ERDS/NON_EMPTY_MULT_LANG_URI_LIST/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.2 Target Conformance to ERDS Evidence and metadata content Predicate Instances of NonEmptyMultiLangURIListType type, do not have any XML attributes except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence For the URI child element of instances of NonEmptyMultiLangURIListType type, the test assertions defined in clause 5.2.4 shall apply.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.2.6 Test assertions for instances of NonEmptyStringType type
|
ERDS/NON_EMPTY_STRING/TA_01 TA Id ERDS/NON_EMPTY_STRING/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.3 Target Conformance to ERDS Evidence and metadata content Predicate Instances of NonEmptyStringType type do not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_STRING/TA_02 TA Id ERDS/NON_EMPTY_STRING/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.3 Target Conformance to ERDS Evidence and metadata content Predicate Instances of NonEmptyStringType type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/NON_EMPTY_STRING/TA_03 TA Id ERDS/NON_EMPTY_STRING/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.3 Target Conformance to ERDS Evidence and metadata content Predicate The value of an instance of NonEmptyStringType type is not an empty string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 15
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.2.7 Test assertions for instances of AttributedNonEmptyStringType type
|
ERDS/ATTR_NON_EMPTY_STRING/TA_01 TA Id ERDS/ATTR_NON_EMPTY_STRING/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.3 Target Conformance to ERDS Evidence and metadata content Predicate Instances of AttributedNonEmptyStringType type do not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ATTR_NON_EMPTY_STRING/TA_02 TA Id ERDS/ATTR_NON_EMPTY_STRING/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.3 Target Conformance to ERDS Evidence and metadata content Predicate The set of attributes (leaving apart the attributes declaring namespaces) of instances of AttributedNonEmptyStringType type, is as follows: type Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ATTR_NON_EMPTY_STRING/TA_03 TA Id ERDS/ATTR_NON_EMPTY_STRING/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.3 Target Conformance to ERDS Evidence and metadata content Predicate The value of an instance of AttributedNonEmptyStringType type is a non empty string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.2.8 Test assertions for instances of xs:boolean type
|
ERDS/BOOLEAN_TYPE/TA_01 TA Id ERDS/BOOLEAN_TYPE/TA_01 Normative source W3C Recommendation [13] Target Conformance to ERDS Evidence and metadata content Predicate Instances of xs:boolean type do not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/BOOLEAN_TYPE/TA_02 TA Id ERDS/BOOLEAN_TYPE/TA_02 Normative source W3C Recommendation [13] Target Conformance to ERDS Evidence and metadata content Predicate Instances of xs:boolean type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/BOOLEAN_TYPE/TA_03 TA Id ERDS/BOOLEAN_TYPE/TA_03 Normative source W3C Recommendation [13] Target Conformance to ERDS Evidence and metadata content Predicate The value of an instance of xs:boolean type is one of the following: true, false, 1 or 0 Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 16 5.3 Test assertions for instances of EntityIdentifierType type This clause defines test assertions for instances of EntityIdentifierType type. This type has the following instances: • In ERDS evidences: Identifier child element of instances of UserDetailsType, and Identifier child element of instances of DelegateDetailsType type. • In metadata: SenderId, ReplyTo, and RecipientId children elements of RelayMetadata element. ERDS/ENTITY_IDENTIFIER/TA_01 TA Id ERDS/ENTITY_IDENTIFIER/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.10 Target Conformance to ERDS Evidence and metadata content Predicate Instances of EntityIdentifierType type do not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ENTITY_IDENTIFIER/TA_02 TA Id ERDS/ENTITY_IDENTIFIER/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.10 Target Conformance to ERDS Evidence and metadata content Predicate The set of attributes (leaving apart the attributes declaring namespaces) of instances of EntityIdentifierType type, is as follows: IdentifierSchemeName Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ENTITY_IDENTIFIER/TA_03 TA Id ERDS/ENTITY_IDENTIFIER/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.10 Target Conformance to ERDS Evidence content Predicate The value of instances of EntityIdentifierType type is not empty Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence 5.4 Test assertions for instances of AssuranceLevelDetailsType type This clause defines test assertions for instances of AssuranceLevelDetailsType type. This type has the following instances: • In ERDS evidences: GlobalAssuranceLevel, IdentityProofAssuranceLevel, AuthenticationAssuranceLevel, and FederationAssuranceLevel children elements of instances of AssuranceLevelsDetailsType. NOTE: ETSI EN 319 522-3 [3] defines two XML types that have very similar names, namely: AssuranceLevelDetailsType, and AssuranceLevelsDetailsType. Please note the plural in "Levels" within the second one. Instances of the second type include components that are instances of the first one. Instances of the first type contain the details of one assurance level (for authentication for instance). Instances of the second type contain the details of several different assurance levels (the assurance level for authentication, and the assurance level for identity validation, for instance. • In metadata: RequiredAssuranceLevel child element of RelayMetadata element. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 17 ERDS/ASSURANCE_LEVEL/TA_01 TA Id ERDS/ASSURANCE_LEVEL/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The content of AssuranceLevelDetailsType type, in terms of XML children element is as follows: AssuranceLevel PolicyID? PolicyIDDetails? PolicyIDDetailsRessources? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ENTITY_IDENTIFIER/TA_02 TA Id ERDS/ENTITY_IDENTIFIER/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The instances of AssuranceLevelDetailsType type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ASSURANCE_LEVEL/TA_03 TA Id ERDS/ASSURANCE_LEVEL/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The AssuranceLevel child element of instances of AssuranceLevelDetailsType type does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ASSURANCE_LEVEL/TA_04 TA Id ERDS/ASSURANCE_LEVEL/TA_04 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The AssuranceLevel child element of instances of AssuranceLevelDetailsType type does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ASSURANCE_LEVEL/TA_05 TA Id ERDS/ASSURANCE_LEVEL/TA_05 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The value of a AssuranceLevel child element of instances of AssuranceLevelDetailsType is a valid URI reference Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ASSURANCE_LEVEL/TA_06 TA Id ERDS/ASSURANCE_LEVEL/TA_06 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The PolicyID child element of instances of AssuranceLevelDetailsType type does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 18 ERDS/ASSURANCE_LEVEL/TA_07 TA Id ERDS/ASSURANCE_LEVEL/TA_07 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The PolicyID child element of instances of AssuranceLevelDetailsType type does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ASSURANCE_LEVEL/TA_08 TA Id ERDS/ASSURANCE_LEVEL/TA_08 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The value of a PolicyID child element of instances of AssuranceLevelDetailsType is a valid URI reference Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ASSURANCE_LEVEL/TA_09 TA Id ERDS/ASSURANCE_LEVEL/TA_09 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The PolicyIDDetails child element of instances of AssuranceLevelDetailsType type does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/ASSURANCE_LEVEL/TA_010 TA Id ERDS/ASSURANCE_LEVEL/TA_010 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence and metadata content Predicate The PolicyIDDetails child element of instances of AssuranceLevelDetailsType type does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence For PolicyIDDetailsResources child element of instances of AssuranceLevelDetailsType, the test assertions defined in clause 5.2.5 shall apply.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.5 Test assertions for instances of xs:dateTime type
|
This clause defines test assertions for testing any component of type xs:dateTime. ERDS/DATE_TIME_TYPE/TA_01 TA Id ERDS/DATE_TIME_TYPE/TA_01 Normative source ETSI EN 319 522-3 [3], any clause where a XML element is defined as being of type xs:dateTime type Target Conformance to ERDS Evidence content Predicate Instances of xs:dateTime type do not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 19 ERDS/DATE_TIME_TYPE/TA_02 TA Id ERDS/EVENT_TIME/TA_02 Normative source ETSI EN 319 522-3 [3], any clause where a XML element is defined as being of type xs:dateTime type Target Conformance to ERDS Evidence content Predicate Instances of xs:dateTime type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/DATE_TIME_TYPE/TA_03 TA Id ERDS/EVENT_TIME/TA_03 Normative source ETSI EN 319 522-3 [3], any clause where a XML element is defined as being of type xs:dateTime type Target Conformance to ERDS Evidence content Predicate The value of Instances of xs:dateTime type is a date and time as specified in W3C Recommendation [13] Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
5.6 Test assertions for instances of ERDSPolicyIDType type
|
ERDS/EVIDENCE/ERDS_POLICY_ID/TA_01 TA Id ERDS/EVIDENCE/ERDS_POLICY_ID/TA_01 Normative source ETSI EN 319 522-3 [3], clauses 4.3.15 and 5.2.2.9 Target Conformance to ERDS Evidence content Predicate The content of instances ERDSPolicyIDType type, in terms of XML children element is as follows: PolicyID+ Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ERDS_POLICY_ID/TA_02 TA Id ERDS/EVIDENCE/ERDS_POLICY_ID/TA_02 Normative source ETSI EN 319 522-3 [3], clauses 4.3.15 and 5.2.2.9 Target Conformance to ERDS Evidence content Predicate Instances of ERDSPolicyIDType type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ERDS_POLICY_ID/TA_03 TA Id ERDS/EVIDENCE/ERDS_POLICY_ID/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.15 Target Conformance to ERDS Evidence content Predicate The PolicyID child of instances of ERDSPolicyIDType type does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ERDS_POLICY_ID/TA_04 TA Id ERDS/EVIDENCE/ERDS_POLICY_ID/TA_04 Normative source ETSI EN 319 522-3 [3], clause 4.3.15 Target Conformance to ERDS Evidence content Predicate The PolicyID child of instances of ERDSPolicyIDType type does not have any XML attributes except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 20 ERDS/EVIDENCE/ERDS_POLICY_ID/TA_05 TA Id ERDS/EVIDENCE/ERDS_POLICY_ID/TA_05 Normative source ETSI EN 319 522-3 [3], clause 4.3.15 Target Conformance to ERDS Evidence content Predicate The value of the PolicyID child of instances of ERDSPolicyIDType type is an URI reference value Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ERDS_POLICY_ID/TA_06 TA Id ERDS/EVIDENCE/ERDS_POLICY_ID/TA_06 Normative source ETSI EN 319 522-3 [3], clause 4.3.15 Target Conformance to ERDS Evidence content Precondition The scheme of the URI reference value of the PolicyID child of instances of ERDSPolicyIDType type is urn Predicate The value of PolicyID child of ERDSPolicyIDType element is an URN Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ERDS_POLICY_ID/TA_07 TA Id ERDS/EVIDENCE/ERDS_POLICY_ID/TA_07 Normative source ETSI EN 319 522-3 [3], clause 4.3.15 Target Conformance to ERDS Evidence content Precondition The value of PolicyID child of instances of ERDSPolicyIDType type is an URN Predicate The value of the Namespace Identifier (NID) of this URN is oid. Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ERDS_POLICY_ID/TA_08 TA Id ERDS/EVIDENCE/ERDS_POLICY_ID/TA_08 Normative source ETSI EN 319 522-3 [3], clause 4.3.15 Target Conformance to ERDS Evidence content Precondition The value of PolicyID child of instances of ERDSPolicyIDType type is an URN Predicate The value of the Namespace Specific String (NSS) of this URN is as specified in IETF RFC 3061 [19] Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6 Common test assertions for ERDS evidence
| |
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.1 Introduction
|
The next clauses define a set of test assertions that are common for any of the types of ERDS evidence specified in ETSI EN 319 522-3 [3]. The same considerations than the ones detailed in clause 5.1 shall apply in the test assertions defined throughout the whole clause 6.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.2 Test assertions for Evidence element
| |
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.2.1 XML children of Evidence per type of Evidence
|
This clause defines test assertions for testing the content, in terms of XML children elements, of the Evidence root element depending on the event that has triggered the generation of the ERDS Evidence, i.e. the value of the ERDSEventId child element. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 21 ERDS/EVIDENCE/ROOT/TA_01 TA Id ERDS/EVIDENCE/ROOT/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.3 Target Conformance to ERDS Evidence structure Predicate The Evidence XML element contains the ERDSEventId child element Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ROOT/TA_02 TA Id ERDS/EVIDENCE/ROOT/TA_02 Normative source ETSI EN 319 522-2 [2], clause 8.4, ETSI EN 319 522-3 [3], clause 5.2.2.3 Prerequisite The value of the ERDSEventId child element is EITHER "http://uri.etsi.org/19522/Event/SubmissionAcceptance" OR "http://uri.etsi.org/19522/Event/SubmissionRejection" Target Conformance to ERDS Evidence structure Predicate The content of the Evidence XML element, in terms of XML children element is as follows: EvidenceIdentifer ERDSEventId EventReasons? EventTime EvidenceIssuerPolicyID EvidenceIssuerDetails SenderDetails SenderDelegateDetails? RecipientDetails+ SubmissionTime MessageIdentifier UserContentInfo ExternalERDSDetails TransactionLogInformation? Extensions? ds:Signature Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ROOT/TA_03 TA Id ERDS/EVIDENCE/ROOT/TA_03 Normative source ETSI EN 319 522-2 [2], clause 8.4, ETSI EN 319 522-3 [3], clause 5.2.2.3 Prerequisite The value of the ERDSEventId child element is EITHER "http://uri.etsi.org/19522/Event/RelayAcceptance" OR "http://uri.etsi.org/19522/Event/RelayRejection" OR "http://uri.etsi.org/19522/Event/RelayFailure" Target Conformance to ERDS Evidence structure Predicate The content of the Evidence XML element, in terms of XML children element is as follows: EvidenceIdentifer ERDSEventId EventReasons? EventTime EvidenceIssuerPolicyID EvidenceIssuerDetails SenderDetails SenderDelegateDetails? RecipientDetails+ SubmissionTime? MessageIdentifier UserContentInfo ExternalERDSDetails TransactionLogInformation? Extensions? ds:Signature Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 22 ERDS/EVIDENCE/ROOT/TA_04 TA Id ERDS/EVIDENCE/ROOT/TA_04 Normative source ETSI EN 319 522-2 [2], clause 8.4, ETSI EN 319 522-3 [3], clause 5.2.2.5 Prerequisite The value of the ERDSEventId child element is EITHER "http://uri.etsi.org/19522/Event/NotificationForAcceptance" OR "http://uri.etsi.org/19522/Event/NotificationForAcceptanceFailure" OR "http://uri.etsi.org/19522/Event/ConsignmentAcceptance" OR "http://uri.etsi.org/19522/Event/ConsignmentRejection" OR "http://uri.etsi.org/19522/Event/AcceptanceRejectionExpiry" OR "http://uri.etsi.org/19522/Event/NotificationDelivered" OR "http://uri.etsi.org/19522/Event/ContentConsignment" OR "http://uri.etsi.org/19522/Event/ContentConsignmentFailure" OR "http://uri.etsi.org/19522/Event/NotificationAccessTracking" OR "http://uri.etsi.org/19522/Event/ContentAccessTracking" OR "http://uri.etsi.org/19522/Event/ConsignmentNotification" OR "http://uri.etsi.org/19522/Event/ConsignmentNotificationFailure" OR "http://uri.etsi.org/19522/Event/ContentHandover" OR "http://uri.etsi.org/19522/Event/ContentHandoverFailure" Target Conformance to ERDS Evidence structure Predicate The content of the Evidence XML element, in terms of XML children element is as follows: EvidenceIdentifer ERDSEventId EventReasons? EventTime EvidenceIssuerPolicyID EvidenceIssuerDetails SenderDetails SenderDelegateDetails? RecipientDetails+ RecipientsDelegateDetails* SubmissionTime? EvidenceRefersToRecipient MessageIdentifier UserContentInfo ExternalSystem? TransactionLogInformation? Extensions? ds:Signature Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ROOT/TA_05 TA Id ERDS/EVIDENCE/ROOT/TA_05 Normative source ETSI EN 319 522-2 [2], clause 8.4, ETSI EN 319 522-3 [3], clause 5.2.2.3 Prerequisite The value of the ERDSEventId child element is EITHER "http://uri.etsi.org/19522/Event/RelayToNonERDS" OR "http://uri.etsi.org/19522/Event/RelayToNonERDSFailure" Target Conformance to ERDS Evidence structure Predicate The content of the Evidence XML element, in terms of XML children element is as follows: EvidenceIdentifer ERDSEventId EventReasons? EventTime EvidenceIssuerPolicyID EvidenceIssuerDetails SenderDetails SenderDelegateDetails? RecipientDetails+ SubmissionTime? MessageIdentifier UserContentInfo ExternalSystem TransactionLogInformation? Extensions? ds:Signature Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ROOT/TA_06 TA Id ERDS/EVIDENCE/ROOT/TA_06 Normative source ETSI EN 319 522-2 [2], clause 8.4, ETSI EN 319 522-3 [3], clause 5.2.2.3 Prerequisite The value of the ERDSEventId child element is "http://uri.etsi.org/19522/Event/ReceivedFromNonERDS" Target Conformance to ERDS Evidence structure Predicate The content of the Evidence XML element, in terms of XML children element is as follows: EvidenceIdentifer ERDSEventId EventReasons? EventTime EvidenceIssuerPolicyID EvidenceIssuerDetails SenderDetails? RecipientDetails+ SubmissionTime? MessageIdentifier UserContentInfo ExternalSystem TransactionLogInformation? Extensions? ds:Signature Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 23 ERDS/EVIDENCE/ROOT/TA_07 TA Id ERDS/EVIDENCE/ROOT/TA_07 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.3 Target Conformance to ERDS Evidence structure Predicate The set of attributes (leaving apart the attributes declaring namespaces) of the Evidence XML element, is as follows: version Id? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ROOT/TA_08 TA Id ERDS/EVIDENCE/ROOT/TA_08 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.3 Target Conformance to ERDS Evidence content Predicate The value of version attribute of Evidence element is "EN319522v1.1.1" Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.3 Test assertions for EvidenceIdentifier element
|
ERDS/EVIDENCE/EVIDENCE_ID/TA_01 TA Id ERDS/EVIDENCE/EVIDENCEID/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.4 Target Conformance to ERDS Evidence content Predicate The EvidenceIdentifier element child of Evidence element does not have any XML child element Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVIDENCE_ID/TA_02 TA Id ERDS/EVIDENCE/EVIDENCEID/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.4 Target Conformance to ERDS Evidence content Predicate The EvidenceIdentifier element child of Evidence element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.4 Test assertions for ERDSEventId element
|
ERDS/EVIDENCE/EVENT_ID/TA_01 TA Id ERDS/EVIDENCE/EVENT_ID/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.5 Target Conformance to ERDS Evidence content Predicate The ERDSEventId element child of Evidence element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVENT_ID/TA_02 TA Id ERDS/EVIDENCE/EVENT_ID/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.5 Target Conformance to ERDS Evidence content Predicate The ERDSEventId child element of Evidence element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 24 ERDS/EVIDENCE/EVENT_ID/TA_03 TA Id ERDS/EVIDENCE/EVENT_ID/TA_03 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.5 Target Conformance to ERDS Evidence content Predicate The value of ERDSEventId element child of Evidence element is one of the values listed in Table 2, within clause 5.2.2.4 of ETSI EN 319 522-3 [3], i.e. "http://uri.etsi.org/19522/Event/SubmissionAcceptance" "http://uri.etsi.org/19522/Event/SubmissionRejection" "http://uri.etsi.org/19522/Event/RelayAcceptance" "http://uri.etsi.org/19522/Event/RelayRejection" "http://uri.etsi.org/19522/Event/RelayFailure" "http://uri.etsi.org/19522/Event/NotificationForAcceptance" "http://uri.etsi.org/19522/Event/NotificationForAcceptanceFailure" "http://uri.etsi.org/19522/Event/ConsignmentAcceptance" "http://uri.etsi.org/19522/Event/ConsignmentRejection" "http://uri.etsi.org/19522/Event/AcceptanceRejectionExpiry" "http://uri.etsi.org/19522/Event/NotificationDelivered" "http://uri.etsi.org/19522/Event/ContentConsignment" "http://uri.etsi.org/19522/Event/ContentConsignmentFailure" "http://uri.etsi.org/19522/Event/ConsignmentNotification" "http://uri.etsi.org/19522/Event/ConsignmentNotificationFailure" "http://uri.etsi.org/19522/Event/NotificationAccessTracking" "http://uri.etsi.org/19522/Event/ContentAccessTracking" "http://uri.etsi.org/19522/Event/ContentHandover" "http://uri.etsi.org/19522/Event/ContentHandoverFailure" "http://uri.etsi.org/19522/Event/RelayToNonERDS" "http://uri.etsi.org/19522/Event/RelayToNonERDSFailure" "http://uri.etsi.org/19522/Event/ReceivedFromNonERDS" Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.5 Test assertions for EventReasons element
|
ERDS/EVIDENCE/EVENT_REASONS/TA_01 TA Id ERDS/EVIDENCE/EVENT_REASONS/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.7 Target Conformance to ERDS Evidence content Predicate The content of the EventReasons element child of Evidence element, in terms of XML children element is as follows: EventReason+ Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVENT_REASONS/TA_02 TA Id ERDS/EVIDENCE/EVENT_REASONS/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.7 Target Conformance to ERDS Evidence content Predicate The EventReasons child element of Evidence element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVENT_REASONS/TA_03 TA Id ERDS/EVIDENCE/EVENT_REASONS/TA_03 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.7 Target Conformance to ERDS Evidence content Predicate The content of the EventReason child element of EventReasons element, in terms of XML children element is as follows: Code Details? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 25 ERDS/EVIDENCE/EVENT_REASONS/TA_04 TA Id ERDS/EVIDENCE/EVENT_REASONS/TA_04 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.7 Target Conformance to ERDS Evidence content Predicate The EventReason child element of EventReasons element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVENT_REASONS/TA_05 TA Id ERDS/EVIDENCE/EVENT_REASONS/TA_05 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.7 Target Conformance to ERDS Evidence content Predicate The Code element child of EventReason element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVENT_REASONS/TA_06 TA Id ERDS/EVIDENCE/EVENT_REASONS/TA_06 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.7 Target Conformance to ERDS Evidence content Predicate The Code element child of EventReason element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVENT_REASONS/TA_07 TA Id ERDS/EVIDENCE/EVENT_REASONS/TA_07 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.7 Target Conformance to ERDS Evidence content Predicate The value of Code element child of EventReason element is one of the values listed in tables 7 to 12, within clause 8.3.3 of ETSI EN 319 522-2 [2] Prescription level Recommended Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVENT_REASONS/TA_08 TA Id ERDS/EVIDENCE/EVENT_REASONS/TA_08 Normative source ETSI EN 319 522-3 [3],clause 5.2.2.7 Target Conformance to ERDS Evidence content Predicate The Details element child of EventReason element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVENT_REASONS/TA_09 TA Id ERDS/EVIDENCE/EVENT_REASONS/TA_09 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.7 Target Conformance to ERDS Evidence content Predicate The Details element child of EventReason element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.6 Test assertions for EventTime element
|
The test assertions defined in clause 5.5 shall apply for testing the EventTime child element of Evidence element. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 26
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.7 Test assertions for EvidenceIssuerPolidyID element
|
The test assertions defined in clause 5.6 shall apply for testing the EvidenceIssuerPolicyID child element.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.8 Test assertions for EvidenceIssuerDetails element
|
The test assertions defined in clause 6.22.1 shall apply for testing the EvidenceIssuerDetails child element.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.9 Test assertions for SenderDetails element
|
The test assertions defined in clause 6.22.2 shall apply for testing the SenderDetails child element.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.10 Test assertions for SenderDelegateDetails element
|
The test assertions defined in clause 6.22.2 shall apply for testing the SenderDelegateDetails child element.
|
71110a50b9eefbc38d87c6747ddad15a
|
119 524-1
|
6.11 Test assertions for RecipientDetails element
|
The test assertions defined in clause 6.22.2 shall apply for testing each RecipientDetails child element. 6.12 Test assertions for RecipientsDelegateDetails element The test assertions defined in clause 6.22.3 shall apply for testing the RecipientsDelegateDetails child element.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.