Artifact GuideGLOBALETSI EN 319 411-2

ETSI EN 319 411-2 QTSP supervision evidence for qualified certificate services

ETSI EN 319 411-2 gives certificate-policy and security requirements for EU qualified certificate services, but it does not by itself make a provider or certificate qualified.

This FAQ helps separate standards conformance evidence from trusted-list status, independent assessment, and supervisory records.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

Use ETSI EN 319 411-2 as an evidence framework for a 's EU qualified certificate service, not as the supervision decision. Under eIDAS, qualified status follows conformity assessment, supervisory verification, and entry of the provider and service in the national . The supervision file should connect that legal status to the selected certificate policy and the operating evidence.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

Does ETSI EN 319 411-2 make a TSP qualified?

No. ETSI EN 319 411-2 expressly warns that conformance to the standard alone does not mean that the TSP or its certificates are qualified. A supervision answer should therefore avoid treating an EN 319 411-2 audit result as a substitute for qualified status.

For a issuing EU qualified certificates, the standard is still central evidence. It incorporates EN 319 411-1 general policy and security requirements, then adds requirements for EU qualified certificates for signatures, seals, and website authentication.

Current eIDAS Article 20 requires an audit by a at the 's expense at least every 24 months. The QTSP must notify the supervisory body at least one month before a planned audit and submit the resulting report within three working days after receiving it. The supervisory body may also audit the QTSP or request another assessment at any time. Article 21 governs the supervisory decision for a new qualified service; the service may begin only after qualified status appears in the . Commission Implementing Regulation (EU) 2025/2162 supplies the current accreditation, assessment-scheme, and report rules.

  • Keep the qualified-status decision separate from EN 319 411-2 conformance evidence.
  • Identify the exact qualified certificate policy in scope, such as QCP-n, QCP-l, QCP-n-qscd, QCP-l-qscd, QEVCP-w, QNCP-w, or QNCP-w-gen.
  • Show how EN 319 411-2 adds EU qualified certificate requirements on top of the EN 319 411-1 certificate policy baseline.
  • Calendar the recurring assessment from the last applicable assessment, the one-month pre-audit notice, and the three-working-day report submission; retain proof for each date rather than recording only the final report.
Question 2

What should a QTSP supervision file contain?

A useful supervision file should start with the certificate service and policy identifier, then link the certification practice statement (CPS), certificate profile, repository, identity proofing, revocation, status service, incident, and termination evidence to the relevant EN 319 411-2 and incorporated EN 319 411-1 requirements.

The record should also prove the relying-party path. EN 319 411-2 says relying-party notices for EU qualified certificates need to explain that the trust anchor is identified in the service digital identifier of an appropriate EU trusted-list entry for the . Record the provider, the specific qualified service, its status and status history, and the certificates or other service identifiers carried by that entry. Keep subcontracted operations in the same map: the QTSP identified in the retains overall responsibility for issuing the certificates even when another party performs a component activity.

  • Preserve the selected policy identifier and the certificate profile evidence used to signal that policy.
  • Attach CPS sections for issuance, maintenance, revocation, status services, records, and service termination.
  • Keep the trusted-list service digital identifier and the trust anchor it identifies as separate evidence fields.
  • Track supervisory findings through owner, remedy, due date, evidence of completion, and closure; a standards cross-reference does not prove that an operational deficiency was corrected.
Question 3

What are the most common supervision mistakes?

The most common mistakes are to blur qualified-status evidence with standards conformance, omit the trusted-list reliance path, or leave the supervision file without a traceable link from the selected certificate policy to the operational records.

Another common problem is treating incident, revocation, and records-retention evidence as optional. EN 319 411-2 and EN 319 411-1 map those topics into the qualified-certificate supervision file, while eIDAS Article 46b gives the supervisory body powers to request conformity assessments, grant or withdraw qualified status, require remediation, and verify termination plans.

  • Do not claim qualified status from EN 319 411-2 conformance alone.
  • Do not omit the trusted-list service digital identifier or the notice to relying parties.
  • Do not leave revocation, incident, and records-retention evidence outside the supervision pack.
