Artifact GuideGLOBALETSI EN 319 411-2

ETSI EN 319 411-2 vs eIDAS qualified trust services

A comparison of the ETSI certificate-policy standard used for EU qualified certificates and the eIDAS legal framework that grants and supervises qualified trust-service status.

Use this to separate standard conformance evidence from qualified-status, trusted-list, and supervisory evidence.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
6

Structured answer sets in this page tree.

Primary sources
12

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

ETSI EN 319 411-2 and eIDAS are related, but they do different jobs. EN 319 411-2 specifies policy and security requirements for trust service providers issuing EU qualified certificates. eIDAS defines qualified trust services, qualified trust service providers, supervisory bodies, conformity assessment, and trusted lists. Meeting the ETSI standard can support a qualified-certificate evidence file; it does not, by itself, grant qualified status.

Side-by-side comparison

ETSI EN 319 411-2 vs eIDAS qualified trust services: what changes?

Use this comparison to keep certificate-policy conformance separate from the legal qualified-status and trusted-list checks required under eIDAS.

Review all sources
First framework
ETSI EN 319 411-2

A European standard for policy and security requirements for TSPs issuing EU qualified certificates.

Second framework
eIDAS qualified trust services

The EU legal framework for qualified trust services, qualified trust service providers, supervision, conformity assessment, and trusted lists.

Comparison row 1

Scope and covered activity

ETSI EN 319 411-2

EN 319 411-2 covers policy and security requirements for TSPs issuing EU qualified certificates, including named qualified certificate policy profiles.

eIDAS qualified trust services

eIDAS covers qualified trust services as a legal category, including qualified certificates for signatures, seals, and website authentication plus the provider status framework around them.

Operational implication

Start by naming both the certificate policy profile and the eIDAS service status being claimed; the standard scope and the legal qualified-service scope are related but not identical.

Comparison row 2

Who must act

ETSI EN 319 411-2

The EN 319 411-2 owner is the certificate-issuing TSP and its CA, RA, repository, revocation, certificate status, CP/CPS, and security-control owners.

eIDAS qualified trust services

The eIDAS owners include the trust service provider seeking or holding qualified status, the conformity assessment body, the supervisory body, and the Member State trusted-list function.

Operational implication

Assign standard evidence to certificate-service operators and legal status evidence to the qualified-service governance team; one generic compliance owner will miss handoffs.

Comparison row 3

Trigger or threshold

ETSI EN 319 411-2

EN 319 411-2 is triggered when a TSP issues, or claims conformance for issuing, EU qualified certificates under one of the standard's qualified certificate policy profiles.

eIDAS qualified trust services

eIDAS qualified-service work is triggered when a provider intends to provide a qualified trust service or needs to maintain qualified status after it has been granted.

Operational implication

Do not wait until public launch copy is drafted; trigger both reviews when the certificate profile and the intended qualified-service status are selected.

Comparison row 4

Core obligations

ETSI EN 319 411-2

EN 319 411-2 obligations are implemented through certificate policy selection, CP/CPS controls, identity validation, issuance, acceptance, revocation, suspension, certificate status, repository, and QSCD-related evidence where applicable.

eIDAS qualified trust services

eIDAS obligations include notification, conformity assessment, supervisory verification, ongoing audits, remedy where required, status withdrawal risk, and trusted-list publication.

Operational implication

Build two linked workstreams: one for certificate-service controls and one for qualified-status lifecycle controls.

Comparison row 5

Evidence and records

ETSI EN 319 411-2

EN 319 411-2 evidence is the CP/CPS, certificate policy identifier, subscriber and subject validation, certificate issuance, revocation, suspension, certificate status, repository, QSCD indication, and records material.

eIDAS qualified trust services

eIDAS evidence is the conformity assessment report, notification to the supervisory body, supervisory verification, qualified-status grant, and trusted-list entry.

Operational implication

Keep a traceable matrix with separate columns for standard conformance artifacts and legal qualified-status artifacts.

Comparison row 6

Timing and cadence

ETSI EN 319 411-2

EN 319 411-2 timing is driven by certificate lifecycle events such as application, issuance, acceptance, renewal, re-key, modification, revocation, suspension, status service operation, and records archival.

eIDAS qualified trust services

eIDAS timing includes the Article 20 audit cadence of at least every 24 months, submission of the conformity assessment report, supervisory verification, and trusted-list update timing.

Operational implication

Track certificate lifecycle clocks separately from qualified-status audit and supervisory clocks.

Comparison row 7

Enforcement or assurance route

ETSI EN 319 411-2

EN 319 411-2 is enforced through assessment, audit expectations, certification or procurement requirements, and the ability to prove the certificate service matches the selected policy profile.

eIDAS qualified trust services

eIDAS supervision is performed by supervisory bodies that can audit, require remedy, and withdraw qualified status where the Regulation's requirements are not met.

Operational implication

Escalate when an EN 319 411-2 finding affects status evidence, because a technical nonconformity can become a supervisory issue under eIDAS.

Comparison row 8

Overlap and reuse

