By Sorena AIPublished Updated

ETSI EN 319 411-2

ETSI EN 319 411-2

Guide to ETSI EN 319 411-2 V2.6.1, its EU qualified profiles, current eIDAS adaptations, routes, trusted-list status, and certificate lifecycle controls.

Topics
16
FAQs
9
Comparisons
2
Edition
V2.6.1

Understand ETSI EN 319 411-2

ETSI EN 319 411-2 V2.6.1 sets policy and security requirements for trust service providers issuing EU qualified certificates for signatures, seals, and website authentication. It covers policy selection, identity, issuance, qualified signature or seal creation devices (QSCDs), revocation, status services, and relying-party information.

Choose the certificate purpose, subject, and policy profile first. Then apply the general EN 319 411-1 controls, the Part 2 additions, and each binding EU adaptation. Regulation (EU) 2025/1943 references and adapts V2.6.1 for qualified signature and seal certificates; the QWAC reference rules in Regulation (EU) 2025/2527 apply from 6 January 2027. A provider may run both qualified and non-qualified services, and qualified status attaches only to the specific service entered as qualified in a national trusted list.

Use the linked pages to identify the applicable policy, actor, control, and retained evidence. Recheck the mapping after a policy or OID change, CA hierarchy change, identity route change, status change, trusted-list update, significant service change, or new binding EU adaptation.

Quick scan

ETSI EN 319 411-2 requirements

Start with the CP, CPS, certificate usage, publication, identity validation, issuance, acceptance, revocation, and status-service topics. Identify which controls belong to the certification authority (CA), registration authority (RA), subscriber, subject, manager, or status-service operator.

Qualified certificate scope

Use when the question is whether EN 319 411-2, an inherited EN 319 411-1 control, a binding EU adaptation, or trusted-list status drives the decision.

Qualified profile selector workflow

Use when a profile, indication, or qualified website authentication certificate profile must be selected and documented.

Where to start in the EN 319 411-2 guide

  1. 1

    ETSI EN 319 411-2 requirements

    Review the policy rules and current EU adaptations before mapping the (CP), Certification Practice Statement (CPS), certificate policy identifiers, lifecycle controls, and publication duties. The CP states what the service promises; the CPS explains how the provider meets it.

  2. 2

    ETSI EN 319 411-2 qualified certificate scope

    Check whether the service issues to a natural person, legal person, or website-authentication subscriber; whether the private key must reside in a ; and which trusted-list service entry supports the qualified claim.

  3. 3

    ETSI EN 319 411-2 profile selector workflow

    Choose between QCP-n, QCP-l, QCP-n-, QCP-l-qscd, QEVCP-w, QNCP-w, and QNCP-w-gen using the certificate subject, QSCD condition, and website-certificate basis. Record the ETSI policy identifier or the object identifier (OID) tied to the policy actually applied.

Choose the next qualified-certificate decision

New to EN 319 411-2? Start with scope and the policy profile. If the profile is already fixed, jump to identity, , lifecycle, trusted-list, supervision, or comparison guidance without treating standard conformance as qualified status.

Start here: scope, profile, and requirements

Define the certificate purpose and subject, select the matching qualified , and identify both the Part 2 additions and inherited EN 319 411-1 requirements.

Identity, QSCD, and relying-party trust

Connect the selected policy to subscriber and subject proofing, the qualified signature or seal creation device route, certificate statements, and the EU trusted-list information used by relying parties.

Lifecycle operations and assessment evidence

Translate the policy into issuance, acceptance, renewal, re-key, modification, revocation, status-service, archival, termination, and reviewable evidence controls.

Qualification, supervision, and comparisons

Separate the standard from eIDAS qualified status and supervision, understand the EN 319 411-1 dependency, or open the FAQ for a focused implementation question.

Sources

eur-lex.europa.eu
Referenced sections
  • Binding EU source that references EN 319 411-2 V2.6.1 and applies specified adaptations for qualified certificates for electronic signatures and electronic seals.
eur-lex.europa.eu
Referenced sections
  • Binding EU source for qualified website authentication certificate reference standards; it applies from 6 January 2027 and lists the EN 319 411-2 QEVCP-w, QNCP-w, and QNCP-w-gen routes for certificates issued for use in TLS authentication outside the web-browser context.
eur-lex.europa.eu
Referenced sections
  • Current consolidated legal framework for qualified trust services, identity verification, trusted lists, qualified certificates, and qualified signature or seal creation devices.
digital-strategy.ec.europa.eu
Referenced sections
  • Commission explanation that a provider and service are qualified only when the service appears as qualified in a national trusted list.

Next steps

Assess qualified certificate policies

Review qualified certificate policies in Assessment Autopilot. Use Research Copilot to investigate profile selection, treatment, trusted-list context, or lifecycle evidence against cited sources.

  • Start from the EN 319 411 2 topic page that matches the , CPS, , QWAC, revocation, or trusted-list question.
  • Use Assessment Autopilot to assign owners for CPS updates, mapping, publication evidence, identity validation, revocation, and status-service controls.
  • Use Research Copilot to answer profile, scope, and source interpretation questions with cited outputs.
  • Keep official standard citations separate from organization-specific policy choices and assessor requests.