Comparison GuideGLOBALETSI EN 319 401

ETSI EN 319 401 vs EN 319 403-1 TSP policy vs conformity assessment

A practical comparison for teams that need to separate a trust service provider's operating controls from the conformity-assessment context around those controls.

Grounded in ETSI EN 319 401 V3.1.1 and its references. EN 319 403-1 coverage is intentionally limited where the local reference only confirms its title and role.

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

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

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

Use this page when an audit plan, procurement question, trust service policy, or evidence request mentions both ETSI EN 319 401 and ETSI EN 319 403-1. EN 319 401 is the general policy baseline for the operation and management practices of trust service providers. EN 319 401 points to EN 319 403-1 for requirements for conformity assessment bodies assessing trust service providers, so the comparison should keep provider obligations and assessor-facing expectations separate.

Side-by-side comparison

ETSI EN 319 401 vs ETSI EN 319 403-1: what changes operationally?

Use this table to keep the trust service provider's EN 319 401 operating evidence separate from the EN 319 403-1 conformity-assessment-body context.

Review all sources
First framework
ETSI EN 319 401

General policy requirements for trust service providers, focused on the TSP's operation and management practices across trust service policy, risk, security, incidents, continuity, termination, and suppliers.

Second framework
ETSI EN 319 403-1

Referenced by EN 319 401 for requirements for conformity assessment bodies assessing trust service providers; this page limits 403-1 detail to that supported comparator role.

Comparison row 1

Scope and covered activity

ETSI EN 319 401

EN 319 401 applies to general policy requirements for TSPs and is independent of the type of TSP; it defines requirements on operation and management practices.

ETSI EN 319 403-1

EN 319 403-1 is identified as the standard for requirements for conformity assessment bodies assessing TSPs, not as another TSP operating-policy baseline.

Operational implication

Write the scope memo around the trust service and TSP first; add CAB assessment scope only after the assessor-facing standard is confirmed.

Comparison row 2

Who owns the work

ETSI EN 319 401

The TSP owns EN 319 401 implementation through management approval, policy ownership, trusted roles, personnel controls, operational controls, incident handling, continuity, termination planning, and supplier oversight.

ETSI EN 319 403-1

The CAB-side owner is the conformity assessment body and its assessment process; the local reference does not support assigning detailed EN 319 403-1 duties to TSP staff.

Operational implication

Assign TSP evidence owners for EN 319 401 and keep assessor requests in a separate log with the CAB contact, date, standard version, and requested evidence.

Comparison row 3

Trigger or threshold

ETSI EN 319 401

EN 319 401 work starts when a provider is defining, operating, changing, assessing, or evidencing a trust service policy and the related TSP operation.

ETSI EN 319 403-1

EN 319 403-1 becomes relevant when a conformity assessment body is assessing a trust service provider; detailed trigger facts should be confirmed in EN 319 403-1.

Operational implication

Rerun the comparison when the trust service, policy, significant systems, suppliers, incident history, or assessment scope changes.

Comparison row 4

Core obligations

ETSI EN 319 401

Convert EN 319 401 into TSP controls for risk assessment, risk treatment, practice statements, terms and conditions, information security policy, personnel, assets, access control, cryptographic controls, physical security, operational security, network security, incidents, continuity, termination, compliance, and supply chain.

ETSI EN 319 403-1

Convert EN 319 403-1 into assessment-body requirements only after direct clause review; this page supports the CAB-assessment context but does not restate detailed EN 319 403-1 obligations.

Operational implication

Use EN 319 401 as the provider evidence checklist and label EN 319 403-1 items as assessor-confirmed only when the clause has been checked.

Comparison row 5

Evidence and records

ETSI EN 319 401

Evidence should include the risk assessment, risk treatment records, practice statement, terms and conditions, information security policy, asset inventory, trusted-role appointments, access records, monitoring and incident records, continuity and crisis-management tests, termination plan, and supplier agreements.

ETSI EN 319 403-1

Assessment evidence should be organized so a CAB can trace each TSP control to a source, owner, version, and record; EN 319 403-1-specific evidence fields require direct confirmation.

Operational implication