ETSI EN 319 411-2

Reuse EN 319 411-2 controls where the same certificate service, policy profile, CP/CPS, CA/RA process, revocation service, and records boundary are unchanged.

eIDAS qualified trust services

Reuse eIDAS qualified-service evidence only where the same provider, service, Member State supervision, qualified-status decision, and trusted-list entry are in scope.

Operational implication

A shared control can reduce duplication, but status evidence, certificate-profile evidence, and trusted-list evidence must remain traceable to the exact source that supports the claim.

Comparison row 9

Practical decision rule

ETSI EN 319 411-2

Use EN 319 411-2 when the question is whether certificate-policy, CP/CPS, lifecycle, QSCD, QWAC, or CA/RA evidence meets the qualified-certificate standard.

eIDAS qualified trust services

Use eIDAS when the question is whether the provider and service have qualified status, supervisory verification, conformity assessment evidence, and a trusted-list entry.

Operational implication

Use both only when the same qualified certificate service needs standard-conformance evidence and eIDAS qualified-status evidence.

Practical decision rule

How to choose the controlling source

  • Use EN 319 411-2 when the decision is about certificate policy, CP/CPS, certificate lifecycle operations, QSCD indication, or qualified certificate profile evidence.
  • Use eIDAS when the decision is about qualified status, supervisory verification, conformity assessment reports, trusted-list publication, or legal qualified-service wording.
  • Use both only when a specific qualified certificate service needs both standard-conformance evidence and eIDAS qualified-status evidence.
Section 1

What each source controls

Use EN 319 411-2 when the question is whether a certificate-issuing trust service provider has implemented the policy and security requirements for EU qualified certificates. The standard names the certificate policy families and points back to EN 319 411-1 for general CA, registration, repository, revocation, and certificate lifecycle requirements.

Use eIDAS when the question is whether a trust service is legally qualified in the EU. eIDAS defines a qualified trust service as one meeting the Regulation's applicable requirements and defines a qualified trust service provider as one granted qualified status by the supervisory body.

  • EN 319 411-2 is evidence for certificate policy and CA operations; it is not the legal act that grants qualified status.
  • eIDAS controls supervisory verification, qualified-status grant or withdrawal, trusted-list publication, and qualified-service legal effects.
  • A procurement claim such as "eIDAS qualified" should be checked against the trusted list and supervisory status, not only against an EN 319 411-2 audit statement.
Section 2

Certificate policy evidence vs qualified-status evidence

EN 319 411-2 evidence should show which qualified certificate policy is being used, how the certification practice statement and certificate policy implement the requirement, and how lifecycle controls such as identity validation, issuance, revocation, suspension, certificate status services, and repository publication are operated.

eIDAS evidence should show the supervisory path: notification to the supervisory body, a conformity assessment report, supervisory verification, grant of qualified status, and the trusted-list entry that indicates the provider and service are qualified.

  • Keep CP/CPS, registration, identity proofing, certificate profile, QSCD indication, revocation, and certificate status evidence in the EN 319 411-2 file.
  • Keep conformity assessment report, supervisory correspondence, qualified-status decision, and trusted-list verification in the eIDAS qualified-service file.
  • Do not describe a service as qualified until the eIDAS status evidence exists; an ETSI standards audit alone is not enough.
Section 3

Where QCP, QSCD, and QWAC details fit

EN 319 411-2 is the better place to track certificate-policy details such as QCP-n, QCP-l, QCP-n-qscd, QCP-l-qscd, QEVCP-w, QNCP-w, and QNCP-w-gen. These profile choices affect certificate wording, evidence, and technical controls.

eIDAS is the better place to verify whether the certificate is part of a qualified trust service and whether the provider is listed as qualified for that service. eIDAS also supplies Annex requirements for qualified certificates for electronic signatures, electronic seals, and website authentication.

  • For signature or seal certificates, record whether the qualified certificate indicates QSCD use where the selected policy requires it.
  • For website authentication certificates, keep the EN 319 411-2 QEVCP-w or QNCP-w evidence separate from the eIDAS QWAC status and browser-recognition context.
  • Use trusted-list validation to confirm the service status that relying parties should depend on.
Section 4

Audit and supervision are not the same control

An EN 319 411-2 assessment can support conformity evidence, but eIDAS supervision has its own legal mechanics. Qualified trust service providers are audited at least every 24 months by a conformity assessment body and submit the report to the supervisory body.

The supervisory body can also audit, request a conformity assessment, require remedy, and withdraw qualified status where eIDAS conditions are not met. Treat this as a supervised-status lifecycle, not as a one-time certificate-policy checklist.

  • Map EN 319 411-2 findings to the conformity assessment report, but keep the supervisory decision and trusted-list update as separate artifacts.
  • Track the 24-month audit cadence and the report-submission obligation in the eIDAS evidence calendar.
  • Escalate material CP/CPS, certificate-profile, revocation, QSCD, or service-boundary changes because they may affect both the ETSI evidence file and the eIDAS qualified-service status.
Section 5

Implementation checklist

