---
title: "How should relying parties use trusted lists under ETSI EN 319 411-2?"
canonical_url: "https://www.sorena.io/artifacts/global/etsi-en-319-411-2/faq/trusted-lists"
source_url: "https://www.sorena.io/artifacts/global/etsi-en-319-411-2/faq/trusted-lists"
author: "Sorena AI"
description: "FAQ on EN 319 411-2 trusted-list reliance for EU qualified certificates: relying-party notices, QTSP service identifiers, validation evidence, and source references."
published_at: "2026-05-09"
updated_at: "2026-05-27"
keywords:
  - "ETSI EN 319 411-2"
  - "trusted lists"
  - "EU trusted list"
  - "QTSP"
  - "relying party notice"
  - "EU qualified certificate"
  - "EU qualified certificates"
  - "Relying parties"
  - "FAQ"
---
**[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)

---

# How should relying parties use trusted lists under ETSI EN 319 411-2?

FAQ on EN 319 411-2 trusted-list reliance for EU qualified certificates: relying-party notices, QTSP service identifiers, validation evidence, and source references.

*Artifact Guide* *GLOBAL* *ETSI EN 319 411-2*

## ETSI EN 319 411-2 Trusted-list reliance FAQ

A direct answer to what EN 319 411-2 expects a QTSP to tell relying parties about EU trusted lists and qualified-certificate validation.

Use this page to review relying-party notices, CP/CPS language, validation procedures, and trusted-list evidence before making an EU qualified-certificate reliance claim.

Under ETSI EN 319 411-2, a relying-party notice for an EU qualified certificate must point relying parties to the trust anchor identified by the service digital identifier in the appropriate EU trusted-list entry for the qualified trust service provider.

## What does EN 319 411-2 require for trusted-list reliance?

ETSI EN 319 411-2 does not treat a trusted list as a loose background reference. In the notice to relying parties, the TSP must explain that, as one condition for relying on the certificate as an EU Qualified Certificate, the validation trust anchor is the service digital identifier in the appropriate EU trusted-list entry for the QTSP.

That means the public reliance message should name the trusted-list dependency clearly. A certificate policy OID, CA certificate, repository page, or marketing statement is not enough by itself if the question is whether the certificate can be relied on as an EU qualified certificate.

- Put the trusted-list condition in the relying-party notice or the terms and conditions referenced by that notice.
- Tie the claim to the QTSP and qualified trust service entry, not only to a generic provider name or certificate chain.
- Keep the certificate policy identifier visible because EN 319 411-2 says policy identifiers help relying parties assess suitability and trustworthiness under eIDAS.

Sources for this answer:

