ETSI EN 319 401 Gap Analysis
A clause-by-clause self-assessment for trust service providers
ETSI EN 319 401 sets the general policy requirements for trust service providers. Conformity assessments of a qualified trust service provider under eIDAS are normally built on it. Answer the 141 questions below to see which clauses you already cover and where the gaps are.
Based on: ETSI EN 319 401 V3.2.1 (2026-01), the current edition when this checklist was written. Clause numbers and titles follow that edition; check etsi.org for a newer one before you rely on the result.
What this is not: a conformity assessment. It is a self-assessment aid. The questions summarise each clause in our own words and do not cover every requirement, so the standard itself is authoritative. EN 319 401 is also only the base layer: service-specific standards such as EN 319 411-1 and -2 for certificates or EN 319 421 for time-stamps add requirements on top.
Your answers are saved in this browser only, so you can leave and come back. Nothing you enter is sent to our server.
Both fields are only used in the exported report.
Summary
0 of 141 questions answered
- 0 met
- 0 partly
- 0 not met
- 0 not applicable
- 141 unanswered
4 Overview
0 of 3 answered
- 0 met
- 0 partly
- 0 not met
- 0 not applicable
- 3 unanswered
5 Risk Management Framework and Risk Assessment
0 of 5 answered
- 0 met
- 0 partly
- 0 not met
- 0 not applicable
- 5 unanswered
6 Policies and practices
0 of 13 answered
- 0 met
- 0 partly
- 0 not met
- 0 not applicable
- 13 unanswered
7 TSP management and operation
0 of 120 answered
- 0 met
- 0 partly
- 0 not met
- 0 not applicable
- 120 unanswered
4 Overview
4.2 Applicability of Conditional Requirements
0 of 3 answered
Evidence an auditor typically expects: An applicability analysis filed with the risk assessment, showing the reasoning behind each decision and who approved it, in a form you could hand to the supervisory body.
5 Risk Management Framework and Risk Assessment
0 of 5 answered
Evidence an auditor typically expects: The risk methodology, the current risk register and treatment plan, management approval and residual-risk acceptance (minutes or a signed record), the review history, and the procedure and results for measuring the effectiveness of controls.
6 Policies and practices
6.1 Trust Service Practice statement
0 of 5 answered
Evidence an auditor typically expects: The published practice statement with its version history, approval records, the review procedure, change notices in your repository, and the sections on subcontractors and on termination.
Related tool: CPS Builder — draft an RFC 3647-structured practice statement for a CA.
6.2 Terms and Conditions
0 of 3 answered
Evidence an auditor typically expects: The published terms (or PKI disclosure statement), the sign-up or ordering flow showing the terms are presented before the contract is concluded, and archived earlier versions.
6.3 Information and Network Security Policy
0 of 5 answered
Evidence an auditor typically expects: The approved policy with approval date, staff acknowledgements, review minutes, the supervisory-body notification procedure with any past notifications, and configuration-check reports.
7 TSP management and operation
7.1 Internal organization
7.1.1 General
0 of 4 answered
Evidence an auditor typically expects: An organisation chart, role descriptions or a responsibility matrix, the appointment of the security lead with the reporting line, and records of role reviews.
7.1.2 Organization reliability
0 of 4 answered
Evidence an auditor typically expects: The insurance certificate, recent financial statements or a parent-company guarantee, and the complaints procedure together with the complaints log.
7.1.3 Segregation of duties
0 of 2 answered
Evidence an auditor typically expects: A role-conflict matrix, the current list of who holds which role, and system access settings that enforce the separation.
7.2 Human resources
0 of 5 answered
Evidence an auditor typically expects: Trusted-role appointment and acceptance records, the screening policy and evidence that checks were completed, training records, job descriptions, conflict-of-interest declarations, confidentiality clauses in contracts and the remote working policy.
7.3 Asset management
7.3.1 General requirements
0 of 2 answered
Evidence an auditor typically expects: The asset management policy and a mapping that shows which protective controls apply to which class of asset.
7.3.2 Assets classification
0 of 4 answered
Evidence an auditor typically expects: The asset inventory with owners and classification levels, the classification scheme, acceptable-use rules, and joiner/mover/leaver checklists showing returned assets.
7.3.3 Storage media and asset handling
0 of 4 answered
Evidence an auditor typically expects: The media handling and removable media policies, endpoint settings that block removable media, transport records and destruction certificates.
7.4 Access control
7.4.1 General
0 of 5 answered
Evidence an auditor typically expects: The access control policy, access request and approval records, the access rights register, periodic access review reports, leaver tickets and system role configuration.
7.4.2 Privileged and system administration accounts
0 of 3 answered
Evidence an auditor typically expects: The privileged access policy, a list of privileged accounts with named owners, authentication settings, and dated privileged-access review records.
7.4.3 Administration systems
0 of 2 answered
Evidence an auditor typically expects: Network and system diagrams showing the administration systems (jump hosts, management consoles), their hardening baseline and their access configuration.
7.4.4 Identification
0 of 3 answered
Evidence an auditor typically expects: An export from the identity directory, the list of approved shared or service accounts with justification, identity review records and identity-management logs.
7.4.5 Authentication
0 of 4 answered
Evidence an auditor typically expects: The authentication policy, password and lockout settings, session timeout settings, the credential issuance procedure and the record of the last review of authentication methods.
7.4.6 Multi-factor authentication
0 of 2 answered
Evidence an auditor typically expects: Authentication configuration for each system in scope and the list linking asset classification levels to the authentication required.
7.5 Cryptographic controls
0 of 4 answered
Evidence an auditor typically expects: The cryptography policy, key management procedures, key ceremony scripts and signed records, the HSM inventory with certification details, and the latest algorithm review.
Related tool: Key Ceremony Planner — produce the ceremony script and sign-off sheets an auditor will ask for.
7.6 Physical and environmental security
0 of 5 answered
Evidence an auditor typically expects: Site plans showing security zones, physical access lists and logs, alarm and CCTV records, UPS and generator test reports, environmental monitoring records and the data centre contract or certification if hosting is outsourced.
7.7 Operation security
0 of 5 answered
Evidence an auditor typically expects: Secure development rules, change tickets including emergency changes, patch reports and documented exceptions, configuration baselines with monitoring output, and security test reports with remediation tracking.
7.8 Network security
0 of 5 answered
Evidence an auditor typically expects: A current network diagram, firewall rule sets and their review records, quarterly scan reports, the annual penetration test report with tester qualifications, and remediation tracking.
7.9 Vulnerabilities and Incident management
7.9.1 Monitoring and logging
0 of 5 answered
Evidence an auditor typically expects: The logging and monitoring procedure, the list of logged assets, SIEM or log platform configuration and alert rules, log review records, time synchronisation settings and retention settings.
7.9.2 Incident response
0 of 5 answered
Evidence an auditor typically expects: The incident handling policy, response manuals, escalation charts and contact lists, incident records, the vulnerability register showing dates of discovery and treatment, and reports from incident response exercises.
7.9.3 Reporting
0 of 4 answered
Evidence an auditor typically expects: The notification procedure with authority contact details and templates, records of past notifications, the reporting channel as published to customers, and your incident classification criteria.
7.9.4 Event assessment and classification
0 of 3 answered
Evidence an auditor typically expects: The triage criteria, event and incident tickets showing classification and any reclassification, and the quarterly recurring-incident review.
7.9.5 Post-incident reviews
0 of 3 answered
Evidence an auditor typically expects: Vulnerability advisories you subscribe to and the resulting assessments, post-incident review reports, and the actions they triggered in the risk treatment plan.
7.10 Collection of evidence
0 of 4 answered
Evidence an auditor typically expects: The records retention schedule, archive configuration (write-once storage, off-site copies), a sample retrieval of an archived record, and time-source configuration with synchronisation logs.
7.11 Business continuity management
7.11.1 General
0 of 3 answered
Evidence an auditor typically expects: The business impact analysis, the continuity and disaster recovery plans (including the key-compromise scenario), redundancy design, and test reports with follow-up actions.
7.11.2 Back up
0 of 4 answered
Evidence an auditor typically expects: The backup plan, backup job reports, integrity check logs, off-site storage arrangements and dated restore test reports.
7.11.3 Crisis management
0 of 4 answered
Evidence an auditor typically expects: The crisis management plan, the crisis team contact list, records showing how CSIRT advisories were handled, and reports from crisis exercises.
7.12 TSP termination and termination plans
0 of 5 answered
Evidence an auditor typically expects: The termination plan with its last review date, the agreement with the party that takes over records, the financial arrangement (escrow, insurance or guarantee), and the termination section of the practice statement.
7.13 Compliance
0 of 4 answered
Evidence an auditor typically expects: A legal requirements register, accessibility statement or assessment, GDPR records (processing register, DPIAs, processor agreements) and periodic compliance reports to management.
7.14 Supply chain
7.14.1 Supply chain policy
0 of 3 answered
Evidence an auditor typically expects: The supply chain security policy, supplier selection records showing the criteria applied, supplier performance and incident reviews, and the policy review history.
7.14.2 Supply chain procedures and processes
0 of 5 answered
Evidence an auditor typically expects: Procurement security requirements, supplier documentation such as software bills of materials and hardening guides, acceptance test records, the list of critical components with support dates, and the cloud usage policy.
7.14.3 Responsibility, third parties agreements and SLA
0 of 5 answered
Evidence an auditor typically expects: Supplier contracts and service level agreements with their security clauses, the supplier register, supplier audit reports or certifications, and annual supplier review records.
Gaps to close
Questions answered Not met come first, then Partly, each in clause order.
Nothing here yet. Questions you answer Not met or Partly are listed here.
Want a second pair of eyes on the gaps before the conformity assessment body arrives? MI Support IT provides PKI consulting for trust service providers — audit preparation, CP/CPS documentation and key ceremonies.
How to use the result
Where EN 319 401 sits
It covers what every trust service has in common: risk management, policies, people, access control, operations, incidents, continuity, termination and suppliers. What is specific to issuing certificates or time-stamps lives in the service standards that build on it. Annexes A to C of the standard map its clauses to DORA, eIDAS and the NIS2 implementing regulation (EU) 2024/2690.
Answer from evidence
An auditor does not accept "we do that". Choose Met only when you could put the document or record on the table today, Partly when the practice exists but is undocumented or incomplete, and use the note to record where the evidence lives.
Closing documentation gaps
Two common gaps are a practice statement that no longer matches operations and missing key ceremony records. The CPS Builder gives you a structured draft for the first, and the Key Ceremony Planner a script with sign-off sheets for the second.
Related tools
- CPS Builder — draft the practice statement that clause 6.1 asks for
- Key Ceremony Planner — script the key generation ceremony behind your cryptographic controls
Privacy: Your answers and notes are stored only in your browser's local storage and are never sent to us. Read our privacy policy.