Artifact GuideGLOBALETSI EN 319 401

ETSI EN 319 401 vs eIDAS

A narrow comparison between ETSI EN 319 401 V3.1.1 and the eIDAS provisions ETSI maps in Annex B.

Use it to separate the ETSI baseline for trust service providers from the eIDAS legal duties that still need legal and supervisory review.

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

Structured answer sets in this page tree.

Primary sources
24

Cited legal and guidance references.

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

ETSI EN 319 401 is not a replacement for eIDAS. The standard specifies general policy requirements for Trust Service Providers and includes an informative Annex B mapping selected EN 319 401 requirements to eIDAS Regulation provisions. This page turns that mapping into practical scoping and evidence questions without claiming full eIDAS coverage.

Side-by-side comparison

ETSI EN 319 401 vs eIDAS: what changes operationally?

This comparison is limited to the eIDAS provisions ETSI maps in EN 319 401 Annex B and to service-specific warnings supported by the ETSI grounding.

Review all sources
First framework
ETSI EN 319 401

A general TSP policy baseline for operation and management practices, including risk, security policy, personnel, incident handling, continuity, records, termination, and suppliers.

Second framework
eIDAS mapped provisions

Selected eIDAS obligations mapped by EN 319 401 Annex B, mainly Article 19 security requirements and specific Article 24.2 requirements for qualified trust service providers.

Comparison row 1

Scope and covered activity

ETSI EN 319 401

EN 319 401 covers general policy requirements for Trust Service Providers, independent of trust service type, and does not define every service-specific assessment requirement.

eIDAS mapped provisions

The source-linked comparator is the Annex B mapping to selected eIDAS provisions, not the full eIDAS Regulation.

Operational implication

Define the trust service first, then state whether the work is only the EN 319 401 baseline, an Annex B eIDAS mapping, or a service-specific qualified trust service assessment.

Comparison row 2

Who must act

ETSI EN 319 401

EN 319 401 assigns work to the TSP and its management, including approval of risk assessment, information security policy, role allocation, personnel competence, and supplier control.

eIDAS mapped provisions

Annex B maps qualified trust service provider duties in Article 24.2 for staff and subcontractors, change or cessation notification, terms, records, and termination planning.

Operational implication

Assign both operational control owners and legal or supervisory owners; the same artifact may support both, but accountability should not be collapsed.

Comparison row 3

Trigger or threshold

ETSI EN 319 401

EN 319 401 triggers operational review when risk assessments, information security policy, assets, suppliers, incidents, continuity plans, or service termination facts change.

eIDAS mapped provisions

Annex B makes the clearest eIDAS trigger explicit for Article 19.2: a breach of security or loss of integrity with significant impact on the trust service or maintained personal data.

Operational implication

Keep a trigger register that distinguishes planned reviews, significant changes, supplier incidents, service termination, and reportable Article 19.2 events.

Comparison row 4

Core obligations

ETSI EN 319 401

EN 319 401 requires the TSP to assess risks, select treatment measures, document policies and procedures, manage personnel and assets, operate security controls, handle incidents, maintain continuity, keep records, and manage suppliers.

eIDAS mapped provisions

Annex B ties Article 19 to risk and security measures, incident prevention and impact reduction, notification, and continuity; it ties selected Article 24.2 points to staff, terms, financial resources or insurance, records, and termination planning.

Operational implication

Build a crosswalk row only when the ETSI control and the eIDAS mapped duty point to the same service boundary and evidence artifact.

Comparison row 5

Evidence and records

ETSI EN 319 401

EN 319 401 evidence should include the risk assessment, residual-risk approval, Trust Service Practice statement, terms and conditions, security policy, asset inventory, monitoring logs, incident records, continuity tests, and supplier agreements.

eIDAS mapped provisions

The mapped eIDAS evidence should show the Article 19 security and incident path, plus any selected Article 24.2 evidence such as pre-contract terms, staff competence, records retained for legal proceedings, or termination plan.

Operational implication

Label each artifact by source: EN 319 401 baseline, Annex B Article 19 support, selected Article 24.2 support, or service-specific qualified trust service evidence.

Comparison row 6

Timing and cadence

ETSI EN 319 401

