Artifact GuideGLOBALETSI EN 319 401

ETSI EN 319 401 Subcontractor Evidence Workflow

A practical evidence workflow for trust service providers that use subcontractors, outsourcers, suppliers, cloud providers, or trust service component providers.

Grounded in ETSI EN 319 401 V3.1.1 clauses on policies, supplier relationships, records, and supply-chain responsibility. Use it as implementation guidance, supporting implementation planning and should be validated against jurisdiction-specific legal, contractual, and policy requirements before implementation.

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

Structured answer sets in this page tree.

Primary sources
6

Cited legal and guidance references.

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

Use this page to turn EN 319 401 subcontractor and supplier requirements into an audit-ready evidence workflow. The focus is narrow: what a trust service provider should collect, review, retain, and update when another party provides part of the trust service or supplies ICT products or services that support it.

Section 1

When does subcontractor evidence become in scope?

Start with the trigger. EN 319 401 treats subcontracting, outsourcing, and other third-party arrangements as in-scope when another party provides parts of the TSP's service. That can include trust service component providers, direct suppliers, service providers, ICT suppliers, and cloud computing providers where they support the service boundary.

The key evidence point is retained accountability. When the TSP uses other parties to provide parts of its service, EN 319 401 says the TSP keeps overall responsibility for conformance with its supply chain policy, information security policy, and the requirements defined in the trust service policy.

  • Name the supplied product, service, component, or cloud service and explain how it supports the trust service.
  • Record whether the relationship is subcontracting, outsourcing, a third-party arrangement, a direct supplier relationship, or use of a trust service component.
  • Map the relationship to the TSP supply chain policy, information security policy, trust service policy, and practice statement.
  • Keep the scope narrow enough that evidence can show which party is responsible for each required control.
Section 2

Evidence to collect before a supplier is used

Before relying on a supplier or subcontractor, collect evidence that the selection and contracting decision used EN 319 401 criteria. The supplier evidence should show its ability to meet the TSP's cybersecurity specifications, risk position, and classification levels for the services, systems, or products being delivered.

The contract file should also show the liability model, required controls, commencement requirements, termination requirements, and a documented agreement or contractual relationship that makes both parties' information security obligations clear.

  • Selection record: criteria used to select and contract the supplier or service provider, including cybersecurity requirements and risk/classification fit.
  • Risk record: supplier risk assessment input, including any coordinated security risk assessment for a critical supply chain.
  • Contract evidence: documented agreement, liability allocation, required TSP controls, and supplier obligations for information security.
  • Start and exit controls: evidence of controls required before use begins and controls required when supplier products or services are terminated.
Section 3

Evidence to maintain while the supplier is active

Operational evidence should show that supplier controls are not frozen at onboarding. EN 319 401 requires monitoring, review, evaluation, and change management for supplier information security practices and service delivery, including planned reviews and review after incidents related to supplier-provided services.

For ICT suppliers, the workflow should also preserve evidence that security requirements are propagated through subcontracted ICT services, that supplier product or service components critical to functionality are identified, and that the TSP has acceptable methods for validating that ICT products and services conform to stated cybersecurity requirements.

  • Monitoring evidence: review logs, supplier service review minutes, change records, and incident-triggered supplier reassessments.
  • SLA or audit mechanism: service agreements should include service level agreements and/or auditing mechanisms aligned with the TSP risk assessment.
  • ICT supply-chain evidence: downstream security requirement propagation, software component information, implemented security functions, secure configuration information, and critical component records where applicable.
  • Supplier register: maintain and update the register of suppliers and agreements so it tracks where TSP information is managed or archived.
Section 4

Subcontractor evidence workflow table

Use this workflow as the operating table for a subcontractor evidence pack: Step | Owner | Evidence | Decision.

1 | Service owner | Supplier scope note, supported trust service, and component/service description | Does this relationship provide or support part of the TSP service?

2 | Procurement and security | Selection criteria, risk/classification fit, and supplier due-diligence record | Can the supplier meet the TSP's cybersecurity specifications and risk requirements?

