--- title: "ETSI EN 319 411-2 QTSP supervision evidence workflow" canonical_url: "https://www.sorena.io/artifacts/global/etsi-en-319-411-2/qtsp-supervision-evidence-workflow" source_url: "https://www.sorena.io/artifacts/global/etsi-en-319-411-2/qtsp-supervision-evidence-workflow" author: "Sorena AI" description: "Build an assessment-ready QTSP supervision evidence pack for ETSI EN 319 411-2 qualified certificate services, covering policy identifiers, trusted-list checks, incident records, QSCD evidence, and termination controls." published_at: "2026-05-09" updated_at: "2026-05-09" keywords: - "ETSI EN 319 411-2" - "QTSP supervision evidence" - "qualified certificate policy" - "trusted list" - "QSCD evidence" - "qualified certificates" - "trusted lists" - "QSCD" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # ETSI EN 319 411-2 QTSP supervision evidence workflow Build an assessment-ready QTSP supervision evidence pack for ETSI EN 319 411-2 qualified certificate services, covering policy identifiers, trusted-list checks, incident records, QSCD evidence, and termination controls. *Workflow* *GLOBAL* *ETSI EN 319 411-2* ## ETSI EN 319 411-2 QTSP supervision evidence workflow A workflow for turning EN 319 411-2 qualified certificate obligations into a supervision evidence pack that an assessment lead, compliance owner, or supervisory-body liaison can review. Use it to organize operational evidence; it is supporting implementation planning and should be validated against jurisdiction-specific legal, contractual, and policy requirements before implementation and does not prove qualified status by itself. Use this workflow when a qualified trust service provider needs to show how an EU qualified certificate service is controlled, monitored, and ready for assessment or supervisory follow-up. The page focuses on evidence that EN 319 411-2 actually supports: qualified certificate policy identifiers, CP/CPS and disclosure material, inherited EN 319 411-1 controls, QSCD checks, trusted-list reliance, incident escalation, status services, record retention, and termination planning. ## 1. Start the evidence pack with the qualified service boundary Open one evidence pack per qualified certificate service, not one pack for an entire PKI estate. Name the issuing qualified TSP, CA or RA components in scope, certificate policy identifier, CP and CPS versions, PKI disclosure statement, subscriber terms, repository location, and certificate population covered by the review. EN 319 411-2 defines qualified certificate policies for natural persons, legal persons, QSCD-backed certificates, and qualified website authentication certificates. The supervision file should therefore show exactly which profile is claimed and which EN 319 411-1 baseline controls are inherited. - Input: service name, issuing TSP, CA hierarchy, RA route, repository URL, CP/CPS versions, terms and conditions, and assessment period. - Profile field: QCP-n, QCP-l, QCP-n-qscd, QCP-l-qscd, QEVCP-w, QNCP-w, or QNCP-w-gen. - Boundary rule: keep non-qualified certificate evidence separate unless the pack identifies the inherited EN 319 411-1 requirement being reused. - Output: a scoped supervision evidence index with owner, source clause, evidence artifact, last review result, and open gaps. Sources for this answer: - [ETSI EN 319 411-2 V2.6.1 qualified certificate requirements](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - Supports the page scope, qualified certificate policy identifiers, and the need to tie evidence to a specific EU qualified certificate service. - [ETSI EN 319 411-1 V1.5.1 general certificate requirements](https://www.etsi.org/deliver/etsi_en/319400_319499/31941101/01.05.01_60/en_31941101v010501p.pdf?ref=sorena.io) - Supports inherited certificate-service evidence for CP/CPS, subscribers, repositories, revocation, records, and assessment preparation. *Recommended next step* *Placement: after practical guidance* ## Operationalize the EN 319 411-2 evidence workflow Use the workflow to assign certificate policy, trusted-list, QSCD, incident, status-service, termination, and assessment evidence before assessor or supervisory review. - [Open Assessment Autopilot for ETSI EN 319 411-2](/solutions/assessment.md): Convert QTSP supervision evidence into accountable tasks, evidence requests, and assessment-ready records. - [Research ETSI EN 319 411-2 source questions](/solutions/research-copilot.md): Resolve policy, QSCD, incident, trusted-list, status-service, or termination questions against cited ETSI material. - [Talk through QTSP evidence gaps](/contact.md): Review EN 319 411-2 supervision evidence, owners, unresolved gaps, and next actions with Sorena. ## 2. Triage supervision triggers before the evidence pack changes Use a trigger log so changes do not disappear into policy edits. A trigger should be opened when the qualified certificate service changes, when the QSCD route changes, when a trusted-list or status-service dependency changes, when a breach or loss of integrity may affect the service, when termination is planned, or when an assessor raises a finding. The log should separate three decisions: whether the CP/CPS or disclosure material must be updated, whether assessment evidence must be refreshed, and whether the supervisory-body liaison needs to review the event. When national filing details are not present in the source material, record that as a local compliance action instead of inventing a public rule. - Change trigger: new policy identifier, certificate profile, CA hierarchy, RA process, repository practice, subscriber terms, or relying-party notice. - QSCD trigger: new QSCD supplier, third-party TSP involvement, device status change, or missing proof that the certified public key came from a QSCD-generated key pair. - Operational trigger: breach or loss of integrity, revocation or status-service issue, last-CRL or beyond-validity status gap, or planned termination. - Output: trigger record with owner, affected policy, source clause, evidence to refresh, external action needed, and release decision. Sources for this answer: - [ETSI EN 319 401 V3.1.1 general policy requirements for TSPs](https://www.etsi.org/deliver/etsi_en/319400_319499/319401/03.01.01_60/en_319401v030101p.pdf?ref=sorena.io) - Supports escalation for changes in qualified trust-service provision, communications to supervisory or regulatory bodies, incident reporting, and termination notifications. - [ETSI EN 319 411-2 V2.6.1 qualified certificate requirements](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - Supports QSCD-status monitoring, qualified certificate policy selection, trusted-list reliance, and qualified certificate life-cycle evidence. ## 3. Build row-level evidence for the supervision file Treat the supervision pack as a row-level evidence register. Each row should name the claim, source requirement, evidence artifact, owner, review result, and assessor or supervisory relevance. This prevents a CP/CPS statement such as 'qualified certificate' from standing alone without the policy identifier, trusted-list evidence, QSCD route, or status-service proof behind it. A useful register has enough detail to be reviewed without opening internal systems first. For example, a QSCD-backed QCP-n-qscd row should point to the QSCD certification evidence, key-pair generation evidence, certificate request control, CPS measure for QSCD status changes, and the certificate qcStatement evidence where relevant. - Policy row: policy identifier, subject type, baseline inherited from EN 319 411-1, CP/CPS section, terms and conditions, and approval date. - Identity row: natural-person, legal-person, or website-authentication route; verification method; RA evidence; and exception handling. - QSCD row: device certification evidence, third-party TSP qualification check where applicable, public-key origin proof, status monitoring, and CPS response measure. - Trusted-list row: service digital identifier, QTSP entry, relying-party notice, validation date, and owner of follow-up when the entry changes. - Status-service row: certificate database, revocation publication evidence, CRL or OCSP availability, beyond-validity handling, and expired-certificate status evidence. Sources for this answer: - [ETSI EN 319 411-2 V2.6.1 qualified certificate requirements](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - Supports the evidence rows for policy identifiers, identity proofing, QSCD checks, trusted-list reliance, status services, and records concerning EU qualified certificates. ## 4. Preserve incident, record-retention, and termination evidence Supervision evidence should include more than normal certificate issuance records. EN 319 411-2 maps eIDAS incident, record-accessibility, certificate-database, revocation, status-information, and termination requirements to standard clauses, while warning that its Annex A is informative and not a definitive legal conformance statement. For incidents, keep the awareness time, affected service, certificate population, integrity impact, personal-data impact, notification assessment, sent notices, containment result, and post-incident control changes. For retention and termination, keep evidence that information remains accessible beyond service termination, that the certificate database is kept updated, and that continuity planning has an accountable owner. - Incident evidence: event timeline, significant-impact assessment, 24-hour supervisory notification assessment, affected-person notice decision, and remediation owner. - Retention evidence: archive index for data issued and received by the QTSP, legal-proceeding evidence path, and continuity-of-service access path. - Termination evidence: up-to-date termination plan, subscriber and relying-party communication plan, last-status-service handling, and supervisory-body verification point. - Caveat: do not present EN 319 411-2 Annex A as complete eIDAS legal conformance; record legal or national-law questions separately. Sources for this answer: - [ETSI EN 319 411-2 V2.6.1 eIDAS mapping annex](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - Supports the incident, retention, certificate database, revocation, status-service, termination, and Annex A limitation checks used in this workflow. - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj/eng?ref=sorena.io) - Legal framework referenced by EN 319 411-2 for qualified trust service providers, supervisory notification, records, revocation, and qualified certificate context. ## 5. Close the workflow with assessor-ready outputs Close the workflow only when each open trigger has a decision and each material claim has evidence. The closeout should be short enough for an assessment lead to use, but specific enough to show which requirement, certificate policy, evidence artifact, and owner support each claim. EN 319 411-2 references ETSI TR 119 411-4 as a checklist supporting audit of TSPs against EN 319 411-1 or EN 319 411-2. Keep requirement identifiers visible in the evidence register so the assessor can trace from the finding back to the CP/CPS, repository, log, certificate record, or change decision. - Closeout field: service boundary, policy identifier, CP/CPS version, repository evidence, trusted-list evidence, and assessment period. - Closeout field: trigger type, source clause or requirement identifier, evidence artifact, owner, review result, and unresolved gap. - Closeout field: required external action, such as supervisory-body liaison review, conformity-assessment follow-up, subscriber notice, relying-party notice, or CP/CPS publication update. - Stop condition: the pack cannot show the qualified profile, trusted-list basis, QSCD basis where claimed, status-service basis, or owner for a material open gap. Sources for this answer: - [ETSI EN 319 411-2 V2.6.1 qualified certificate requirements](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - Supports preserving EN 319 411-2 requirement identifiers and the referenced audit-checklist approach when preparing assessment evidence. - [ETSI EN 319 401 V3.1.1 general policy requirements for TSPs](https://www.etsi.org/deliver/etsi_en/319400_319499/319401/03.01.01_60/en_319401v030101p.pdf?ref=sorena.io) - Supports closeout fields for trust-service governance, security-policy communication, incident reporting, and termination-related responsibilities. ## Primary sources - [ETSI EN 319 411-2 V2.6.1 qualified certificate requirements](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - Primary source for EN 319 411-2 qualified certificate policy identifiers, QSCD evidence, trusted-list reliance, status-service continuity, eIDAS mapping, and assessment-preparation references. - Quote: "Requirements for trust service providers issuing EU qualified certificates" - [ETSI EN 319 411-1 V1.5.1 general certificate requirements](https://www.etsi.org/deliver/etsi_en/319400_319499/31941101/01.05.01_60/en_31941101v010501p.pdf?ref=sorena.io) - Supports inherited certificate-service controls for CP/CPS, subscriber and subject handling, repositories, revocation, records archival, and conformity assessment preparation. - Quote: "Policy and security requirements for Trust Service Providers issuing certificates" - [ETSI EN 319 401 V3.1.1 general policy requirements for TSPs](https://www.etsi.org/deliver/etsi_en/319400_319499/319401/03.01.01_60/en_319401v030101p.pdf?ref=sorena.io) - Supports supervisory-change escalation, TSP incident reporting, security-policy communication, and termination notification evidence. - Quote: "supervisory or other regulatory bodies" - [Regulation (EU) No 910/2014 (eIDAS)](https://eur-lex.europa.eu/eli/reg/2014/910/oj/eng?ref=sorena.io) - Legal framework referenced by EN 319 411-2 for EU qualified certificates, qualified trust services, supervisory notification, records, revocation, and status information. - Quote: "electronic identification and trust services" ## Related Topic Guides - [eIDAS QTSP supervision workflow for ETSI EN 319 411-2](/artifacts/global/etsi-en-319-411-2/eidas-qtsp-supervision-workflow.md): Operational workflow for qualified trust service providers using ETSI EN 319 411-2 to manage supervisory-body changes, incidents, termination evidence, trusted-list checks, and assessment records. - [EN 319 411-2 vs EN 319 411-1 Qualified Certs](/artifacts/global/etsi-en-319-411-2/en-319-411-2-vs-en-319-411-1.md): Compare ETSI EN 319 411-2 qualified certificate requirements with EN 319 411-1 general certificate-service requirements, including QCP profiles, QSCD evidence, CP/CPS reuse, and audit boundaries. - [ETSI EN 319 411-2 compliance checklist](/artifacts/global/etsi-en-319-411-2/compliance.md): Compliance checklist for ETSI EN 319 411-2 qualified certificate services, covering policy selection, CP/CPS evidence, identity validation, QSCD status, trusted-list reliance, and certificate status services. - [ETSI EN 319 411-2 FAQ for EU Qualified Certificates](/artifacts/global/etsi-en-319-411-2/faq.md): Answers to common ETSI EN 319 411-2 questions about EU qualified certificate policies, QSCD use, identity validation, trusted lists, and revocation status services. - [ETSI EN 319 411-2 Identity Proofing](/artifacts/global/etsi-en-319-411-2/identity-proofing.md): How EN 319 411-2 applies identity validation for EU qualified certificates, including QCP natural-person, legal-person, website, and evidence-record checks. - [ETSI EN 319 411-2 QSCD Route](/artifacts/global/etsi-en-319-411-2/qscd-route.md): When QCP-n-qscd or QCP-l-qscd is the right EN 319 411-2 route, what QSCD evidence is needed, and which certificate-profile claims must stay aligned. - [ETSI EN 319 411-2 qualified certificate operations: issuance, suspension, and revocation](/artifacts/global/etsi-en-319-411-2/qualified-certificate-operations.md): Operational guide for ETSI EN 319 411-2 qualified certificate services: policy identifiers, identity validation, issuance, QSCD handling, revocation status, and relying-party notices. - [ETSI EN 319 411-2 Qualified Certificate Scope](/artifacts/global/etsi-en-319-411-2/qualified-certificate-scope.md): Use ETSI EN 319 411-2 to scope EU qualified certificate services by certificate policy, subject type, QSCD use, website authentication profile, and eIDAS context. - [ETSI EN 319 411-2 requirements map](/artifacts/global/etsi-en-319-411-2/requirements.md): Map ETSI EN 319 411-2 requirements for EU qualified certificate services across QCP profiles, CP/CPS documentation, QSCD use, certificate profiles, revocation, and eIDAS Annex A references. - [ETSI EN 319 411-2 trusted-list evidence](/artifacts/global/etsi-en-319-411-2/trusted-list-evidence.md): Build EN 319 411-2 trusted-list evidence for EU qualified certificate reliance: relying-party notice text, QTSP service identifiers, validation records, and change triggers. - [ETSI EN 319 411-2 trusted-list validation workflow](/artifacts/global/etsi-en-319-411-2/trusted-list-validation-workflow.md): Validate an EN 319 411-2 EU qualified-certificate claim by mapping the certificate service to the QTSP trusted-list entry, policy profile, relying-party notice, and status evidence. - [ETSI EN 319 411-2 vs eIDAS Qualified Trust Services](/artifacts/global/etsi-en-319-411-2/en-319-411-2-vs-eidas-qualified-trust-services.md): Compare ETSI EN 319 411-2 certificate policy requirements with the eIDAS qualified-status, supervision, audit, and trusted-list framework. - [ETSI EN 319 411-2: Certificate Revocation FAQ](/artifacts/global/etsi-en-319-411-2/faq/revocation.md): Answer the ETSI EN 319 411-2 revocation question for qualified certificate services: CPS procedures, 24-hour publication, CRL or OCSP status, and evidence to retain. - [ETSI EN 319 411-2: end-to-end qualified certificate lifecycle management workflow](/artifacts/global/etsi-en-319-411-2/qualified-certificate-lifecycle-workflow.md): Lifecycle workflow for ETSI EN 319 411-2 qualified certificate services, from policy selection and identity validation through issuance, renewal, re-key, modification, revocation, status services, and records. - [ETSI EN 319 411-2: Legal vs Natural Person Certs](/artifacts/global/etsi-en-319-411-2/faq/legal-and-natural-persons.md): ETSI EN 319 411-2 separates qualified certificate policies for natural persons, legal persons, QSCD use, and website authentication subscribers. - [ETSI EN 319 411-2: QCP, QNCP, and QEVCP Profile Selection](/artifacts/global/etsi-en-319-411-2/qcp-qncp-and-qevcp-profile-selection.md): Choose the right ETSI EN 319 411-2 qualified certificate policy profile: QCP-n, QCP-l, QCP-n-qscd, QCP-l-qscd, QEVCP-w, QNCP-w, or QNCP-w-gen. - [ETSI EN 319 411-2: workflow for selecting QCP-n, QCP-l, or QCP-w certificate profile](/artifacts/global/etsi-en-319-411-2/qualified-profile-selector-workflow.md): Select the right ETSI EN 319 411-2 qualified certificate policy profile for signatures, seals, QSCD use, and website authentication. - [How should QTSPs select an ETSI EN 319 411-2 qualified certificate profile?](/artifacts/global/etsi-en-319-411-2/faq/qualified-profile-selection.md): A focused FAQ on choosing QCP-n, QCP-l, QCP-n-qscd, QCP-l-qscd, QEVCP-w, QNCP-w, or QNCP-w-gen under ETSI EN 319 411-2. - [How should relying parties use trusted lists under ETSI EN 319 411-2?](/artifacts/global/etsi-en-319-411-2/faq/trusted-lists.md): FAQ on EN 319 411-2 trusted-list reliance for EU qualified certificates: relying-party notices, QTSP service identifiers, validation evidence, and source references. - [QSCD Requirements in ETSI EN 319 411-2](/artifacts/global/etsi-en-319-411-2/faq/qscd.md): How ETSI EN 319 411-2 treats QSCD-backed qualified certificates, including QCP-n-qscd and QCP-l-qscd policies, key-use controls, QSCD verification, and certificate profile evidence. - [QTSP Supervision and ETSI EN 319 411-2](/artifacts/global/etsi-en-319-411-2/faq/qtsp-supervision.md): How ETSI EN 319 411-2 supports QTSP supervision evidence for qualified certificate services, trusted-list reliance, liability responsibility, incident records, and audit preparation. - [Qualified certificates under ETSI EN 319 411-2](/artifacts/global/etsi-en-319-411-2/faq/qualified-certificates.md): FAQ answer for QTSPs on how ETSI EN 319 411-2 treats EU qualified certificates, policy identifiers, QSCD variants, website certificates, and lifecycle evidence. - [What are the qualified certificate policies in ETSI EN 319 411-2?](/artifacts/global/etsi-en-319-411-2/faq/qualified-certificate-policies.md): FAQ on ETSI EN 319 411-2 qualified certificate policies, including QCP-n, QCP-l, QSCD variants, QEVCP-w, QNCP-w, and policy identifiers. - [Which QWAC Profile Fits ETSI EN 319 411-2?](/artifacts/global/etsi-en-319-411-2/faq/website-authentication-certificates.md): Choose between QEVCP-w, QNCP-w, and QNCP-w-gen for qualified website authentication certificates under ETSI EN 319 411-2. --- [Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/global/etsi-en-319-411-2/qtsp-supervision-evidence-workflow