Artifact GuideGLOBALETSI EN 319 401

ETSI EN 319 401 Audit and conformity assessment evidence

A source-linked guide to preparing EN 319 401 policies, practice statements, terms, records, and evidence for audit or assessor review.

EN 319 401 defines general TSP policy requirements; it does not define the independent assessment method, so assessor scope and scheme claims need separate support.

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

Structured answer sets in this page tree.

Primary sources
2

Cited legal and guidance references.

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

Use this page when a trust service provider needs to turn ETSI EN 319 401 into evidence that can be reviewed by internal audit, customers, supervisory stakeholders, or an external assessor. The key boundary is narrow: EN 319 401 specifies general policy requirements for TSP operation and management, while conformity-assessment-body requirements sit outside this standard.

Section 1

Start with the assessment boundary

ETSI EN 319 401 applies to Trust Service Providers and defines general policy requirements for their operation and management, independent of the specific trust service type. It also states that other specifications refine those requirements for particular forms of TSP.

For audit planning, this means the EN 319 401 evidence pack should not claim that the standard itself defines an independent-party assessment method. The standard explicitly says it does not specify how requirements are assessed by an independent party, and points readers to ETSI EN 319 403-1 for conformity assessment bodies assessing TSPs.

  • Name the trust service, operating boundary, and applicable trust service policy before mapping EN 319 401 clauses.
  • Separate EN 319 401 requirement evidence from assessment-scheme evidence, assessor rules, certificates, trust-list entries, or regulator-specific submissions.
  • Use EN 319 401 as the baseline for TSP operation and management controls, then add service-specific ETSI standards where the trust service type requires them.
  • Avoid public claims such as certified, qualified, assessed, or conformant unless the scheme, assessor, service boundary, policy, and assessment result are independently documented.
Section 2

Evidence the assessor will expect to trace

The most useful EN 319 401 audit file is a traceable set of policies, practice statements, terms, records, and review decisions. Clause 6 requires the TSP to specify policies and practices for the trust services it provides, have management approval, communicate them to relevant employees and external parties, and maintain a review process for the practice statement.

The terms and conditions are especially important because EN 319 401 requires them to identify the trust service policy, limitations on use, subscriber obligations, relying-party information, event-log retention, liability limitations, applicable legal system, complaints and dispute procedures, conformity-assessment status and scheme where applicable, and TSP contact information.

  • Keep the trust service practice statement mapped to each applicable trust service policy and to the obligations of external organizations supporting the service.
  • Preserve management approval evidence for the policy set, practice statement, and information security policy.
  • Show how revised practice statements are reviewed, approved, made available, and notified when changes may affect subscribers, subjects, or relying parties.
  • Treat the terms and conditions as audit evidence, not just customer copy, because EN 319 401 uses them to disclose retention, liability, complaints, and assessment status.
Section 3

Build a clause-to-evidence audit index

A clause-to-evidence index should make the EN 319 401 control story inspectable without relying on tribal knowledge. At minimum, map risk assessment, information security policy, management and operations, incident management, continuity, termination planning, compliance with legal requirements, and supply-chain controls to owners and current evidence.

Clause 7.10 is central for audit readiness because it requires relevant information concerning data issued and received by the TSP to be recorded and kept accessible for an appropriate period, including after TSP activities have ceased, for legal evidence and service continuity purposes. It also requires confidentiality and integrity of current and archived records, disclosed archival practices, availability for evidence of correct operation in legal proceedings, precise timing of significant events, and UTC synchronization for audit-log event times at least once a day.

  • Map each EN 319 401 requirement ID to the control owner, evidence artifact, evidence location, review date, and exception status.
  • Include records showing risk assessment approval, residual-risk acceptance, information security policy approval, and regular review.
  • Index event logs, incident classifications, post-incident reviews, continuity tests, backup recovery tests, and termination-plan evidence where they support the relevant clauses.
  • Record the disclosed retention period used for service records and ensure it matches the public terms and conditions.
Section 4

Explain eIDAS relevance without overclaiming

EN 319 401 includes an informative mapping to Regulation (EU) No 910/2014. That mapping connects eIDAS Article 19 security requirements to EN 319 401 clauses on risk, information security, management, operations, incident handling, and continuity. It also maps Article 24 qualified trust service provider duties to specific EN 319 401 areas, including terms and conditions, changes in qualified trust services, trustworthy systems, records, and continuity.

For public-facing evidence, use this mapping as context rather than a standalone legal conclusion. A page can say which EN 319 401 evidence supports an eIDAS-related control area, but it should not claim qualified status, trusted-list inclusion, supervisory approval, or legal compliance unless those facts are separately evidenced.

  • Use the EN 319 401 Annex B mapping to explain why risk, incident, continuity, records, and terms-and-conditions evidence matter for eIDAS-oriented trust services.
  • Keep qualified-service claims separate from general EN 319 401 controls and require service-specific support before publishing them.
  • When certificate services are in scope, add EN 319 411-1 or EN 319 411-2 evidence instead of relying on EN 319 401 alone.
  • Document the difference between internal audit readiness, customer evidence, conformity assessment, and legal or supervisory status.
Section 5

Common audit-readiness failures

Most weak EN 319 401 audit files fail because the evidence is either too broad or too detached from the service being assessed. A generic security policy is not enough if it cannot be traced to the trust service practice statement, the applicable trust service policy, the service records, and the disclosed terms.

The other common failure is claiming more than the source supports. EN 319 401 can support a disciplined evidence model for TSP operation and management, but conformity assessment details, assessor competence, scheme rules, certificate-service policies, and qualified-service status must come from the relevant external scheme, service-specific ETSI standard, or legal evidence.

  • Do not describe EN 319 401 as a complete audit methodology or conformity assessment scheme.
  • Do not treat service-specific certificate, time-stamp, validation, preservation, or registered delivery requirements as covered unless the applicable service standard is mapped.
  • Do not publish an assessment claim without naming the trust service, policy, conformity assessment scheme, assessment period, and evidence boundary.
  • Do not keep retention, complaint, liability, or assessment-status facts only in private spreadsheets when EN 319 401 expects them in subscriber and relying-party terms.
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 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.
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.