- [ETSI EN 319 411-2 V2.6.1 relying-party trusted-list notice](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - OVR-6.3.5-12 requires the notice to relying parties to identify the EU trusted-list service digital identifier used as the trust anchor for validating an EU qualified certificate.
- [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, QTSP status, and qualified trust services.

## What should a QTSP publish or retain for relying parties?

The practical evidence set should show that relying parties were told how qualified-certificate reliance depends on the relevant EU trusted-list entry. Keep the public notice text, the CP/CPS or terms section it points to, and a mapping from the certificate service to the trusted-list service digital identifier.

For operational review, retain a dated validation record showing the trusted-list source checked, the QTSP name, the service identifier, the service status considered, the certificate profile or policy OID, and the validation procedure used. This is evidence of the reliance process, not a substitute for the formal trusted list itself.

- Relying-party notice: the exact wording that explains the EU trusted-list trust anchor condition.
- Service mapping: QTSP, qualified trust service, service digital identifier, certificate profile, and policy OID.
- Validation record: trusted-list source, date checked, result, reviewer or system owner, and exception handling if the entry or status changes.
- Change trigger: recheck after trusted-list updates, QTSP service-status changes, CP/CPS changes, certificate-profile changes, or validation failures.

Sources for this answer:

- [ETSI EN 319 411-2 V2.6.1 trusted-list validation references](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - The notes below OVR-6.3.5-12 reference Implementing Decision 2015/1505 for trusted-list formats and ETSI TS 119 615 for validating a certificate against EU trusted lists.
- [Commission Implementing Decision (EU) 2015/1505 on trusted-list specifications](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32015D1505&ref=sorena.io) - Official EU source for the technical specifications and formats for trusted lists under Article 22(5) of eIDAS.

## How should validation teams use trusted-list standards?

Use EN 319 411-2 to identify the relying-party notice obligation, then use the trusted-list standards it references for the validation method. ETSI TS 119 612 is referenced for the trusted-list service digital identifier; ETSI TS 119 615 is referenced for procedures for using and interpreting EU Member State national trusted lists.

If the validation question is about whether a signature or seal qualifies, keep that separate from merely checking a certificate. EN 319 411-2 points to ETSI TS 119 172-4 for a signature validation policy that describes validation against EU trusted lists for European qualified electronic signatures or seals.

- Use TS 119 612 terminology when documenting the service digital identifier and trusted-list entry.
- Use TS 119 615-aligned procedures when deciding whether a certificate can be considered an EU qualified certificate from trusted-list data.
- Use TS 119 172-4-aligned validation policy evidence when the relying-party outcome concerns a qualified electronic signature or seal.

Sources for this answer:

- [ETSI TS 119 612 V2.4.1 trusted lists](https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.04.01_60/ts_119612v020401p.pdf?ref=sorena.io) - Referenced by EN 319 411-2 for the service digital identifier of the appropriate EU trusted-list entry.
- [ETSI TS 119 615 V1.2.1 trusted-list procedures](https://www.etsi.org/deliver/etsi_ts/119600_119699/119615/01.02.01_60/ts_119615v010201p.pdf?ref=sorena.io) - Referenced by EN 319 411-2 as guidance for validating a digital certificate against EU trusted lists.
- [ETSI EN 319 411-2 V2.6.1 signature and seal validation reference](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - EN 319 411-2 references ETSI TS 119 172-4 for validation policy when determining whether a signature or seal can be considered qualified using EU trusted lists.

## Primary sources

- [ETSI EN 319 411-2 V2.6.1 relying-party trusted-list notice](https://www.etsi.org/deliver/etsi_en/319400_319499/31941102/02.06.01_60/en_31941102v020601p.pdf?ref=sorena.io) - Primary source for the EN 319 411-2 relying-party notice obligation, trusted-list trust-anchor rule, and references to ETSI TS 119 612, ETSI TS 119 615, ETSI TS 119 172-4, and Implementing Decision 2015/1505.
  - Quote: "service digital identifier of an appropriate EU trusted list entry"
- [ETSI TS 119 612 V2.4.1 trusted lists](https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.04.01_60/ts_119612v020401p.pdf?ref=sorena.io) - Source for trusted-list terminology and the service digital identifier referenced by EN 319 411-2.
  - Quote: "Trusted Lists"
- [ETSI TS 119 615 V1.2.1 trusted-list procedures](https://www.etsi.org/deliver/etsi_ts/119600_119699/119615/01.02.01_60/ts_119615v010201p.pdf?ref=sorena.io) - Source for procedures for using and interpreting EU Member State national trusted lists during certificate validation.
  - Quote: "Procedures for using and interpreting European Union Member States national trusted lists"
- [Commission Implementing Decision (EU) 2015/1505 on trusted-list specifications](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32015D1505&ref=sorena.io) - Official EU source for the technical specifications and formats for trusted lists under Article 22(5) of eIDAS.
  - Quote: "technical specifications and formats relating to trusted lists"
- [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, QTSP status, and qualified trust services.
  - Quote: "electronic identification and trust services"

## 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 QTSP supervision evidence workflow](/artifacts/global/etsi-en-319-411-2/qtsp-supervision-evidence-workflow.md): 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.
- [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.
- [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.

*Recommended next step*

*Placement: after FAQ evidence*

## Map the relying-party notice to the QTSP trusted-list entry

Use this answer to verify that each EN 319 411-2 qualified-certificate route has clear relying-party notice text, a trusted-list service identifier, a validation procedure, and an owner for status-change reviews.

- [Turn reliance into controls](/solutions/assessment.md): Convert trusted-list reliance checks into accountable notices, service mappings, validation records, and review triggers.
- [Research a validation edge case](/solutions/research-copilot.md): Use cited research support when the QTSP entry, service status, or signature validation policy is unclear.
- [Talk through implementation](/contact.md): Review relying-party notices, trusted-list evidence, and the next EN 319 411-2 compliance actions with Sorena.


---

[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/faq/trusted-lists