EN 319 401 uses planned review cycles and event-driven reviews, including regular risk assessment review, planned information security policy review, incident procedure testing, continuity plan testing, and supplier monitoring.

eIDAS mapped provisions

Annex B reproduces the Article 19.2 notification clock for significant breaches as without undue delay and in any event within 24 hours after awareness.

Operational implication

Do not let an internal annual review cadence hide a reportable breach clock; keep planned control reviews and incident notification timing separate.

Comparison row 7

Enforcement or assurance route

ETSI EN 319 401

EN 319 401 states that it does not specify how requirements are assessed by an independent party and points to EN 319 403-1 for conformity assessment bodies.

eIDAS mapped provisions

For eIDAS, Annex B references supervisory bodies and other relevant bodies in the Article 19.2 mapping, and qualified-service change or cessation notices in Article 24.2(a).

Operational implication

Use EN 319 401 to build assessor-ready operational evidence, but confirm the legal notification path and any conformity assessment route from the applicable eIDAS and service-specific sources.

Comparison row 8

Overlap and reuse

ETSI EN 319 401

EN 319 401 evidence can be reused where it proves the same TSP operation, control, and review result for the same service boundary.

eIDAS mapped provisions

Annex B supports reuse only for the mapped Article 19 and selected Article 24.2 points; unmapped eIDAS duties need their own source analysis.

Operational implication

Reuse evidence with a bridge note that names the EN 319 401 clause family, the mapped eIDAS provision, the artifact, the owner, and any remaining legal gap.

Comparison row 9

Practical decision rule

ETSI EN 319 401

Use EN 319 401 as the control baseline when the task is to operate and evidence a TSP management, security, incident, continuity, record, or supplier control.

eIDAS mapped provisions

Use the eIDAS side when the decision is about a legal duty, supervisory notification, qualified trust service obligation, or an unmapped eIDAS provision.

Operational implication

The crosswalk is useful for implementation evidence, but it is not a legal conclusion that EN 319 401 alone satisfies eIDAS.

Practical decision rule

How to choose the controlling source

  • Use EN 319 401 when the work is a general TSP policy, risk, security, incident, continuity, record, termination, or supplier control.
  • Use the Annex B crosswalk when the question is specifically Article 19 or one of the selected Article 24.2 points ETSI maps.
  • Use eIDAS and the relevant service-specific ETSI standard when the question is legal effect, supervisory status, qualified-service authorization, certificate policy, or any unmapped eIDAS duty.
Section 1

When should teams compare ETSI EN 319 401 with eIDAS?

Compare them when a trust service provider needs to show how its general ETSI controls support an eIDAS-driven trust service obligation. The strongest source coverage is for the Annex B mapping in ETSI EN 319 401 V3.1.1, especially eIDAS Article 19 and selected Article 24.2 points.

Do not use this comparison to decide every eIDAS question. ETSI EN 319 401 says other specifications refine the baseline for particular trust-service types, and it points to ETSI EN 319 411-2 as an example for EU qualified certificate providers.

  • Use the comparison for trust service risk management, information security policy, incident handling, continuity, records, terms and conditions, staff competence, and termination planning.
  • Treat Annex B as an informative map, then keep the legal eIDAS obligation and the ETSI operational control in separate columns.
  • Escalate certificate-specific, qualified-service-specific, supervisory, penalty, and legal-effect questions to the applicable eIDAS text and service-specific ETSI standard.
Section 2

What ETSI EN 319 401 actually contributes

EN 319 401 specifies baseline policy requirements for the operation and management practices of TSPs, independent of the type of trust service. It covers risk assessment, Trust Service Practice statements, terms and conditions, information security policy, internal organization, personnel, assets, access control, incident management, continuity, termination, and supplier relationships.

That makes it useful for building an evidence pack, but it does not by itself define every legal result under eIDAS or every assessment method for a particular qualified trust service.

  • Start the EN 319 401 side with a current risk assessment approved by TSP management and linked to selected treatment measures.
  • Keep the Trust Service Practice statement, terms and conditions, information security policy, and asset inventory under review after significant changes.
  • Map each operational control to evidence: policies, role descriptions, training records, monitoring logs, incident records, continuity tests, supplier agreements, and termination records.
Section 3

Where the eIDAS comparison is source-linked

