Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 5: QCStatements

Note

ETSI standard, part 5, defining specific QCStatements for the qcStatements extension of RFC 3739, with the requirements for their use in EU qualified certificates (version 2.5.1).

Summary

Purpose

European standard ETSI EN 319 412-5 (version 2.5.1, June 2025) defines the QCStatements placed in the qcStatements extension of a certificate (RFC 3739), and the rules for their use in EU qualified certificates ETSI EN 319 412-5 V2.5.1, § 1 Scope ETSI EN 319 412-5 V2.5.1, History RFC 3739. Its scope begins as follows:

These statements can supplement any certificate profile, in particular those of ETSI EN 319 412-2, 412-3 and 412-4 ETSI EN 319 412-5 V2.5.1, § 1 Scope.

Who it applies to

• To qualified trust service providers that issue qualified certificates for signatures, seals or website authentication ETSI EN 319 412-5 V2.5.1, § 5 Requirements on QCStatements in EU qualified certificates; for signatures and seals, through Implementing Regulation 2025/1943 Art. 1.
• To providers of PuB-EAA (electronic attestations of attributes issued by or on behalf of a public body responsible for an authentic source): their attestations issued to wallets comply with at least one of the standards of Annex II to Implementing Regulation 2024/2979, which addresses the qualified certificate supporting their signature Art. 4(1) Annex II.

Key points

• EU qualified certificate: the esi4-qcStatement-1 statement claims that the certificate is qualified; it is mandatory, and the statement designating the country or countries under whose legislation a certificate is qualified is then prohibited ETSI EN 319 412-5 V2.5.1, § 4.2.1 QCStatement claiming that the certificate is a EU qualified certificate or a certificate being qualified within a defined legal framework from an identified country or set of countries ETSI EN 319 412-5 V2.5.1, § 5 Requirements on QCStatements in EU qualified certificates.
• Certificate type: a statement indicates whether it is issued for signatures, seals or website authentication; it is mandatory for certificates for seals and websites ETSI EN 319 412-5 V2.5.1, § 4.2.3 QCStatement claiming that the certificate is a certificate of a particular type ETSI EN 319 412-5 V2.5.1, § 5 Requirements on QCStatements in EU qualified certificates.
• Key in a qualified device (QSCD): a statement indicates it; it must be present when the private key resides in such a device ETSI EN 319 412-5 V2.5.1, § 4.2.2 QCStatement claiming that the private key related to the certified public key resides in a QSCD ETSI EN 319 412-5 V2.5.1, § 5 Requirements on QCStatements in EU qualified certificates.
• Identification method: a qualified provider may indicate the identity verification method it used among those provided for by Regulation 910/2014 for the issuance of qualified certificates ETSI EN 319 412-5 V2.5.1, § 4.3.5.1 General requirements Art. 24(1a).
• PKI Disclosure Statement (PDS): optional, it gives at least one address pointing to an English version ETSI EN 319 412-5 V2.5.1, § 5 Requirements on QCStatements in EU qualified certificates.

What the acts apply, and how

• Implementing Regulation 2025/1943: EN 319 412-5 version 2.5.1 is among the standards that Annexes I (signature) and II (seal) make applicable; no specific adaptation targets it, but it replaces normative references of EN 319 411-2 version 2.6.1 and EN 319 412-2 version 2.4.1 as adapted Annex I Annex II. EN 319 411-2 requires the certificate to contain all the appropriate statements of EN 319 412-5 ETSI EN 319 411-2 V2.6.1, § 6.6.1 Certificate Profile. A qualified certificate that complies with these standards, specifications and procedures is presumed to comply with the requirements of Annex I or III to the regulation Art. 28(6) Art. 38(6).
• Implementing Regulation 2024/2979: Annex II makes clauses 2 to 6 of ETSI TS 119 472-1 applicable with adaptations; one of them requires the qualified certificate supporting the signature of a PuB-EAA to contain the QcType statement of EN 319 412-5 version 2.5.1, with a new value, id-etsi-qct-eidaspsbeaa Annex II ETSI TS 119 472-1 V1.2.1. Wallet providers support attestations issued in accordance with that annex Art. 8. The current Annex II comes from Implementing Regulation 2026/1731 List of standards referred to in Article 8.
• Implementing Decision 2015/1505 (trusted lists): each list refers to a descriptive text common to all lists; among the default rules for interpreting the qualified status of a certificate, that text relies on the presence of the QCStatements of EN 319 412-5, cited without a version, with requirements on their content Annex I. The section containing that text was replaced by Implementing Decision 2025/2164, applicable from 29 April 2026 Annex Art. 2.
• Implementing Regulation 2025/2162: Annex II cites EN 319 412-5, without a version, for the three services issuing qualified certificates Annex II.

Important clauses

• ETSI EN 319 412-5 V2.5.1, § 1 Scope: scope.
• ETSI EN 319 412-5 V2.5.1, § 4.2 QCStatements claiming compliance with specific legislation: statements linked to a legislation.
• ETSI EN 319 412-5 V2.5.1, § 5 Requirements on QCStatements in EU qualified certificates: table of mandatory, optional and prohibited statements.
• ETSI EN 319 412-5 V2.5.1, Annex B (normative): ASN.1 declarations: ASN.1 module.

Links

• Profiles that use it: ETSI EN 319 412-2 ETSI EN 319 412-2 V2.4.1, 412-3 ETSI EN 319 412-3 V1.3.1, 412-4 ETSI EN 319 412-4 V1.4.1.
• Learning path: step 4, trust services.

ETSI standard: the site reproduces only short extracts; the full text is available from ETSI ETSI EN 319 412-5 V2.5.1. Written by Asphalia.