Use this checklist when a product page, RFP answer, audit pack, or relying-party document uses both EN 319 411-2 and eIDAS qualified-service language.

  • Identify the exact certificate service and policy profile: QCP-n, QCP-l, QCP-n-qscd, QCP-l-qscd, QEVCP-w, QNCP-w, or QNCP-w-gen.
  • Map the CP/CPS, identity validation, issuance, revocation, certificate status, repository, and records evidence to EN 319 411-2 and EN 319 411-1 clauses.
  • Verify the eIDAS qualified-status path: conformity assessment report, supervisory body verification, qualified-status grant, and trusted-list entry.
  • Separate public wording: say "aligned with EN 319 411-2" only for standard evidence, and say "qualified trust service" only where eIDAS status and trusted-list evidence support it.
  • Review both files after certificate-profile, QSCD, CA/RA, revocation, repository, supervisory, or trusted-list changes.
Section 6

Common mistakes to avoid

Most mistakes come from collapsing the technical standard and the legal status into one label. Keep the evidence split so a reader can see whether a claim is about certificate-policy conformance, qualified-service status, or both.

  • Do not imply that EN 319 411-2 certification automatically makes the provider or service qualified under eIDAS.
  • Do not cite a CP/CPS or audit report as a substitute for the trusted-list status check.
  • Do not mix non-qualified EN 319 411-1 certificate evidence into a qualified-service claim without a clear bridge to EN 319 411-2 and eIDAS.
  • Do not use QWAC, QSCD, QCP, or QTSP acronyms in public copy unless the evidence file defines the exact profile and status being claimed.
Primary sources

References and citations

etsi.org
Referenced sections
  • Grounds the lifecycle and records controls that should be checked before reusing certificate-service evidence.
"Records archival"
etsi.org
Referenced sections
  • Grounds when EN 319 411-2 controls the certificate-policy side of the decision.
"Certificate Policy"
eur-lex.europa.eu
Referenced sections
  • Grounds that qualified service provision begins after qualified status appears in the trusted lists.
"after the qualified status has been indicated"
eur-lex.europa.eu
Referenced sections
  • Grounds the provider-and-service trusted-list boundary for eIDAS evidence reuse.
"information related to the qualified trust services"
eur-lex.europa.eu
Referenced sections
  • Grounds the legal definition of a qualified trust service provider.
"granted the qualified status by the supervisory body"
eur-lex.europa.eu
Referenced sections
  • Grounds the supervisory body's role in ensuring qualified services meet eIDAS requirements.
"supervise qualified trust service providers"
eur-lex.europa.eu
Referenced sections
  • Grounds the conformity assessment, supervisory verification, qualified-status grant, and trusted-list evidence.
"establish, maintain and publish trusted lists"
eur-lex.europa.eu
Referenced sections
  • Grounds eIDAS requirements for qualified certificates for electronic signatures, electronic seals, and website authentication.
"qualified certificate for website authentication"
Related guides

Explore more topics

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.
EN 319 411-2 vs EN 319 411-1 Qualified Certs
Compare ETSI EN 319 411-2 qualified certificate requirements with EN 319 411-1 general certificate-service requirements, including QCP profiles, QSCD evidence, CP/CPS reuse, and audit boundaries.
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 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 operations: issuance, suspension, and revocation
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 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: Certificate Revocation FAQ
Answer the ETSI EN 319 411-2 revocation question for qualified certificate services: CPS procedures, 24-hour publication, CRL or OCSP status, and evidence to retain.
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: Legal vs Natural Person Certs
ETSI EN 319 411-2 separates qualified certificate policies for natural persons, legal persons, QSCD use, and website authentication subscribers.
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.
ETSI EN 319 411-2: workflow for selecting QCP-n, QCP-l, or QCP-w certificate profile
Select the right ETSI EN 319 411-2 qualified certificate policy profile for signatures, seals, QSCD use, and website authentication.
How should QTSPs select an ETSI EN 319 411-2 qualified certificate profile?
A focused FAQ on choosing QCP-n, QCP-l, QCP-n-qscd, QCP-l-qscd, QEVCP-w, QNCP-w, or QNCP-w-gen under ETSI EN 319 411-2.
How should relying parties use trusted lists under ETSI EN 319 411-2?
FAQ on EN 319 411-2 trusted-list reliance for EU qualified certificates: relying-party notices, QTSP service identifiers, validation evidence, and source references.
QSCD Requirements in ETSI EN 319 411-2
How ETSI EN 319 411-2 treats QSCD-backed qualified certificates, including QCP-n-qscd and QCP-l-qscd policies, key-use controls, QSCD verification, and certificate profile evidence.
QTSP Supervision and ETSI EN 319 411-2
How ETSI EN 319 411-2 supports QTSP supervision evidence for qualified certificate services, trusted-list reliance, liability responsibility, incident records, and audit preparation.
Qualified certificates under ETSI EN 319 411-2
FAQ answer for QTSPs on how ETSI EN 319 411-2 treats EU qualified certificates, policy identifiers, QSCD variants, website certificates, and lifecycle evidence.
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.