Annex B in EN 319 401 maps eIDAS Article 19 security requirements to EN 319 401 clauses 5, 6.3, and 7.2 through 7.12. That supports a concrete crosswalk for risk management, security controls, incident prevention, incident impact reduction, notifications, stakeholder communication, and continuity.

Annex B also maps selected eIDAS Article 24.2 requirements for qualified trust service providers: change and cessation notifications, competent staff and subcontractors, financial resources or liability insurance, pre-contract terms and conditions, records, and termination planning.

  • Use Article 19 mapping for risk assessment, information security policy, personnel controls, operations, monitoring, incident response, reporting, and business continuity.
  • Use Article 24.2 mapping only for the points ETSI lists; do not infer coverage for unmapped qualified-trust-service duties.
  • For EU qualified certificates, use EN 319 411-2 or another service-specific ETSI source before claiming that EN 319 401 evidence is complete.
Section 4

Evidence model for a defensible crosswalk

Build the comparison as an evidence matrix, not as a merged checklist. Each row should identify the eIDAS provision, the EN 319 401 clause or requirement family, the service boundary, the owner, and the artifact that proves the control is operated.

The most useful evidence is concrete: risk assessment outputs, management approval of residual risk, Trust Service Practice statements, terms and conditions, information security policy, personnel competence records, incident logs, post-incident reviews, continuity plans, backup records, supplier registers, and termination notices.

  • Record whether the evidence supports EN 319 401 only, an Annex B eIDAS mapping, or a service-specific qualified-trust-service claim.
  • Keep Article 19 incident evidence tied to detection, response, notification, stakeholder communication, post-incident review, and continuity interfaces.
  • Keep Article 24.2 evidence tied to the exact mapped point, such as terms before contract, staff competence, record retention, or termination planning.
Section 5

Implementation checklist for ETSI EN 319 401 vs eIDAS

Use this checklist before a customer response, conformity-assessment preparation, qualified-service change, or internal audit. Every item should produce a visible artifact rather than a general claim of compliance.

  • Confirm the trust service type and whether the claim is non-qualified, qualified, certificate-specific, or another service-specific ETSI profile.
  • Create an Annex B map for eIDAS Article 19 and the selected Article 24.2 points that actually apply to the service.
  • Attach EN 319 401 clauses to owners for risk assessment, policy maintenance, staff competence, incident response, continuity, records, and supplier management.
  • Name any service-specific ETSI standard needed before claiming qualified certificate or other qualified trust service coverage.
  • Document unresolved eIDAS questions instead of filling them with generic compliance language.
Section 6

Common mistakes in this comparison

The usual failure mode is overclaiming: teams read the Annex B mapping as if EN 319 401 proves full eIDAS compliance. The safer reading is that EN 319 401 supplies a general TSP control baseline that can support selected eIDAS obligations when the service boundary and evidence match.

  • Do not claim full eIDAS compliance from EN 319 401 alone.
  • Do not apply qualified certificate conclusions without a service-specific source such as EN 319 411-2.
  • Do not mix Article 19 incident reporting evidence with unrelated operational logs unless the logs show detection, response, notification, and review decisions.
  • Do not cite internal files or local reference paths; source URLs on the public page must be external HTTPS links with the Sorena reference parameter.
Primary sources

References and citations

etsi.org
Referenced sections
  • Source for the Article 19 and selected Article 24.2 mapping used in this comparison.
"Regulation article 19 Security requirements applicable to trust service providers"
etsi.org
Referenced sections
  • Source for the limit that EN 319 401 does not define independent assessment methods.
"does not specify how the requirements identified can be assessed"
etsi.org
Referenced sections
  • Source for using EN 319 401 as the general TSP control baseline.
"general policy requirements"
Related guides

Explore more topics