Question 4

Questions and answers

Does ETSI EN 319 411-2 make a TSP qualified?

No. ETSI EN 319 411-2 says that conformance to the standard alone does not mean that the TSP or its certificates are qualified under Regulation (EU) No 910/2014. It remains relevant evidence, but the supervisory decision and trusted-list entry establish qualified status.

What should a supervision file contain?

The record should link the selected policy identifier to the CPS, certificate profile, identity proofing, trusted-list service and status history, revocation and status-service evidence, incident records, conformity assessment reports, remediation, and termination or records-retention controls.

What is the most common supervision mistake?

A common mistake is treating EN 319 411-2 conformance as proof of qualified status and leaving out the trusted-list notice, operational records, or lifecycle evidence that supports the claim.

How often must a undergo conformity assessment?

Under current eIDAS Article 20, a must be audited at its own expense by a at least every 24 months. It must notify the supervisory body at least one month before a planned audit and send the assessment report within three working days after receiving it. The supervisory body can also audit or request an assessment at any time, so the 24-month cycle is a minimum recurring control, not a shield from additional review.

What happens when supervision finds non-compliance?

The supervisory body can require remediation, carry out or request further assessment, and grant or withdraw qualified status. The should preserve the finding, affected service and policy scope, remediation owner and deadline, implementation evidence, reassessment result, and any trusted-list status change. EN 319 411-2 mapping helps organize that file but does not decide the legal outcome.

Primary sources

References and citations

etsi.org4 citations
Referenced sections
  • Provides the incorporated certificate policy and security baseline for CPS, publication, repository, identity validation, revocation, status service, records, and lifecycle evidence.
  • Provides the incorporated baseline for certificate policy, CPS, repository, revocation, subscriber identity, and lifecycle controls.
  • Provides the underlying certificate lifecycle and CPS controls that the QTSP supervision file should map to the qualified certificate service.
Show 1 more
  • Provides the incorporated baseline controls for certificate lifecycle operations, revocation, records, publication, and repository responsibilities.
"Trust Service Providers issuing certificates"
More quoted passages
"Certification Practice Statement"
"Certificate Life-Cycle Operational Requirements"
etsi.org4 citations
Referenced sections
  • Defines the EU qualified certificate policy requirements, warns that standards conformance alone does not create qualified status, and maps QTSP lifecycle evidence to trusted-list, incident, revocation, recordkeeping, and termination topics.
  • Supports the distinction between EN 319 411-2 conformance and legal qualified status, and defines the EU qualified certificate policy scope.
  • Supports policy identifier evidence, relying-party notice requirements, and the EU trusted-list trust-anchor path for QTSP certificates.
Show 1 more
  • Supports the liability-responsibility point for the qualified TSP identified in the trusted list and the mapped controls for incidents, records, termination, revocation, and certificate status services.
"does not imply"
More quoted passages
"EU trusted list entry"
"maintains overall responsibility"
eur-lex.europa.eu2 citations
Referenced sections
  • Current implementing rules for conformity-assessment body accreditation, assessment schemes, certificates of conformity, and conformity assessment reports.
  • Sets the accreditation, conformity-assessment scheme, and report requirements used for QTSP and qualified-service assessments.
eur-lex.europa.eu2 citations
Referenced sections
  • Articles 20, 21, 22, and 46b govern conformity assessment, grant and withdrawal of qualified status, trusted-list publication, supervisory powers, remediation, and termination-plan review.
  • Articles 20 and 21 set the recurring conformity-assessment, audit-notice, report-submission, supervisory verification, and trusted-list entry steps for qualified status.
Show all related guides (24)

What are the qualified certificate policies in ETSI EN 319 411-2?

FAQ on ETSI EN 319 411-2 qualified certificate policies, including QCP-n, QCP-l, QSCD variants, QEVCP-w, QNCP-w, and policy identifiers.

