ETSI EN 319 411-2 Trusted-list evidence

Start with the exact reliance claim: a certificate is being presented or used as an EU qualified certificate under an EN 319 411-2 qualified certificate policy. The evidence should connect that claim to the issuing QTSP, the certificate service, the certificate policy identifier, and the trusted-list service digital identifier that relying parties are told to use.

Do not treat a certificate chain, policy OID, CP/CPS statement, or repository page as enough by itself. EN 319 411-2 ties qualified-certificate reliance to the appropriate EU trusted-list entry for the QTSP, while eIDAS supplies the legal framework for qualified trust services and EU trusted lists.

A useful trusted-list evidence record should be reviewable without opening private systems first. It should show the public statement made to relying parties, the trusted-list entry used for that statement, and the validation procedure or source used to interpret the trusted-list data.

Keep this evidence per qualified certificate service or certificate population. A one-time screenshot is weak unless it is paired with the service boundary, date checked, service identifier, profile claim, reviewer or system owner, and the event that would require the check to be refreshed.

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

Keep certificate validation evidence separate from signature or seal validation evidence. EN 319 411-2 points to ETSI TS 119 172-4 for a validation policy describing how to validate a digital signature against EU trusted lists when the outcome is whether it can be considered a qualified electronic signature or seal.

Trusted-list evidence should be refreshed when the fact pattern behind the reliance claim changes. The trigger is not a generic review cadence; it is a change to the certificate service, profile, QTSP status context, trusted-list entry, validation method, or relying-party notice that could alter how the certificate is relied on as qualified.

When a check fails or the trusted-list entry does not match the claim, record the issue as an exception before publishing or reusing the qualified-certificate claim. The exception should identify whether the gap is a standards implementation issue, a trusted-list recognition issue, a CP/CPS publication issue, or a legal or supervisory question outside the standard.