hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.1 Certificate Application | REG-6.2.3.1-01: The requirements identified in ETSI EN 319 411-1 [4], clause 6.3.1 shall apply. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.2 Certificate application processing | REG-6.2.3.2-01: The requirements identified in ETSI EN 319 411-1 [4], clause 6.3.2 shall apply. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.3 Certificate issuance | GEN-6.2.3.3-01: The following requirements GEN-6.3.3-01, GEN-6.3.3-02, GEN-6.3.3-05 identified in ETSI EN 319 411-1 [4], clause 6.3.3 shall apply. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.4 Certificate acceptance | OVR-6.2.3.4-01: The requirements identified in ETSI EN 319 411-1 [4], clause 6.3.4 shall apply. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.5 Key Pair and Certificate Usage | No policy requirement. NOTE : For WRPRC is not bound to a key pair. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.6 Certificate Renewal | REG-6.2.3.6-01: Before WRPRC renewal the provider shall repeat the verification of the WRP attributes to be included in the WRP register. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.7 Certificate Re-key | No policy requirement. NOTE: For WRPRC is not bound to a key pair. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 28 |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.8 Certificate Modification | No policy requirement. NOTE: Certificate modification refers to the issuance of a new certificate. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.9 Certificate Revocation and Suspension | REV-6.2.3.9-01: The requirements specified in ETSI EN 319 411-1 [4], clause 6.3.9 shall apply. In addition, the following shall apply: REV-6.2.3.9-02: The provider of WRPRC shall implement measures and automated mechanisms to continuously monitor any changes in the WRP national register in which WRP to whom they have issued WRPRCs are registered. REV-6.2.3.9-03: The provider of WRPRC shall enable receiving information's from the registrar when the registration of WRP is suspended or cancelled. REV-6.2.3.9-04: The provider of WRPRC shall revoke any WRPRC when the registration of the WRP is suspended or cancelled. REV-6.2.3.9-05: The WRPRC provider shall provide to the WRP registrar an interface to request certificate revocation following the procedure defined in the certificate policy or national registration policy. REV-6.2.3.9-06: The revocation procedure shall allow the WRP registrar to specify a reason, which can be descriptive rather than in a standard form, for the revocation. NOTE: Where the WRP intends to revoke a certificate, the revocation request may be submitted to the registrar of wallet-relying parties. The registrar then forwards the validated request to the WRPRC provider in accordance with national policy. This ensures consistent oversight and traceability in the certificate lifecycle. REV-6.2.3.9-07: The WRPRC provider shall revoke the WRPRC without undue delay when changes in the national register require it, in particular when: • the content of the WRPRC is no longer accurate or consistent with the registered information; or • the registration of the wallet-relying party is modified, suspended, or cancelled. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.10 Certificate Status Services | CSS-6.2.3.10-01: The requirements specified in ETSI EN 319 411-1 [4], clause 6.3.10 shall apply. NOTE 1 : WRPRC providers do not provide OCSP or CRL service. NOTE 2: IETF DRAFT Token Status List (TSL) [i.21] provides status list guidance. CSS-6.2.3.10-02: The WRPRC provider shall make the status list publicly available for validation. CSS-6.2.3.10-03: The status list shall be accessible over a stable and high-availability endpoint to ensure continuity of WRPRC validation. CSS-6.2.3.10-04: The WRPRC provider shall update the status list without undue delay upon a change in the status of a WRPRC. CSS-6.2.3.10-05: If a compressed encoding is used for the status list payload, the issuer shall ensure that standard compression mechanisms are used to maximize compatibility with EUDIWs. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.11 End of Subscription | No policy requirement. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 29 |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.3.12 Key Escrow and Recovery | No policy requirement. NOTE : For WRPRC is not bound to a key pair. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.4 Facility, Management and Operational Controls | OVR-6.2.4-01: The requirements identified in ETSI EN 319 411-1 [4], clause 6.4 shall apply. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.5 Technical Security Controls | OVR-6.2.5-01: The requirements identified in ETSI EN 319 411-1 [4], clause 6.5 shall apply. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.6 Certificate, Status List Profiles | |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.6.1 Certificate Profile | GEN-6.2.6.1-01: The WRPRC shall be issued according to the relevant certificate profile defined in clause 5.2. GEN-6.2.6.1-02: The WRPRC shall include the policy identifier defined in clause 6.1.3. GEN-6.2.6.1-03: The WRPRC shall include a unique identifier (id) for the WRPRC in a machine-readable format, suitable for use as a reference in a Status List. GEN-6.2.6.1-04: The status field shall include: • idx: A numeric string indicating the position in the bitstring; and • uri: A URI identifying the full status list credential. GEN-6.2.6.1-05: The value of idx shall be unique for each WRPRC issued by the same issuer and correspond to a valid index within the bitstring of the referenced status list credential. GEN-6.2.6.1-06: The WRPRC provider shall ensure that the status list credential referenced in status is published in a verifiable format. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.6.2 Status List Profile | REV-6.2.6.2-01: The WRPRC provider shall publish a status list structure that enables offline or near-real-time verification of the validity of issued WRPRC, including revocation. NOTE 1: IETF DRAFT Token Status List (TSL) [i.21] provides status list guidance. REV-6.2.6.2-02: The status list shall consist of a compact array of status bits, where each group of bits corresponds to the status of an individual WRPRC issued by the provider. NOTE 2: IETF DRAFT Token Status List (TSL) [i.21] provides status list guidance. REV-6.2.6.2-03: The WRPRC shall ensure that each WRPRC includes a reference to: • the status list's unique identifier (e.g. URI); and • the position index assigned to that WRPRC within the status list. NOTE 3: IETF DRAFT Token Status List (TSL) [i.21] provides status list guidance. REV-6.2.6.2-04: The status list shall support the following status semantics: • valid: the WRPRC is currently trusted and has not been revoked; • revoked: the WRPRC is no longer valid. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 30 REV-6.2.6.2-05: The status list shall be protected using a digital signature . |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.7 Compliance Audit and Other Assessment | NOTE: See ETSI EN 319 411-1 [4], clause 6.7. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.8 Other Business and Legal Matters | OVR-6.2.8-01: The requirements identified in ETSI EN 319 411-1 [4], clause 6.8 shall apply. |
4f00fbfc79e6e24a0b835fcacc3936a6 | 119 475 | 6.2.9 Other Provisions | OVR-6.2.9-01: The requirements identified in ETSI EN 319 411-1 [4], clause 6.9 shall apply. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 31 Annex A (normative): WRP identifiers A.1 OID identifiers The entitlement identifier for the WRPRC described in the present document is: id-etsi-wrpa-entitlement OBJECT IDENTIFIER ::= { itu-t(0) identified-organization(4) etsi(0) eudiwrpa(19475) entitlement(1)} A.2 WRP entitlement identifiers A.2.1 Service_Provider Entitlement Service_Provider Description General service provider OID id-etsi-wrpa-entitlement 1 URI https://uri.etsi.org/19475/Entitlement/Service_Provider A.2.2 QEAA_Provider Entitlement QEAA_Provider Description Qualified trust service provider issuing qualified electronic attestations of attributes OID id-etsi-wrpa-entitlement 2 URI https://uri.etsi.org/19475/Entitlement/QEAA_Provider A.2.3 Non_Q_EAA_Provider Entitlement Non_Q_EAA_Provider Description Trust service provider issuing non-qualified electronic attestations of attributes OID id-etsi-wrpa-entitlement 3 URI https://uri.etsi.org/19475/Entitlement/Non_Q_EAA_Provider A.2.4 PUB_EAA_Provider Entitlement PUB_EAA_Provider Description Public sector body or its agent issuing electronic attestations of attributes from authentic sources OID id-etsi-wrpa-entitlement 4 URI https://uri.etsi.org/19475/Entitlement/PUB_EAA_Provider A.2.5 PID_Provider Entitlement PID_Provider Description Provider of person identification data OID id-etsi-wrpa-entitlement 5 URI https://uri.etsi.org/19475/Entitlement/PID_Provider ETSI ETSI TS 119 475 V1.2.1 (2026-03) 32 A.2.6 QCert_for_ESeal_Provider Entitlement QCert_for_ESeal_Provider Description QTSP issuing qualified certificates for electronic seals OID id-etsi-wrpa-entitlement 6 URI https://uri.etsi.org/19475/Entitlement/QCert_for_ESeal_Provider A.2.7 QCert_for_ESig_Provider Entitlement QCert_for_ESig_Provider Description QTSP issuing qualified certificates for electronic signatures OID id-etsi-wrpa-entitlement 7 URI https://uri.etsi.org/19475/Entitlement/QCert_for_ESig_Provider A.2.8 rQSealCDs_Provider Entitlement rQSealCDs_Provider Description QTSP managing remote qualified electronic seal creation devices OID id-etsi-wrpa-entitlement 8 URI https://uri.etsi.org/19475/Entitlement/rQSealCDs_Provider A.2.9 rQSigCDs_Provider Entitlement rQSigCDs_Provider Description QTSP managing remote qualified electronic signature creation devices OID id-etsi-wrpa-entitlement 9 URI https://uri.etsi.org/19475/Entitlement/rQSigCDs_Provider A.2.10 ESig_ESeal_Creation_Provider Entitlement ESig_ESeal_Creation_Provider Description Non-qualified provider for remote signature/seal creation OID id-etsi-wrpa-entitlement 10 URI https://uri.etsi.org/19475/Entitlement/ESig_ESeal_Creation_Provider ETSI ETSI TS 119 475 V1.2.1 (2026-03) 33 A.3 Service provider sub-entitlements identifiers A.3.1 Payment Service Provider Identifiers Account Servicing Payment Service Provider https://uri.etsi.org/19475/SubEntitlement/psp/psp-as Payment Initiation Service Provider https://uri.etsi.org/19475/SubEntitlement/psp/psp-pi Account Information Service Provider https://uri.etsi.org/19475/SubEntitlement/psp/psp-ai Payment Service Provider issuing card-based payment instruments https://uri.etsi.org/19475/SubEntitlement/psp/psp-ic UnspecifiedPayment Service Provider https://uri.etsi.org/19475/SubEntitlement/psp/unspecified NOTE 1: Payment service providers roles and entitlements are as defined in ETSI TS 119 495 [i.12], clause 4.2. NOTE 2: Future editions of the present document may include other sub-entitlements defined at national or EU level. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 34 Annex B (normative): Wallet-Relying Party Attributes B.1 Introduction The present annex defines a common data model for representing WRP attributes as part of the issuance and validation of WRPAC and WRPRC. The attribute classes and structures described herein are intended to support consistent interpretation of registration data by wallets and relying parties. The data model reflects the current practices described in the EUDI Architecture Reference Framework (ARF) [i.7] and EU Technical Specifications TS2 [i.8] and TS5 [i.9]. The present annex purpose is to establish a clear and interoperable encoding format for certificate generation and processing. The attributes defined in the present annex are limited to those relevant for WRPs and are aligned with the requirements set out in Commission Implementing Regulation (EU) 2025/848 [i.2], Annex I. The specification does not impose any obligation on Member States to restructure their registers. The present annex serves as a normative basis for encoding and interpreting registration certificate content in a harmonised and machine-readable way. The data model makes use of standard data types such as String, Integer, Boolean, and structured classes (e.g. MultiLangString, Identifier, Credential). These are defined for clarity and are not intended to prescribe implementation details in national systems. The described format enables reliable interpretation of WRPRC payloads by digital wallets, including attribute filtering, language localization, and entitlement verification. B.2 Wallet-Relying Party Attributes Classes B.2.1 Class WalletRelyingParty Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] tradeName [0..1] string The trade name (common name, service name) of the WRP Annex I.2 supportURI [1..*] string The support URI for the service provided by the WRP Annex I.7(a) srvDescription [1..*] Array of MultiLangString objects Array of arrays with localized descriptions of the services provided by the WRP Annex I.8 intendedUse [0..*] IntendedUse The intended use to request specific electronic attestations of attributes from a wallet. Annex I.9 Annex I.10 isPSB [1..1] boolean The WRP is a public sector body Annex I.11 entitlement [1..*] string Set of entitlements of the WRP as specified in Annex A Annex I.12 providesAttestations [0..*] Credential Set of sub-entitlements of the WRP, present only if any entitlement of the WRP is of type QEAA_Provider, Non_Q_EAA_Provider, PUB_EAA_Provider or PID_Provider Annex I.13 supervisoryAuthority [1..1] LegalEntity The competent data protection supervisory authority Annex IV.3(g) Annex V.3(f) registryURI [1..1] string The URL for the national registry API of the registered WRP Article 3(5) usesIntermediary [0..*] WalletRelyingParty Indicates whether the WRP depends on use of at least one intermediary Annex I.14 ETSI ETSI TS 119 475 V1.2.1 (2026-03) 35 NOTE: The supportURI provides the contact point where users or other parties can reach the WRP for support purposes, including at least one channel for submitting data deletion requests, as required by the TS7 [i.10] and CIR (EU) 2025/848 [i.2], Annex I point 7(a). B.2.2 Class LegalEntity Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] legalPerson [0..1] LegalPerson Specific attributes of a legal person Only one legalPerson or naturalPerson attribute may be present. Annex I.1 naturalPerson [0..1] NaturalPerson Specific attributes of a natural person Only one legalPerson or naturalPerson attribute may be present. Annex I.1 identifier [0..*] Identifier Identifiers of the legal entity, as stated in an official record. Annex I.3 postalAddress [1..1] string The postal address of the legal entity. Annex I.4 country [1..1] string Specifies the alpha-2 country code according to ISO 3166-1 [8] of the country in which the legal entity is established, or the string "EU" for providers operating on a European level. Annex I.6 email [0..*] string Specifies one or more email addresses according to IETF RFC 5322 [11] of the legal entity. Annex I.7(c) phone [0..*] string Specifies one or more phone numbers of the legal entity starting with the '+' symbol as the international code prefix and the country code, followed by numbers only as specified in IETF RFC 5341 [12]. Annex I.7(b) infoURI [0..*] string Specifies one or more Unique Resource Identifiers (URIs) according to IETF RFC 8820 [13] with webpages for information about the legal entity. Annex I.5 NOTE: The infoURI provides a general-purpose web address where users and other parties can access public information about the WRP, such as its services, legal notices, terms of use, and privacy policies. It is intended for informational and transparency purposes and complements, but does not replace, the dedicated support contact points provided via supportURI. B.2.3 Class LegalPerson Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] legalName [1..*] string Legal name of the legal person, as specified in an official record. Annex I.1 establishedBylaw [0..*] Law Legal basis on which the legal person is established. - ETSI ETSI TS 119 475 V1.2.1 (2026-03) 36 B.2.4 Class NaturalPerson Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] givenName [1..1] string First name(s) of the natural person including middle name(s) where applicable, as specified in official records. Annex I.1 familyName [1..1] string Last name(s) or surnames of the natural person, as specified in official records. Annex I.1 dateOfBirth [0..1] string Data of birth of the natural person, as specified in official records. Annex I.1 placeOfBirth [0..1] string Place of birth of the natural person, as specified in official records. Annex I.1 B.2.5 Class Identifier Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] type [1..1] string Is the type of the identifier specified by a URI according to IETF RFC 8820 [13], whereas the following URIs are defined in the present document: • http://data.europa.eu/eudi/id/EO RI-No - Economic Operator Registration and Identification Number (EORI-No) according to (EU) No 1352/2013 [i.14] • http://data.europa.eu/eudi/id/LEI - Legal Entity Identifier (LEI) according to (EU) No 2022/1860 [i.4] and ISO 17442-1 [i.13] • http://data.europa.eu/eudi/id/EU ID - European Unique Identifier (EUID) according to (EU) 2020/2244 [i.15] and (EU) 2021/1042 [i.18] • http://data.europa.eu/eudi/id/VA TIN - Value Added Tax Identification Number (VATIN) according to the Council Directive 2006/112/EC [i.16] • http://data.europa.eu/eudi/id/TIN - Taxpayer Identification Number (TIN) • http://data.europa.eu/eudi/id/Ex cise - Excise Number according to Article 2 (12) of the Council Regulation (EC) No. 389/2012 [i.17] Annex I.3 identifier [1..1] string The identifier, which identifies the LegalEntity. Annex I.3 NOTE: Additional type identifiers may be defined at national or EU level. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 37 B.2.6 Class MultiLangString Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] lang [1..1] string Specifies the country code of the localized text. A two-letter Alpha-2 language code according to ISO 639 [15] (Set 1). - content [1..1] string The localized text as a string. - NOTE: This class supports the representation of multilingual content and is used to structure the srvDescription attribute as defined in clause B.2.1 or IntendedUse as defined in clause B.2.7. B.2.7 Class IntendedUse Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] purpose [1..*] MultiLangString One or more purposes of the intended data processing according to Article 5 1. (b) of Regulation (EU) 2016/679 [i.19]. Article 8.2(b) privacyPolicy [1..*] Policy Specifies the privacy policy of the intended use. Article 8.2(g) createdAt [1..1] string Validity start date for the intended use in ISO 8601-1 [16] YYYY-MM-DD format. - revokedAt [0..1] string End date for the validity of the intended use in ISO 8601-1 [16] YYYY-MM-DD format. - credential [1..*] Credential Set of potentially requestable attestations which may be requested by the WRP within the scope of the present intended use of data. Annex I.9 intendedUseIdentifier [1..1] string Registrar-provided unique identifier of the registered intended use. - NOTE: The intendedUseIdentifier is optional and reserved for future implementations. B.2.8 Class Policy Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] type [1..1] string The type of the policy in form of a URI according to IETF RFC 8820 [13], whereas the following URIs are defined in the present document: http://data.europa.eu/eudi/policy/privacy- policy - is a Privacy Policy. Article 8.2(g) policyURI [1..1] string The policy URI in form of a URL according to IETF RFC 8089 [14] where the policy is published. Article 8.2(g) NOTE: In Context of WRP attributes only Privacy policy is present. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 38 B.2.9 Class Credential Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] format [1..1] string Format of the attestation. Annex I.9 Annex I.13 meta [1..1] string Object defining additional properties defined per Credential Format [i.6] Section 6.1. Annex I.9 Annex I.13 claim [0..*] Claim An array of objects that specifies a set of attributes able to be requested by WRP. If claim is absent, the WRPRC does not declare any specific attributes intended to be requested by the WRP. Annex I.9 Annex I.13 NOTE: For guidance see OpenID4VP [i.6]. B.2.10 Class Claim Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] path [1..1] string A path pointer that specifies the path to a claim within the Credential. - values [0..1] string Array of strings, integers or boolean values that specifies the expected values of the claim. - NOTE: For guidance see OpenID4VP [i.6]. B.2.11 Class Law Attribute Multiplicity Type Description Link to CIR (EU) 2025/848 [i.2] lang [1..1] string Two-letter Alpha-2 language code according to ISO 639 [15] (Set 1). - legalBasis [1..1] string Legal basis according to which a LegalPerson is established as such or the access to a specific Claim is required or recommended. - NOTE: Only used in context of LegalPerson. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 39 Annex C (informative): Registration Certificate example Following code presents an example of the Registration Certificate: { "typ": "rc-wrp+jwt", "alg": "ES256", "x5c": [],} . { "name": "Example Company", "sub_ln": "Example Company GmbH", "sub": "LEIXG-529900T8BM49AURSDO55", "country": "DE", "registry_uri": "https://registrar.com", "srv_description": [ [ { "lang": "en-US", "value": "Awesome Service by Example Company" }, { "lang": "de-DE", "value": "Super Dienst von Example Company" } ] ], "entitlements": [ "https://uri.etsi.org/19475/Entitlement/Non_Q_EAA_Provider" ], "privacy_policy": "https://example.com/privacy-policy", "info_uri": "https://example.com/info", "support_uri": "https://example.com/support", "supervisory_authority": { "email": "supervisory@dpa.com", "phone": "+49 123 4567890", "uri": "https://dpa.com/supervisory-authority" }, "policy_id": [ "0.4.0.19475.3.1" ], "certificate_policy": "https://registrar.com/certificate-policy", "iat": 1683000000, "status": { "status_list": { "idx": 0, "uri": "https://example.com/statuslists/1" } }, "purpose": [ { "lang": "en-US", "value": "Required for checking the minimum age" }, { "lang": "de-DE", "value": "Benötigt für die Überprüfung des Mindestalters" } ], "credentials": [ { "format": "dc+sd-jwt", "meta": { "vct_values": [ "urn:eudi:pid:de:1" ] }, "claim": [ { "path": [ "age_equal_or_over", "18" ] } ETSI ETSI TS 119 475 V1.2.1 (2026-03) 40 ] }, { "format": "mso_mdoc", "meta": { "doctype_value": "eu.europa.ec.eudi.pid.1" }, "claim": [ { "path": [ "eu.europa.ec.eudi.pid.1", "age_over_18" ] } ] } ], "provides_attestations": [ { "format": "dc+sd-jwt", "meta": { "vct_values": [ "https://example.com/attestations/age_over_18" ] } } ], "intermediary": { "sub": "LEIXG-INTERMEDIARY-1234567890", "name": "Intermediary Services Ltd." } } ETSI ETSI TS 119 475 V1.2.1 (2026-03) 41 Annex D (informative): WRP registration use cases D.1 Use case 1: Integrated model In this model, the registrar and certificate provider are the same entity. The registration and issuance processes are tightly coupled and managed under a single authority. This ensures streamlined control, traceability, and alignment between registration records and issued certificates. It may simplify governance and reduce latency but requires the registrar to maintain full certificate lifecycle capabilities. D.2 Use case 2: Registrar-initiated issuance In this model, the registrar completes the registration and then initiates the certificate issuance by instructing a designated certificate provider. The WRP does not need to interact directly with the provider. This model ensures strong linkage between registration and WRP certificate issuance, with the registrar controlling when and how certificates are generated. It is suitable when Member States centralize the registration workflow while outsourcing issuance. NOTE 1: WRPAC and WRPRC may be separate entities. NOTE 2: Model allows the authorization of one or more WRPAC and/or WRPRC providers. D.3 Use case 3: RP-initiated issuance post-registration In this model, the registrar performs the registration, and later the relying party contacts a certificate provider to request issuance. The provider is responsible for verifying that the relying party is listed in the national register and that the data matches. This model enables decentralised certificate management and can accommodate market-based competition among WRPAC and WRPRC providers, while still relying on authoritative registration data. D.4 Use case 4: Provider-assisted registration In this model, the WRPAC or WRPRC provider acts as a proxy to the registrar, handling both the submission of registration data and the issuance of the certificate once the registration is confirmed. This enables one-stop-shop onboarding for relying parties and reduces complexity on the registrar's side. It is particularly useful when service providers assist relying parties in navigating national registration procedures. NOTE 1: WRPAC and WRPRC may be separate entities. NOTE 2: Model allows the authorization of one or more WRPAC and/or WRPRC providers. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 42 Annex E (informative): Regulatory requirements for WRP certificate providers E.1 Wallet-Relying Party Access Certificates (WRPAC) In accordance with Article 7 and Annex IV of the CIR (EU) 2025/848 [i.2], WRPACs are issued exclusively to entities whose registration as WRP has been validated and is active. Each WRPAC is associated with a unique cryptographic key pair, where the private key is securely managed and controlled by the WRP, and used to generate electronic signatures or electronic seals of the request sent to EUDIW. WRPAC include the following WRP attributes as specified in Annex I of the CIR (EU) 2025/848 [i.2], Annex I: 1) The name of the wallet-relying party, as stated in an official record together with identification data of that official record (CIR Annex I point 1). 2) A user-friendly name of the wallet-relying party (CIR Annex I point 2). 3) One or more identifiers of the wallet-relying party (such as EORI, LEI, or VAT numbers) (CIR Annex I point 3). 4) Uniform Resource Locator (URL) belonging to the wallet-relying party (CIR Annex I point 5). 5) Indicator of the Member State where the wallet-relying party is established (CIR Annex I point 6). 6) Contact information of the wallet-relying party (CIR Annex I point 7). 7) Machine processable reference to the applicable certificate policy (CIR Annex IV point 3(k)). E.2 Wallet-Relying Party Registration Certificates (WRPRC) In accordance with Article 8 of the CIR (EU) 2025/848 [i.2], Member States may mandate or allow the issuance of WRPRC by authorized providers of wallet-relying party registration certificates. These certificates are only issued to WRPs with a valid entry in a national register and reflect the relying party's declared use cases, entitlements, and data request policies. WRPRC include the following WRP attributes as specified in Annex I of the CIR (EU) 2025/848 [i.2] Annex I: 1) The name of the wallet-relying party, as stated in an official record together with identification data of that official record (CIR Annex I point 1). 2) A user-friendly name of the wallet-relying party (CIR Annex I point 2). 3) One or more identifiers of the wallet-relying party (such as EORI, LEI, or VAT numbers) (CIR Annex I point 3). 4) Uniform Resource Locator (URL) belonging to the wallet-relying party (CIR Annex I point 5). 5) Indicator of the Member State where the wallet-relying party is established (CIR Annex I point 6). 6) Additional attributes specifying entitlements and intended use (CIR Annex I points 8-15): - The list of data or attributes the relying party declared to request for each intended use. - A user-friendly description and technical name for each intended use. - An indication of whether the relying party is a public sector body. - One or more formal entitlements (roles), (CIR Annex I point 12). ETSI ETSI TS 119 475 V1.2.1 (2026-03) 43 - A URL to the privacy policy explaining the processing of EUDIW data. - A general access policy used by the EUDIW to detect and signal out-of-scope data requests. - A machine-readable reference to the applicable certificate policy and practice statement (CIR Annex V). NOTE 1: URL in point 4 may be optional for WRPRC but is required for WRPAC. WRPRC is formatted as signed JSON Web Tokens (JWT) [6] or CBOR Web Tokens (CWT) [7] and comply with the syntactic and semantic requirements specified in Annex V of CIR (EU) 2025/848 [i.2]. Both tokens have to be signed with an Advanced Electronic Signature (ADES) with the B-B profile. WRPRCs are issued by providers of wallet-relying party registration certificates that may be recognized as trust service providers. While no separated policy specification currently governs the issuance of WRPRCs, the present document specifies in clause 6.3 the requirements applicable to issuers of such certificates. These include provisions related to syntactic and semantic compliance with Annex V of CIR (EU) 2025/848 [i.2], signing formats, certificate lifecycle management, and the alignment of issued content with national registration and authorization processes. Issuers also comply with the relevant general requirements defined in ETSI EN 319 411-1 [4], including those related to identity verification, certificate management, and trust service provider obligations. NOTE 2: To support recognition and transparency, providers of Wallet-Relying Party Registration Certificates (WRPRCs) may be presented on the EU Trusted List, either as qualified or non-qualified trust service providers, depending on the applicable national supervision and conformity assessment framework. E.3 Registration and access certificate relation WRPRC and WRPAC serve distinct but complementary purposes within the EUDIW ecosystem. While the WRPAC ensures WRP authentication, the WRPRC conveys the WRP's declared use cases and data access policies to both the EUDIW and the end user. Together, they form a dual-layer trust framework, where the WRPAC guarantees the WRP's identity and authentication, and the WRPRC ensures entitlements, transparency and data minimization. Table E.1 outlines the key differences and relationships between these two types of certificates, CIR (EU) 2025/848 [i.2]. Table E.1: WRPAC and WRPRC comparison Aspect WRPAC WRPRC Purpose Authenticates WRP in interactions with the wallet Provides intended use and attributes requested by the WRP or information about service provided to the wallet Regulation Basis Article 7, Annex IV Article 8, Annex V Issued To Registered WRP Registered WRP Includes Entitlements No Yes Includes Intended Use No Yes Used For WRP authentication Transparency and user awareness Contains Contact Info Yes (Annex I, 1-3, 5-7) Yes (Annex I, 1-3, 5-7) Cryptographic Binding X.509 certificate with private key No, claim bound to the Access Certificate by identifier Table E.2 lists the attributes identifying a WRP, as defined in Annex I of CIR (EU) 2025/848 [i.2] present in both WRPAC and WRPRC. NOTE: While the CIR (EU) 2025/848 [i.2] applies, each certificate conveys distinct information. A WRPRC is always presented together with a WRPAC. To avoid duplication, information included in the WRPAC it is not recommended be repeated in the WRPRC. This separation facilitates attribute discovery by the EUDI Wallet, as each attribute can be clearly located in one certificate or the other. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 44 Table E.2: WRP identification attributes WRP attribute WRP Information element (Annex I) Included in WRPAC (Annex IV) Included in WRPRC (Annex V) Notes Subject CIR (EU) 2025/848 [i.2], Annex I point 1 Name & ID data from official record Mandatory where applicable Mandatory where applicable - Friendly name CIR (EU) 2025/848 [i.2], Annex I point 2 User-friendly name Optional Mandatory if subject is not applicable Optional Mandatory if subject is not applicable - Identifier(s) CIR (EU) 2025/848 [i.2], Annex I point 3 Identifiers (EORI, VAT, etc.) Mandatory at least one Mandatory at least one CIR (EU) 2025/848 [i.2] states possibility use of many identifiers, for interoperability reasons at least one of identifiers is the same in both certificates URL CIR (EU) 2025/848 [i.2], Annex I point 5 WRP Uniform Resource Locator URL Mandatory Optional - Country code CIR (EU) 2025/848 [i.2], Annex I point 6 Country code for certain identifiers Mandatory Mandatory - Intermediary CIR (EU) 2025/848 [i.2], Annex I point 15 Association to the intermediary that the WRP is relying upon No Optional It includes identifier of the intermediary present in its WRPAC When a WRP acts through an intermediary, the intermediary presents its own WRPAC to authenticate the connection with the EUDIW. In parallel, the WRP provides a WRPRC that identifies the final relying party, states the intended purpose, and defines the authorized data access for the transaction. In accordance with point 14 of Annex I to CIR (EU) 2025/848 [i.2], the WRPRC also indicates the intermediary involved. A separate WRPRC is therefore required for each intermediary, explicitly binding the intermediary and the final WRP. This arrangement provides the EUDIW with transparent information about the actual relying party behind the request and ensures traceability, accountability, and enforcement of attribute access policies across the data access chain. If no WRPRC is available, the EUDIW retrieves the relevant registration data directly from the national register, using the data structures defined in the present document. In such cases, the register acts as the authoritative source of the relying party's identity, purpose, and entitlements, ensuring that the wallet can still enforce attribute access policies and provide informed user consent even without a WRPRC. ETSI ETSI TS 119 475 V1.2.1 (2026-03) 45 Annex F (informative): Change history Date Version Information about changes September 2025 V1.1.1 First publication January 2026 V1.2.1 Compliance errors in Json schema, editorial corrections ETSI ETSI TS 119 475 V1.2.1 (2026-03) 46 History Version Date Status V1.1.1 October 2025 Publication V1.2.1 March 2026 Publication |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 1 Scope | The present document specifies requirements on the content end entity certificates used by Person Identification Data (PID) providers, Public Sector Body's Electronic Attestation of Attributes (PSBEAA) providers, Electronic Attestation of Attributes (EAA) providers, Qualified Electronic Attestation of Attributes (QEAA) providers and Wallet providers. This profile is based on ETSI EN 319 412-2 [5] and ETSI EN 319 412-3 [6] which in turn build on IETF RFC 5280 [1] for generic profiling of Recommendation ITU-T X.509 | ISO/IEC 9594-8 [i.3] and also uses IETF RFC 5755 [i.8] for attribute issuer certificate profiles. This profile aims at supporting the requirements of the Regulation (EU) No 910/2014 [i.5] as amended by Regulation (EU) No 2024/1183 [i.7]. The scope of the present document is primary limited to facilitate interoperable processing and display of certificate information. This profile therefore excludes support for some certificate information content options, which can be perfectly valid in a local context but which are not regarded as relevant or suitable for use in widely deployed applications. The present document focuses on requirements on certificate content. Requirements on decoding and processing rules are limited to aspects required to process certificate content defined in the present document. Further processing requirements are only specified for cases where it adds information that is necessary for the sake of interoperability. Certain applications or protocols impose specific requirements on certificate content. The present document is based on the assumption that these requirements are adequately defined by the respective application or protocol. It is therefore outside the scope of the present document to specify such application or protocol specific certificate content. The present document aims to meet the requirements of the Regulation (EU) No 910/2014 [i.5] as amended by Regulation (EU) No 2024/1183 [i.7], and architectural reference framework as available at time of preparation of the present document: • Regulation (EU) No 2024/1183 [i.7] Article 45f 1 b) requirements on qualified certificate of PSBEAA • Regulation (EU) No 2024/1183 [i.7] Annex V g) requirements on use of qualified electronic signature seal of QEAA • Regulation (EU) No 2024/1183 [i.7] Annex VII g) requirements on use of qualified electronic signature seal of PSBEAA |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 2 References | |
c00c8c819a3d35432430543eea0429a5 | 119 412-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 in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". [2] IETF RFC 9110: "HTTP Semantics". [3] IETF RFC 2818: "HTTP Over TLS". [4] ETSI EN 319 412-5: "Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 5: QCStatements". ETSI ETSI TS 119 412-6 V1.1.1 (2025-09) 7 [5] ETSI EN 319 412-2: "Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 2: Certificate profile for certificates issued to natural persons". [6] ETSI EN 319 412-3: "Electronic Signatures and Infrastructures (ESI); Certificate Profiles; Part 3: Certificate profile for certificates issued to legal persons". [7] ISO 3166: "Codes for the representation of names of countries and their subdivisions". |
c00c8c819a3d35432430543eea0429a5 | 119 412-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 may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] Directive 1999/93/EC of the European Parliament and of the Council of 13 December 1999 on a Community framework for electronic signatures. [i.2] ETSI EN 319 401: "Electronic Signatures and Trust Infrastructures (ESI); General Policy Requirements for Trust Service Providers". [i.3] Recommendation ITU-T X.509 | ISO/IEC 9594-8: "Information technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks". [i.4] ETSI EN 319 412-1: "Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 1: Overview and common data structures". [i.5] 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.6] ISO/IEC 18013-5:2021: "Personal identification — ISO-compliant driving licence — Part 5: Mobile driving licence (mDL) application". [i.7] Regulation (EU) 2024/1183 of the European Parliament and of the Council of 11 April 2024 amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity Framework. [i.8] IETF RFC 5755: "An Internet Attribute Certificate Profile for Authorization". 3 Definition of terms, symbols, abbreviations and notations |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 319 401 [i.2], ETSI EN 319 412-1 [i.4], Regulation (EU) No 910/2014 [i.5] and the following apply: Electronic Attestation of Attributes (EAA) provider: trust service provider who provides electronic attestation of attributes Person Identification Data (PID) provider: body responsible for ensuring that the person identification data is associated with the European Digital Identity Wallet in accordance with Article 5a(5), point (f) of Regulation (EU) No 910/2014 [i.5] ETSI ETSI TS 119 412-6 V1.1.1 (2025-09) 8 PID provider attribute sign/seal certificate: certificate corresponding to a private key used to sign the PID attribute attestations Public Sector Body's Electronic Attestation of Attributes (PSBEAA) provider: issuer of electronic attestations of attributes by or on behalf of a public sector body responsible for an authentic source Qualified Electronic Attestation of Attributes (QEAA) provider: qualified trust service provider who provides qualified electronic attestation of attributes Wallet provider: provider of an European Digital Identity Wallet Wallet provider sign/seal certificate: certificate corresponding to the private used to sign the output of the Wallet provider |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 3.2 Symbols | Void. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation 1 CA Certification Authority EAA Electronic Attestation of Attributes OCSP Online Certificate Status Protocol OID Object IDentifier PID Person Identification Data PSBEAA Public Sector Body's Electronic Attestation of Attributes QEAA Qualified Electronic Attestation of Attributes |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 3.4 Notations | The requirements identified in the present document are preceded by a 3-letter prefix to denote the applicability to specific profiles as covered by the present multi-part deliverable. Each requirement is identified as follows: <3 letters profile> - < the clause number> - <2 digit number - incremental>. The profile is identified as follows: • PID: Requirements specifically applicable to PID provider certificate profiles. • WAL: Requirements specifically applicable to Wallet provider certificate profiles. • EAA: Requirements specifically applicable to Electronic Attribute Attestation provider (EAA). • QEA: Requirements specifically applicable to Qualified Electronic Attribute Attestation provider (QEAA). • PSB: Requirements specifically applicable to Public Sector Body Electronic Attribute Attestation provider (PSBEAA). The management of the requirement identifiers for subsequent editions of the present document is as follows: • When a requirement is inserted at the end of a clause, the 2 digit number above is incremented to the next available digit. • When a requirement is inserted between two existing requirements, capital letters appended to the previous requirement identifier are used to distinguish new requirements. • The requirement identifier for a deleted requirement is left and completed with "Void". ETSI ETSI TS 119 412-6 V1.1.1 (2025-09) 9 • The requirement identifier for a modified requirement is left void and the modified requirement is identified by capital letter(s) appended to the initial requirement number. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 4 PID Provider sign/seal certificate profile requirements | |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 4.1 General requirements | PID-4.1-01: All certificate fields and extensions shall comply with ETSI EN 319 412-2 [5] with the amendments specified in the present document. PID-4.1-02: Certificate extensions shall not be marked critical unless criticality is explicitly allowed or required in the present document or in IETF RFC 5280 [1]. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 4.2 Issuer | PID-4.2-01: The issuer shall be: a) as specified in ETSI EN 319 412-2 [5], clause 4.2.3; or b) as defined for the subject if the PID certificate is self certified. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 4.3 Subject | PID-4.3-01: [CONDITIONAL] If the PID provider is a natural person the subject shall be as specified in ETSI EN 319 412-2 [5], clause 4.2.4. PID-4.3-02: [CONDITIONAL] If the PID provider is a legal person the subject shall be as specified in ETSI EN 319 412-3 [6], clause 4.2.1. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 4.4 Extensions | |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 4.4.1 Key usage | PID-4.4.1-01: The key usage extension shall be as specified in ETSI EN 319 412-3 [6], clause 4.3.1. PID-4.4.1-02: Type C may also be used. NOTE: Due to the requirements of ISO/IEC 18013-5 [i.6]. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 4.4.2 Subject Key Identifier | PID-4.4.2-01: The subject key identifier shall be present, and shall be set as defined within IETF RFC 5280 [1], clause 4.2.1.2. NOTE: Based on IETF RFC 5280 [1], this extension is non-critical. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 4.4.3 Authority Information Access | PID-4.4.3-01 [CONDITIONAL]: If the PID attribute sign/seal certificate is not self signed (PID-5.3.1-1 option a) the Authority Information Access extension shall be present. PID-4.4.3-02: The Authority Information Access extension shall include an accessMethod OID, id-ad-caIssuers, with an accessLocation value specifying at least one access location of a valid CA certificate of intermediate CA. PID-4.4.3-03: At least one accessLocation shall use the http (http://) IETF RFC 9110 [2] scheme or https (https://) IETF RFC 2818 [3] scheme. ETSI ETSI TS 119 412-6 V1.1.1 (2025-09) 10 4.5 Indicator that the certificate is for a PID Provider sign/seal certificate PID-4.5-01: The certificate shall contain the QcType qcStatement as defined in ETSI EN 319 412-5 [4], with the value id-etsi-qct-pid defined in Annex A of the present document. 5 Wallet Provider sign/seal certificate profile requirements |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 5.1 General requirements | WAL-5.1-01: The requirements of clauses 4.1 to 4.4 on certificate profiles shall apply. 5.2 Indicator that the certificate is for a Wallet Provider sign/seal certificate WAL-5.2-01: The certificate shall contain the QcType qcStatement as defined in ETSI EN 319 412-5 [4], and the values shall be set to id-etsi-qct-wal defined in Annex A of the present document. 6 EAA Provider attribute sign/seal certificate profile requirements |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 6.1 General certificate requirements | EAA-6.1-01: If the Provider is a natural person ETSI EN 319 412-2 [5] on certificate profiles shall apply. EAA-6.1-02: If the Provider is a legal person ETSI EN 319 412-3 [6] on certificate profiles shall apply. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 6.2 Other requirements | EAA-6.2-01: If OCSP is used for the revocation validation of an Attribute Attestation, then the OCSP Responder certificate shall be issued (signed) by this provider sign/seal certificate. EAA-6.2-02: If CRL is used for revocation of an Attribute Attestation, then the CRL shall be signed by this provider sign/seal certificate. NOTE: These are detailed in IETF RFC 5755 [i.8], clause 4.5. 7 QEAA Provider attribute qualified sign/seal certificate profile requirements |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 7.1 General certificate requirements | QEA-7.1-01: If the Provider is a natural person ETSI EN 319 412-2 [5] on certificate profiles shall apply. QEA-7.1-02: If the Provider is a legal person ETSI EN 319 412-3 [6] on certificate profiles shall apply. ETSI ETSI TS 119 412-6 V1.1.1 (2025-09) 11 QEA-7.1-03: The issuer of this certificate shall be a QTSP meeting the relevant regulatory requirements specified in Regulation 910/2014 [i.5]. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 7.2 Extensions | |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 7.2.1 Authority Information Access | QEA-7.2.1-01: The Authority Information Access extension shall be present. QEA-7.2.1-02: The Authority Information Access extension shall include an accessMethod OID, id-ad-caIssuers, with an accessLocation value specifying at least one access location of a valid CA certificate of intermediate CA. QEA-7.2.1-03: At least one accessLocation shall use the http (http://) IETF RFC 9110 [2] scheme or https (https://) IETF RFC 2818 [3] scheme. QEA-7.2.1-04: If OCSP is supported by the certificate issuer, ETSI EN 319 412-2 [5], clause 4.3.11 shall apply. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 7.3 Other requirements | QEA-7.3-01: The requirements of clause 6.2 shall apply. 8 PSBEAA Provider attribute issuer qualified sign/seal certificate profile requirements |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 8.1 General certificate requirements | PSB-8.1-01: If the Provider is a natural person ETSI EN 319 412-2 [5] on certificate profiles shall apply. PSB-8.1-02: If the Provider is a legal person ETSI EN 319 412-3 [6] on certificate profiles shall apply. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 8.2 Extensions | |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 8.2.1 Authority Information Access | PSB-8.2.1-01: The Authority Information Access extension shall be present. PSB-8.2.1-02: The Authority Information Access extension shall include an accessMethod OID, id-ad-caIssuers, with an accessLocation value specifying at least one access location of a valid CA certificate of intermediate CA. PSB-8.2.1-03: At least one accessLocation shall use the http (http://) IETF RFC 9110 [2] scheme or https (https://) IETF RFC 2818 [3] scheme. PSB-8.2.1-04: If OCSP is supported by the certificate issuer, ETSI EN 319 412-2 [5], clause 4.3.11 shall apply. 8.3 Set of data on the National or EU Law under which PSBEAA provider is established PSB-8.3-01: The certificate shall contain the QcPSB qcStatement, as defined in Annex A of the present document. PSB-8.3-02: The QcPSB qcStatement shall contain the identification for the law under which the PSBEAA is established responsible for the authentic source. PSB-8.3-03: The QcPSB qcStatement shall contain an unambiguous identification for the authentic source. ETSI ETSI TS 119 412-6 V1.1.1 (2025-09) 12 PSB-8.3-04: The QcPSB qcStatement shall contain either the ISO 3166 [7] alpha-2 country codes for applicable law, or in the case of European Union law 'EU'. NOTE: The identifier is in the form as appropriate to national or European Union legislation. |
c00c8c819a3d35432430543eea0429a5 | 119 412-6 | 8.4 Other requirements | PSB-8.4-01: The requirements of clause 6.2 shall apply. ETSI ETSI TS 119 412-6 V1.1.1 (2025-09) 13 Annex A (normative): ASN.1 declarations ETSIQCstatementsMod { itu-t(0) identified-organization(4) etsi(0) id-qc-statements-eidas2-provider- extension(194126) id-mod(0) id-mod-qc-statements-extension(0) v1(0)} DEFINITIONS EXPLICIT TAGS ::= BEGIN -- EXPORTS All – IMPORTS QC-STATEMENT, qcStatement-2 FROM PKIXqualified97 {iso(1) identified-organization(3) dod(6) internet(1) security(5) mechanisms(5) pkix(7) id-mod(0) id-mod-qualified-cert-97(35)}; -- new QC type identifiers id-etsi-eidas2-qct-extensions OBJECT IDENTIFIER ::= { itu-t(0) identified-organization(4) etsi(0) qct-extension (194126) 1 } id-etsi-qct-pid OBJECT IDENTIFIER ::= { id-etsi-eidas2-qct-extensions 1 } -- Certificate for PID provider sign/seal certificate id-etsi-qct-wal OBJECT IDENTIFIER ::= { id-etsi-eidas2-qct-extensions 2 } -- Certificate for Wallet provider sign/seal certificate -- PSB certificate mandatory data esi4-qcStatement-10 QC-STATEMENT ::= { SYNTAX QcPSB IDENTIFIED BY id-etsi-qcs-QcPSB } QcPSB ::= SEQUENCE { countryOfLegislation PrintableString (SIZE (2)) (CONSTRAINED BY { -- ISO 3166 alpha-2 country codes or 'EU' -- }), -- this field shall contain the alpha-2 country code of the legislation framework of public sector body -- In the case of European Union law 'EU' shall be used in place of the country code authSourceIdentification UTF8String, -- this field is for the unique identification of authentic source legislationIdentification UTF8String } END ETSI ETSI TS 119 412-6 V1.1.1 (2025-09) 14 History Document history V1.1.1 September 2025 Publication |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 1 Scope | The present document specifies requirements for qualified and non-qualified certificates for electronic seals/signatures for wallet-relying party access certificates to be used by wallet-relying parties aiming to meet the needs of eIDAS2 [i.2] and implementing acts, especially CIR (EU) 2025/848 [i.6] on the access certificates for wallet-relying parties. The present document imposes no requirements on the functioning of Competent Authorities registering and overseeing the operation of wallet-relying parties. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 2 References | |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI EN 319 412-1: "Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 1: Overview and common data structures". [2] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions; Part 1: Country codes". [3] ETSI EN 319 411-1: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 1: General requirements". [4] ETSI EN 319 411-2: "Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 2: Requirements for trust service providers issuing EU qualified certificates". [5] ETSI TS 119 475: "Electronic Signatures and Trust Infrastructures (ESI); Relying party attributes supporting EUDI Wallet user's authorization decisions". |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 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 may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. [i.2] Regulation (EU) 2024/1183 of the European Parliament and of the Council of 11 April 2024 amending Regulation (EU) No 910/2014 as regards establishing the European Digital Identity Framework. ETSI ETSI TS 119 411-8 V1.1.1 (2025-10) 8 [i.3] Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive) (Text with EEA relevance). [i.4] IETF RFC 3647: "Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework". [i.5] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". [i.6] CIR (EU) 2025/848: "Commission Implementing Regulation (EU) 2025/848 of 6 May 2025 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the registration of wallet-relying parties". [i.7] IETF RFC 9162: "Certificate Transparency Version 2.0". [i.8] Recommendation ITU-T X.520: "Information technology - Open Systems Interconnection - The Directory: Selected attribute types". 3 Definition of terms, symbols, abbreviations and notations |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 3.1 Terms | For the purposes of the present document, the terms given in European Digital Identity Framework [i.2], ETSI EN 319 412-1 [1], ETSI EN 319 411-1 [3], ETSI EN 319 411-2 [4] and the following apply: competent authority: authority recognized under the applicable regulations as competent for the national registration policies relating to European Digital Identity wallet-relying parties European digital identity wallet: electronic identification means which allows the user to securely store, manage and validate person identification data and electronic attestations of attributes for the purpose of providing them to relying parties and other users of European Digital Identity Wallets, and to sign by means of qualified electronic signatures or to seal by means of qualified electronic seals NOTE: As defined in European Digital Identity Framework regulation [i.2]. national register of wallet-relying parties: national electronic register used by a Member State to make information on wallet-relying parties registered in that Member State publicly available NOTE: As set out in Article 5b(5) of Regulation (EU) No 910/2014 [i.1]. provider of wallet-relying party access certificates: natural or legal person mandated by a Member State to issue wallet-relying party access certificates to wallet-relying parties registered in that Member State NOTE 1: As defined in CIR (EU) 2025/848 [i.6]. NOTE 2: In the context of the present document, a provider of wallet-relying party access certificates is a trust service provider. registrar of wallet-relying parties: body responsible for establishing and maintaining the list of registered wallet- relying parties established in their territory and who has been designated by a Member State NOTE: As defined in CIR (EU) 2025/848 [i.6]. wallet-relying party: relying party that intends to rely upon wallet units for the provision of public or private services by means of digital interaction NOTE: As defined in CIR (EU) 2025/848 [i.6]. ETSI ETSI TS 119 411-8 V1.1.1 (2025-10) 9 wallet-relying party access certificate: certificate for electronic seals or signatures authenticating and validating the wallet-relying party issued by a provider of wallet-relying party access certificates NOTE: As defined in CIR (EU) 2025/848 [i.6]. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 3.2 Symbols | Void. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: CRL Certificate Revocation List eIDAS electronic IDentification, Authentication and trust Services NOTE: Informal name for Regulation (EU) No 910/2014 [i.1]. eIDAS2 Regulation (EU) 2024/1183 amending eIDAS EUDIW European Digital Identity Wallet eudiwrp european digital identity wallet relying party OCSP Online Certificate Status Protocol TSP Trust Service Provider NOTE: In the context of the present document trust service provider acting as a provider of wallet-relying party access certificates. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 3.4 Notations | 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 that include several choices which ought to be selected according to the applicable situation. Such requirements are indicated by clauses marked by "[CHOICE]"; c) requirements applicable to the services offered under the applicable certificate policy. Such requirements are indicated by clauses marked by the applicable certificate policy indicator: "[NCP-n-eudiwrp]" or "[NCP-l-eudiwrp]" or "[QCP-n-eudiwrp]" or "[QCP-l-eudiwrp]". 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 • SDP: Subject Device Provisioning • CSS: Certificate Status Service The management of the requirement identifiers throughout subsequent editions of the present document is as follows: ETSI ETSI TS 119 411-8 V1.1.1 (2025-10) 10 • When a requirement is inserted at the end of a clause, the 2 digit number above is incremented to the next available digit. • When a requirement is inserted between two existing requirements, capital letters appended to the previous requirement identifier are used to distinguish new requirements. • The requirement identifier for a deleted requirement is left and completed with "Void". • The requirement identifier for a modified requirement is left void and the modified requirement is identified by capital letter(s) appended to the initial requirement number. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 4 General concepts | |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 4.1 General policy requirements concept | ETSI EN 319 411-1 [3], clause 4.1 applies. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 4.2 Certificate policy and certification practice statement | |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 4.2.1 Certification Practice Statement | The explanations identified in ETSI EN 319 411-1 [3], clause 4.2.1 apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 4.2.2 Certificate Policy | The explanations identified in ETSI EN 319 411-1 [3], clause 4.2.2 apply. OVR-4.2.2-01: Providers of wallet-relying party access certificates conforming to the present document normative requirements may use certificate policy OIDs defined in the present document in its documentation and in the wallet- relying party access certificates it issues. OVR-4.2.2-02: The certificate policy and certificate practice statement applicable to the provision of wallet-relying party access certificates shall comply with at least the Normalised Certificate Policy (NCP) requirements as specified in ETSI EN 319 411-1 [3]. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 4.2.3 Terms and conditions and PKI disclosure statement | The guidelines identified in ETSI EN 319 411-1 [3], clause 4.2.3 apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 4.3 Certification services | The guidelines identified in ETSI EN 319 411-1 [3], clause 4.3 apply. 5 General provisions on Certification Practice Statement and Certificate Policies |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.1 General requirements | OVR-5.1-01: The general requirements specified in ETSI EN 319 411-1 [3], clause 5.1 shall apply. OVR-5.1-02 [QCP-n-eudiwrp]: All policy requirements defined for QCP-n as specified in ETSI EN 319 411-2 [4] shall apply. ETSI ETSI TS 119 411-8 V1.1.1 (2025-10) 11 OVR-5.1-03 [QCP-l-eudiwrp]: All policy requirements defined for QCP-l as specified in ETSI EN 319 411-2 [4] shall apply. OVR-5.1-04 [NCP-n-eudiwrp] [NCP-l-eudiwrp]: All policy requirements relevant to wallet-relying party access certificates issued to legal persons or natural persons defined for NCP shall be applied as specified in ETSI EN 319 411-1 [3]. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.2 Certification Practice Statement Requirements | OVR-5.2-01: The requirements identified in ETSI EN 319 411-1 [3], clause 5.2 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.3 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. The policy identifiers for the ETSI certificate policies described in clause 4.2.2 of the present document are: 1) NCP-n-eudiwrp: Normalized certificate policy for wallet-relying party access certificates issued to natural persons; -- NCP-n-eudiwrp: certificate policy for certificates for electronic signature -- issued to EUDIW wallet-relying parties in accordance with the revised eIDAS Regulation; ncp-n-eudiwrp OBJECT IDENTIFIER ::= { itu-t(0) identified-organization(4) etsi(0) eudiwrp(194118) policy-identifiers(1) ncp-natural (1)} 2) NCP-l-eudiwrp: Normalized certificate policy for wallet-relying party access certificates issued to legal persons; -- NCP-l-eudiwrp: certificate policy for certificates for electronic seal -- issued to EUDIW wallet-relying parties in accordance with the revised eIDAS Regulation; ncp-l-eudiwrp OBJECT IDENTIFIER ::= { itu-t(0) identified-organization(4) etsi(0) eudiwrp(194118) policy-identifiers(1) ncp-legal (2)} 3) QCP-n-eudiwrp: Qualified certificate policy for wallet-relying party access certificates issued to natural persons; -- QCP-n-eudiwrp: certificate policy for qualified certificates for electronic signature -- issued to EUDIW wallet-relying parties in accordance with the revised eIDAS Regulation; qcp-n-eudiwrp OBJECT IDENTIFIER ::= { itu-t(0) identified-organization(4) etsi(0) eudiwrp(194118) policy-identifiers(1) qcp-natural (3)} 4) QCP-l-eudiwrp: Qualified certificate policy for wallet-relying party access certificates issued to legal persons; -- QCP-l-eudiwrp: certificate policy for qualified certificates for electronic seal -- issued to EUDIW wallet-relying parties in accordance with the revised eIDAS Regulation; qcp-l-eudiwrp OBJECT IDENTIFIER ::= { itu-t(0) identified-organization(4) etsi(0) eudiwrp(194118) policy-identifiers(1) qcp-legal (4)} |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.4 PKI Participants | |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.4.1 Certification authority | OVR-5.4.1-01: The requirements identified in ETSI EN 319 411-1 [3], clause 5.4.1 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.4.2 Subscriber and subject | OVR-5.4.2-01: The requirements identified in ETSI EN 319 411-1 [3], clause 5.4.2 shall apply. ETSI ETSI TS 119 411-8 V1.1.1 (2025-10) 12 |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.4.3 Others | OVR-5.4.3-01: The requirements identified in ETSI EN 319 411-1 [3], clause 5.4.3 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.5 Certificate Usage | |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.5.1 NCP-n-eudiwrp | Wallet-relying party access certificates issued under this policy identifier are based on NCP and aimed to support the advanced electronic signatures such as defined in article 3 (12) of the Regulation (EU) No 910/2014 [i.1]. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.5.2 NCP-l-eudiwrp | Wallet-relying party access certificates issued under this policy identifier are based on NCP and aimed to support advanced electronic seals such as defined in article 3 (27) of the Regulation (EU) No 910/2014 [i.1]. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.5.3 QCP-n-eudiwrp | Wallet-relying party access certificates issued under this policy identifier are based on QCP-n and aimed to support the advanced electronic signatures based on a qualified certificate defined in articles 26 and 28 of the Regulation (EU) No 910/2014 [i.1]. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 5.5.4 QCP-l-eudiwrp | Wallet-relying party access certificates issued under this policy identifier are based on QCP-l and aimed to support the advanced electronic seals based on a qualified certificate defined in articles 36 and 38 of the Regulation (EU) No 910/2014 [i.1]. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6 Trust Service Providers practice | |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.1 Publication and Repository Responsibilities | OVR-6.1-01: The requirements specified in ETSI EN 319 411-1 [3], clause 6.1 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.2 Identification and Authentication | |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.2.1 Naming | REG-6.2.1-01: The requirements identified in ETSI EN 319 411-2 [4], clause 6.2.1 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.2.2 Initial Identity Validation | REG-6.2.2-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.2.2 or practices which are confirmed to provide equivalent assurance shall apply. NOTE: Registrar of wallet-relying parties may provide written confirmation to the TSP that it validates the identity with equivalence assurance to that provided by ETSI EN 319 411-1 [3], clause 6.2.2. REG-6.2.2-02 [QCP-n-eudiwrp] [QCP-l-eudiwrp]: The requirements identified in ETSI EN 319 411-2 [4], clause 6.2.2 shall apply. In addition, the following shall apply: ETSI ETSI TS 119 411-8 V1.1.1 (2025-10) 13 • REG-6.2.2-03: The provider of wallet-relying party access certificates shall verify that the wallet-relying party is included, with a valid registration status, in a national register of wallet-relying parties of the Member State in which that wallet-relying party is established. • REG-6.2.2-04: If the Competent Authority/Member State in which the wallet-relying party is established provides additional rules for validation of these wallet-relying party access certificates, the provider of wallet-relying party access certificates shall apply the given rules. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.2.3 Identification and authentication for Re-key requests | REG-6.2.3-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.2.3 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.2.4 Identification and authentication for revocation requests | REV-6.2.4-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.2.4 shall apply. In addition, the following shall apply: • REV-6.2.4-02: The provider of wallet-relying party access certificates shall provide a procedure for submission of wallet-relying party access certificate revocation requests by competent supervisory bodies or data protection authorities in its certificate policy or practice statement. • REV-6.2.4-03: In addition, the provider of wallet-relying party access certificates shall provide a communication method, for notifications from the competent supervisory bodies about changes of relevant regulatory information of the wallet-relying party which can affect the validity of the wallet-relying party access certificate. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3 Certificate Life-Cycle Operational Requirements | |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.1 Certificate Application | NOTE: See also clause 6.2.2 regarding identity validation. REG-6.3.1-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.3.1 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.2 Certificate application processing | REG-6.3.2-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.3.2 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.3 Certificate issuance | GEN-6.3.3-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.3.3 shall apply. GEN-6.3.3-02 [QCP-n-eudiwrp] [QCP-l-eudiwrp]: The requirements identified in ETSI EN 319 411-2 [4], clause 6.3.3 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.4 Certificate acceptance | OVR-6.3.4-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.3.4 shall apply. OVR-6.3.4-02 [QCP-n-eudiwrp] [QCP-l-eudiwrp]: The requirements identified in ETSI EN 319 411-2 [4], clause 6.3.4 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.5 Key Pair and Certificate Usage | OVR-6.3.5-01: The general obligations specified in ETSI EN 319 411-1 [3], clause 6.3.5 shall apply. OVR-6.3.5-02 [QCP-n-eudiwrp] [QCP-l-eudiwrp]: The requirements identified in ETSI EN 319 411-2 [4], clause 6.3.5 shall apply. ETSI ETSI TS 119 411-8 V1.1.1 (2025-10) 14 |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.6 Certificate Renewal | REG-6.3.6-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.3.6 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.7 Certificate Re-key | REG-6.3.7-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.3.7 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.8 Certificate Modification | REG-6.3.8-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.3.8 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.9 Certificate Revocation and Suspension | REV-6.3.9-01: The requirements specified in ETSI EN 319 411-1 [3], clause 6.3.9 shall apply. In addition, the following shall apply: REV-6.3.9-02: The provider of wallet-relying party access certificates shall implement measures and processes to continuously monitor any changes in the national register for wallet-relying parties in which wallet-relying parties to whom they have issued wallet-relying party access certificates are registered. REV-6.3.9-03: The provider of wallet-relying party access certificates shall have a process and an agreement with the registrar to be informed by the registrar when the registration of the wallet-relying party is suspended or cancelled. REV-6.3.9-04: The provider of wallet-relying party access certificates shall revoke any wallet-relying party access certificate when the registration of the wallet-relying party is suspended or cancelled. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.10 Certificate Status Services | CSS-6.3.10-01: The requirements specified in ETSI EN 319 411-1 [3], clause 6.3.10 shall apply. CSS-6.3.10-02 [QCP-n-eudiwrp] [QCP-l-eudiwrp]: The requirements specified in ETSI EN 319 411-2 [4], clause 6.3.10 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.11 End of Subscription | No policy requirement. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.3.12 Key Escrow and Recovery | SDP-6.3.12-01: The requirements specified in ETSI EN 319 411-1 [3], clause 6.3.12 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.4 Facility, Management and Operational Controls | |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.4.1 General | OVR-6.4.1-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.4.1 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.4.2 Physical Security Controls | OVR-6.4.2-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.4.2 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.4.3 Procedural Controls | OVR-6.4.3-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.4.3 shall apply. ETSI ETSI TS 119 411-8 V1.1.1 (2025-10) 15 |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.4.4 Personnel Controls | OVR-6.4.4-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.4.4 shall apply. |
c283b321481640a37e74db6d6840f337 | 119 411-8 | 6.4.5 Audit Logging Procedures | OVR-6.4.5-01: The requirements identified in ETSI EN 319 411-1 [3], clause 6.4.5 shall apply. In addition, the following shall apply: OVR-6.4.5-02: The provider of wallet-relying party access certificates shall provide, where relevant, a description on how those wallet-relying party access certificates have been logged which should be in compliance with IETF RFC 9162 [i.7]. NOTE: ETSI is working on a Technical Specification requirements for certificate transparency. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.