Which QWAC Profile Fits ETSI EN 319 411-2?

Choose between QEVCP-w, QNCP-w, and QNCP-w-gen for qualified website authentication certificates under ETSI EN 319 411-2.

eIDAS QTSP supervision workflow for ETSI EN 319 411-2

Operational workflow for qualified trust service providers using ETSI EN 319 411-2 to manage supervisory-body changes, incidents, termination evidence, trusted-list checks, and assessment records.

ETSI EN 319 411-2 certificate operations

Operational guide for ETSI EN 319 411-2 qualified certificate services: policy identifiers, identity validation, issuance, QSCD handling, revocation status, and relying-party notices.

ETSI EN 319 411-2 compliance checklist

Compliance checklist for ETSI EN 319 411-2 qualified certificate services, covering policy selection, CP/CPS evidence, identity validation, QSCD status, trusted-list reliance, and certificate status services.

ETSI EN 319 411-2 FAQ for EU Qualified Certificates

Answers to common ETSI EN 319 411-2 questions about EU qualified certificate policies, QSCD use, identity validation, trusted lists, and revocation status services.

ETSI EN 319 411-2 Identity Proofing

How EN 319 411-2 applies identity validation for EU qualified certificates, including QCP natural-person, legal-person, website, and evidence-record checks.

ETSI EN 319 411-2 profile selector

Select the right ETSI EN 319 411-2 qualified certificate policy profile for signatures, seals, QSCD use, and website authentication.

ETSI EN 319 411-2 QSCD Route

When QCP-n-qscd or QCP-l-qscd is the right EN 319 411-2 route, what QSCD evidence is needed, and which certificate-profile claims must stay aligned.

ETSI EN 319 411-2 QTSP supervision evidence workflow

Build an assessment-ready QTSP supervision evidence pack for ETSI EN 319 411-2 qualified certificate services, covering policy identifiers, trusted-list checks, incident records, QSCD evidence, and termination controls.

ETSI EN 319 411-2 Qualified Certificate Scope

Use ETSI EN 319 411-2 to scope EU qualified certificate services by certificate policy, subject type, QSCD use, website authentication profile, and eIDAS context.

ETSI EN 319 411-2 requirements map

Map ETSI EN 319 411-2 requirements for EU qualified certificate services across QCP profiles, CP/CPS documentation, QSCD use, certificate profiles, revocation, and eIDAS Annex A references.

ETSI EN 319 411-2 trusted-list evidence

Build EN 319 411-2 trusted-list evidence for EU qualified certificate reliance: relying-party notice text, QTSP service identifiers, validation records, and change triggers.

ETSI EN 319 411-2 trusted-list validation workflow

Validate an EN 319 411-2 EU qualified-certificate claim by mapping the certificate service to the QTSP trusted-list entry, policy profile, relying-party notice, and status evidence.

ETSI EN 319 411-2 vs eIDAS Qualified Trust Services

Compare ETSI EN 319 411-2 certificate policy requirements with the eIDAS qualified-status, supervision, audit, and trusted-list framework.

ETSI EN 319 411-2 vs EN 319 411-1

Compare ETSI EN 319 411-2 EU qualified certificate requirements with EN 319 411-1 general certificate-service requirements, including policy inheritance, QSCD controls, and CP/CPS evidence reuse.

ETSI EN 319 411-2: end-to-end qualified certificate lifecycle management workflow

Lifecycle workflow for ETSI EN 319 411-2 qualified certificate services, from policy selection and identity validation through issuance, renewal, re-key, modification, revocation, status services, and records.

ETSI EN 319 411-2: QCP, QNCP, and QEVCP Profile Selection

Choose the right ETSI EN 319 411-2 qualified certificate policy profile: QCP-n, QCP-l, QCP-n-qscd, QCP-l-qscd, QEVCP-w, QNCP-w, or QNCP-w-gen.