CA and RA responsibilities under ETSI EN 319 401
How ETSI EN 319 401 frames CA and RA responsibility: TSP practice statements, management approval, role segregation, subcontractor control, and evidence boundaries.
eIDAS Articles 19 and 24 in ETSI EN 319 401
See how ETSI EN 319 401 V3.1.1 Annex B maps eIDAS Article 19 security duties and selected Article 24 qualified trust service duties to concrete policy evidence.
ETSI EN 319 401 Audit and Conformity Assessment Evidence
How to prepare ETSI EN 319 401 evidence for audit and conformity assessment without overstating what the standard itself assesses.
ETSI EN 319 401 Audit Evidence Pack
Build an ETSI EN 319 401 audit evidence pack around records, logs, policies, risk assessment, incident handling, continuity, and supplier evidence.
ETSI EN 319 401 Audit Evidence Pack Workflow
Build an ETSI EN 319 401 audit evidence pack for trust service providers: risk assessment, practice statement, policies, records, logs, continuity, and supplier evidence.
ETSI EN 319 401 compliance duties for TSPs
source-linked ETSI EN 319 401 compliance guidance for trust service providers: legal operation, evidence, accessibility, privacy, records, incidents, continuity, and suppliers.
ETSI EN 319 401 conformity assessment bodies: what is covered?
Understand what ETSI EN 319 401 says, and does not say, about conformity assessment bodies, independent assessment, and TSP evidence preparation.
ETSI EN 319 401 FAQ for trust service providers
source-linked ETSI EN 319 401 FAQ for TSP scope, trust service practice statements, risk assessment, incidents, records, continuity, and supplier evidence.
ETSI EN 319 401 Incident Evidence Workflow
Build an EN 319 401 incident and continuity evidence workflow for TSP monitoring, response, reporting, records, backup recovery, and crisis review.
ETSI EN 319 401 Incident Reporting and Continuity Duties
Practical ETSI EN 319 401 V3.1.1 guidance for trust service incident response, reporting, evidence retention, business continuity, and termination planning.
ETSI EN 319 401 Personnel, Asset, and Access Controls
Clause-focused EN 319 401 V3.1.1 guide to TSP personnel duties, trusted roles, asset inventories, classification, and access-control evidence.
ETSI EN 319 401 policy and security requirements
source-linked ETSI EN 319 401 guidance for TSP policy and security requirements: risk assessment, practice statements, terms, security policy, controls, incidents, and evidence.
ETSI EN 319 401 policy documentation: what is required?
How ETSI EN 319 401 treats policy documentation: practice statements, terms and conditions, information security policy, evidence records, and change review.
ETSI EN 319 401 requirements map
Map ETSI EN 319 401 V3.1.1 requirements for trust service providers across risk assessment, policies, TSP operations, incidents, evidence, continuity, termination, and supply chain controls.
ETSI EN 319 401 Risk Assessment and Treatment
Clause-grounded ETSI EN 319 401 V3.1.1 guidance for trust service risk assessment, risk treatment, residual-risk approval, and evidence planning.
ETSI EN 319 401 Subcontractor Controls
Practical EN 319 401 guidance for TSP subcontractor controls: retained responsibility, agreements, SLAs, supplier registers, monitoring, and audit evidence.
ETSI EN 319 401 Subcontractor Evidence Workflow
Build an EN 319 401 subcontractor evidence workflow for TSP supplier agreements, SLAs, audit mechanisms, risk reviews, supplier registers, and archived records.
ETSI EN 319 401 Subcontractor Requirements FAQ
How ETSI EN 319 401 treats subcontractors, outsourcing, supplier agreements, SLAs, monitoring, evidence, and retained TSP responsibility.
ETSI EN 319 401 Trust Service Applicability Workflow
A scoped workflow for deciding when ETSI EN 319 401 applies to a trust service and what TSP policy, risk, terms, operations, and supplier evidence to collect.
ETSI EN 319 401 Trust Service Provider Applicability
Use ETSI EN 319 401 to decide whether a trust service provider activity falls in the standard's type-independent baseline and what service, policy, risk, supplier, and evidence boundaries to document.
ETSI EN 319 401 vs EN 319 403-1: TSP Policy vs CAB Assessment
Compare ETSI EN 319 401 and ETSI EN 319 403-1 for trust service providers: TSP operating controls, conformity assessment context, evidence boundaries, and reuse limits.
Security Incidents in ETSI EN 319 401
How ETSI EN 319 401 V3.1.1 expects trust service providers to detect, respond to, report, classify, document, and review security incidents.
Trust service provider scope under ETSI EN 319 401
How to scope ETSI EN 319 401 for a trust service provider: service boundaries, trust service policy, practice statement, terms, risks, and third-party components.