Maintain one source-to-evidence matrix with an EN 319 401 column and a separate EN 319 403-1 confirmation status column.

Comparison row 6

Timing and cadence

ETSI EN 319 401

EN 319 401 requires recurring review patterns, including regular risk-assessment review and review of the information security policy and asset inventory at planned intervals or when significant changes occur.

ETSI EN 319 403-1

The EN 319 403-1 assessment cadence is not grounded in the available local source set; confirm assessment planning and cycle details directly before stating them.

Operational implication

Use EN 319 401 to schedule internal evidence maintenance, and treat CAB assessment timing as a separate confirmed fact.

Comparison row 7

Enforcement and supervisory context

ETSI EN 319 401

EN 319 401 compliance by TSPs operating under eIDAS is supervised through the national supervisory body for trust services in each Member State, which reviews whether TSP policies, practices, and security controls meet the relevant eIDAS and delegated-act requirements.

ETSI EN 319 403-1

Conformity assessment under EN 319 403-1 is enforced through the CAB accreditation chain and the TSP audit cycle. A qualified TSP must obtain a conformity assessment from an accredited CAB before national supervisory body listing; ongoing assessments renew the compliance record.

Operational implication

Record the enforcement route separately: TSP supervisory correspondence, CAB audit scope, accreditation body, and any conditions attached to the conformity assessment report.

Comparison row 8

Overlap and reuse

ETSI EN 319 401

EN 319 401 evidence can be reused when the trust service boundary, version, policy, systems, suppliers, and assessment period match the claim being made.

ETSI EN 319 403-1

CAB-facing reuse should be treated as conditional until the EN 319 403-1 assessment expectation and the CAB request are known.

Operational implication

Reuse evidence only with a visible boundary statement: trust service, policy, system, period, standard version, evidence owner, and assessment status.

Comparison row 9

Practical decision rule

ETSI EN 319 401

If the task is to design, operate, document, or maintain a trust service provider control, start with EN 319 401.

ETSI EN 319 403-1

If the task is to understand how a conformity assessment body assesses the TSP, confirm the relevant EN 319 403-1 clause and keep that assessor requirement separate.

Operational implication

A defensible comparison has three outputs: a TSP evidence map, a CAB assessment question list, and an explicit list of EN 319 403-1 details still requiring direct confirmation.

Practical decision rule

How should teams decide whether a task belongs in EN 319 401 or EN 319 403-1?

  • Use EN 319 401 when designing, implementing, documenting, or maintaining trust service policies, practices, controls, incident procedures, or security evidence.
  • Use EN 319 403-1 when scoping a conformity assessment engagement, agreeing assessment scope with a CAB, preparing evidence for an auditor, or interpreting an audit report.
  • Keep TSP implementation evidence and CAB assessment evidence in separate folders so each reviewer can trace their own requirements without reading across both standards.
  • Escalate when EN 319 403-1 audit scope or sampling decisions raise questions that need TSP policy clarification, because the two standards interact at the assessment boundary.
Section 1

Why compare ETSI EN 319 401 with ETSI EN 319 403-1?

ETSI EN 319 401 V3.1.1 specifies general policy requirements for trust service providers, independent of the type of trust service. It covers the provider's risk assessment, policy documents, information security policy, management and operation, incident handling, continuity, termination, and supply-chain controls.

The same ETSI EN 319 401 grounding identifies ETSI EN 319 403-1 as the standard for requirements for conformity assessment bodies assessing trust service providers. That makes the comparison useful, but it does not make the two standards interchangeable: one is the TSP operating-policy baseline; the other is the conformity-assessment-body context.

  • Use EN 319 401 to build or review TSP policy, practice, risk, security, operational, incident, continuity, and supplier evidence.
  • Use EN 319 403-1 references to identify where a conformity assessment body may need different assessment records or procedures.
  • Do not copy a TSP control narrative into a CAB assessment file without confirming which side actually asks for that evidence.
Section 2

What ETSI EN 319 401 controls before assessment starts

Start the EN 319 401 side with the trust service boundary. The standard defines policy requirements on the operation and management practices of TSPs and says the requirements are independent of the type of TSP.