3 | Legal and control owner | Agreement, liability terms, required controls, SLA or auditing mechanism, and start/exit controls | Are both parties' information security obligations clear enough to rely on?

4 | Operations and assurance | Monitoring reviews, change records, incident-triggered reassessments, supplier register updates, and retained operational records | Is the supplier evidence still valid for the current service boundary?

  • Attach requirement identifiers to each row so reviewers can see why the evidence exists.
  • Separate direct EN 319 401 duties from internal procurement preferences or customer-specific clauses.
  • Keep sensitive supplier details out of public-facing summaries while preserving the underlying evidence for assessors and authorized reviewers.
Section 5

Evidence retention and review checkpoints

The supplier file should be retained as part of the TSP's broader record model. EN 319 401 requires relevant information concerning data issued and received by the TSP to be recorded and kept accessible for an appropriate period, including after the TSP's activities have ceased, for legal evidence and continuity purposes.

Review checkpoints should therefore cover both supplier relationship evidence and operational service evidence. The evidence pack is weak if it only contains the original contract and omits updated supplier reviews, incident follow-up, supplier register validation, or records showing where TSP information is managed or archived.

  • Retain current and archived operation records with confidentiality and integrity controls.
  • Make the retention period consistent with the TSP's terms and conditions where EN 319 401 requires notification of retained service records.
  • Review and validate supplier agreements at planned intervals so they remain valid, fit for purpose, and include relevant information security clauses.
  • Use incidents related to supplier-provided services as explicit triggers to review supplier cybersecurity practices and service delivery.
Section 6

Common evidence gaps to remove before assessment

Most subcontractor evidence gaps are practical rather than semantic: the supplier is named, but the service boundary is not; the contract exists, but the required security controls are not traceable; the supplier register exists, but it does not show where TSP information is managed or archived.

Before presenting the pack to a customer, assessor, or internal governance forum, remove unsupported claims. EN 319 401 supports a strong evidence workflow for supplier responsibility, agreements, monitoring, registers, and records; it does not by itself prove that a supplier, service, or TSP is conformant without the actual implementation and assessment evidence.

  • Do not claim EN 319 401 conformity from a contract alone; retain the operational records and review evidence behind the controls.
  • Do not treat a cloud provider or ICT supplier as out of scope when its products or services support the trust service boundary.
  • Do not omit downstream ICT subcontracting where EN 319 401 requires supplier security requirements to propagate through the supply chain.
  • Do not reuse a supplier approval after a service, location, security practice, incident, or agreement change without checking whether reassessment is needed.
Primary sources

References and citations

etsi.org
Referenced sections
  • Grounds the scope trigger for external organizations supporting TSP services and the TSP's retained responsibility when using subcontracting, outsourcing, or third-party arrangements.
"REQ-6.1-04; REQ-7.14.3-01X"
etsi.org
Referenced sections
  • Grounds the workflow structure by combining practice-statement obligations, supplier agreements and monitoring, supplier registers, and retained records.
"REQ-6.1-04; REQ-7.10-01; REQ-7.14.3-12X"
etsi.org
Referenced sections
  • Grounds record retention, archived operation records, retention periods in terms and conditions, planned supplier agreement reviews, and incident-triggered supplier review.
"REQ-7.10-01; REQ-7.10-07; REQ-7.14.3-10X; REQ-7.14.3-12X"
etsi.org
Referenced sections
  • Grounds supplier selection criteria, documented agreements, outsourcer liability, required controls, and commencement/termination control evidence.
"REQ-7.14-04X; REQ-7.14.3-02X; REQ-7.14.3-04X"
etsi.org
Referenced sections
  • Grounds the gap checks for supplier monitoring, cloud-service shared responsibility, downstream security requirement propagation, and supplier register maintenance.
"REQ-7.14.2-03X; REQ-7.14.2-15X; REQ-7.14.3-10X; REQ-7.14.3-11X"
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 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.