A useful implementation file should therefore name the trust service policy, the TSP practice statement, terms and conditions, information security policy, risk assessment, management approvals, trusted roles, asset inventory, access controls, incident procedures, continuity plans, termination plan, and supplier controls that support the service.

  • Document the risk assessment and management approval of residual risk before treating a control set as complete.
  • Keep the TSP practice statement and terms and conditions aligned with the trust service policy being offered.
  • Tie evidence to named TSP systems, facilities, personnel roles, suppliers, and service components rather than broad claims of compliance.
Section 3

Where EN 319 403-1 enters the workflow

In the available EN 319 401 grounding, EN 319 403-1 appears as an informative reference for requirements for conformity assessment bodies assessing trust service providers. That is enough to justify a comparison, but not enough to restate EN 319 403-1 audit procedures clause by clause.

Treat EN 319 403-1 as the assessor-side reference point: it helps teams ask what a conformity assessment body needs in order to assess the TSP's EN 319 401 evidence. For detailed CAB competence, audit, reporting, impartiality, or decision requirements, confirm the current EN 319 403-1 text directly before publishing claims.

  • Keep a separate assessment index for the conformity assessment body rather than embedding assessor assumptions in the TSP policy.
  • Mark any EN 319 403-1-specific requirement as unconfirmed until the exact clause is checked in EN 319 403-1.
  • When a customer asks for both standards, answer with two columns: TSP control evidence and CAB assessment evidence.
Section 4

Evidence that usually belongs on the EN 319 401 side

EN 319 401 evidence should show that the TSP has translated policy requirements into working operations. The source material supports evidence around risk assessment, risk treatment, trust service practice statements, terms and conditions, information security policy, trusted roles, access control, physical and environmental security, operational security, network security, vulnerability and incident management, business continuity, termination, compliance, and supply chain.

Visitor-facing pages should avoid unsupported labels such as assessed, certified, qualified, or conformant unless they also identify the assessment scheme, boundary, service, version, and source that supports the claim.

  • Risk file: risk identification, analysis, evaluation, risk treatment measures, management approval, and review cadence.
  • Policy file: trust service policy mapping, practice statement, terms and conditions, and information security policy.
  • Operations file: trusted roles, personnel evidence, asset inventory, access reviews, monitoring logs, incident records, continuity tests, termination plan, and supplier agreements.
  • Assessment handoff: an evidence index that tells the CAB where each EN 319 401 requirement is implemented and maintained.
Section 5

Decision checklist for implementation teams

Use this checklist when the comparison is blocking an audit package, procurement response, or internal release decision. Each item should be answerable from the evidence file, not from memory.

  • Name the trust service and the applicable trust service policy before mapping EN 319 401 controls.
  • Identify whether the user question is about TSP operations, CAB assessment, or both.
  • Attach each EN 319 401 claim to a source-linked evidence artifact and owner.
  • Flag every EN 319 403-1-specific claim that still needs direct clause confirmation.
  • Review evidence after significant changes to services, systems, information security policy, suppliers, incidents, or termination arrangements.
Section 6

Common mistakes in this comparison

The most common mistake is treating EN 319 401 and EN 319 403-1 as two labels for the same evidence. The safer approach is to keep the TSP operating evidence, the legal context, and the conformity-assessment evidence visibly separate.

Another common mistake is overstating eIDAS or qualified-status claims. EN 319 401 includes an informative mapping to eIDAS requirements and references qualified trust service context, but public claims still need the exact legal, service, and assessment basis.

  • Do not state that a service is qualified, certified, assessed, or conformant unless the evidence file proves the boundary and scheme.
  • Do not cite EN 319 403-1 as support for a TSP operational control unless the specific CAB-side requirement has been checked.
  • Do not mix generic cybersecurity controls with EN 319 401 evidence unless the control is mapped to a trust service risk, policy, or operation.
  • Do not publish local source filenames, draft notes, or internal evidence paths as public sources.
Primary sources

References and citations

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 eIDAS Article 19 and 24
Compare ETSI EN 319 401 V3.1.1 with the eIDAS provisions mapped in Annex B: trust service risk management, incident handling, records, staff, terms, and termination planning.
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.