FAQGLOBALETSI EN 319 411-1

ETSI EN 319 411-1 Subscriber identity validation for certificate authorities

A focused answer for certification authorities and trust service providers validating subscribers, subjects, representatives, organizations, and device identities before certificate issuance.

Grounded in ETSI EN 319 411-1 and ETSI EN 319 401 source text. Use it as implementation guidance, not for legal interpretation.

Author
Sorena AI
Published
May 9, 2026
Updated
May 27, 2026
Questions
3

Structured answer sets in this page tree.

Primary sources
3

Cited legal and guidance references.

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

Under ETSI EN 319 411-1, the TSP must verify the identity of both the subscriber and the certificate subject before issuance. The validation file should show the subject category, the subscriber-subject relationship, the direct evidence or authorized attestation used, the authorization to request the certificate, and the registration record needed to reconstruct the decision later.

Search this module

Find a question or answer quickly

3 of 3 questions
Question 1

What must be validated before a certificate is issued?

Clause 6.2.2 starts with a direct rule: the TSP verifies the identity of the subscriber and the subject. It then requires the TSP to collect and validate either direct evidence or an attestation from an appropriate and authorized source for the subject's identity and, where applicable, subject attributes.

The validation decision must also cover the certificate request itself. ETSI EN 319 411-1 requires the TSP to check that certificate requests are accurate, authorized, and complete against the collected evidence or attestation. Identity verification happens at registration, and the registration service passes verified identity and attribute results to certificate generation.

  • Identify whether the subject is a natural person, a natural person linked to a legal person, a legal person or organizational entity, or a device or system operated by or for a natural or legal person.
  • Collect direct evidence or an authorized-source attestation for the subject identity and any certificate attributes that will be included or relied on.
  • Check request accuracy, authorization, and completeness before certificate generation uses the registration result.
Citations
Question 2

How does the answer change by subject type?

For natural-person subjects under NCP requirements, ETSI EN 319 411-1 expects identity evidence to be checked against the person directly by physical presence, unless a duly mandated subscriber represents the subject, or indirectly using means that provide equivalent assurance. The evidence set includes the person's full name and either date and place of birth, a recognized identity-document reference, or other distinguishing attributes.

For a natural person associated with a legal person, the file needs both personal and organization evidence: the subject's name and distinguishing attributes, the legal person's full name and legal status, relevant registration information, the affiliation, and approval by both the legal person and natural person that the subject attributes identify the organization. For legal-person and device/system subjects, the evidence shifts to the organization's name, registration or distinguishing attributes, relevant organizational associations, and a device identifier such as an Internet domain name where applicable.

  • Do not use a single identity checklist for every certificate profile; map the requested certificate to the subject type and policy conditions that apply.
  • When the subscriber and subject are different entities, keep evidence that the subscriber is authorized to act for the subject and, if the subscriber is not a natural person, that a natural person is authorized to represent the subscriber.
  • For web certificates, use the domain-name and IP-address verification methods in BRG clauses 3.2.2.4 to 3.2.2.9 for the applicable certificate profile, instead of a generic verification path.
Citations
Regulation (EU) No 910/2014 (eIDAS)

Provides the EU trust-services legal context for certificates and trust service providers where ETSI EN 319 411-1 is used for eIDAS-oriented certification services.

Question 3

What evidence should a CA keep for subscriber identity validation?

The evidence record should be specific enough to re-perform the validation decision without collecting unnecessary long-term personal data. ETSI EN 319 411-1 requires the TSP to record all information necessary to verify the subject identity and attributes, including any reference number on verification documentation and any limits on its validity. The standard notes that long-term retention may be limited to a reference to the document used, depending on the records obligations and applicable law.

The file should also prove process integrity. Keep the request, evidence or attestation source, validation method, certificate profile, subscriber contact attributes, authorization evidence, approval history, and the registration officer or RA record. The registration officer who verifies identity must not be the natural person receiving the certificate as subject.

  • Record the subject type, subscriber-subject relationship, certificate profile, evidence source, validation method, document reference, validity limitations, and request approval.
  • Keep subscriber contact attributes such as a physical address or other contact attributes, plus evidence showing how the registration process meets applicable data-protection legislation.
  • Track registration officer independence, RA involvement, and any delegated evidence source so the CA can show who validated what and under which CPS process.
Citations
Primary sources

References and citations

etsi.org
Referenced sections
  • Supports preserving identity-validation records as controlled trust-service evidence with maintained confidentiality, integrity, availability, and retention appropriate to the service.
"confidentiality and integrity of current and archived records"
etsi.org
Referenced sections
  • Supports the registration evidence requirements for identity records, document references, subscriber contact attributes, data-protection evidence, and registration officer independence.
"record all the information necessary to verify the subject's identity"
eur-lex.europa.eu
Referenced sections
  • Provides the EU trust-services legal context for certificates and trust service providers where ETSI EN 319 411-1 is used for eIDAS-oriented certification services.
"electronic identification and trust services"
Related guides

Explore more topics

CP vs CPS under ETSI EN 319 411-1
Understand how ETSI EN 319 411-1 separates Certificate Policy from Certification Practice Statement work for certification authorities and trust service providers.
EN 319 411-1 vs EN 319 411-2 Certificate Policy
Compare ETSI EN 319 411-1 general certificate-service requirements with EN 319 411-2 EU qualified certificate requirements, including policy scope, CP/CPS evidence, and audit boundaries.
ETSI EN 319 411-1 Audit File Evidence
Build an ETSI EN 319 411-1 audit evidence file for CA logging, registration records, revocation records, CA key lifecycle evidence, and records archival.
ETSI EN 319 411-1 CA Key Management
CA key management guidance for ETSI EN 319 411-1: CPS commitments, key ceremonies, secure cryptographic devices, backup, recovery, and lifecycle evidence.
ETSI EN 319 411-1 certificate lifecycle workflow
Workflow for EN 319 411-1 certificate application, issuance, acceptance, renewal, re-key, modification, revocation, suspension, status services, and evidence records.
ETSI EN 319 411-1 certificate re-key FAQ
What ETSI EN 319 411-1 requires when a TSP re-keys an existing certificate with a new subject public key.
ETSI EN 319 411-1 Certificate Suspension FAQ
How CAs should handle certificate suspension under ETSI EN 319 411-1: CPS disclosure, validated requests, status publication, subscriber notice, and audit evidence.
ETSI EN 319 411-1 Certification Audit Evidence FAQ
How CAs should prepare ETSI EN 319 411-1 audit evidence for CP/CPS scope, registration records, revocation records, CA key logs, and retained assessment files.
ETSI EN 319 411-1 Compliance Guide
Build an ETSI EN 319 411-1 compliance file for certificate policies, CPS commitments, certificate lifecycle controls, revocation services, CA keys, and audit evidence.
ETSI EN 319 411-1 CP and CPS template
Build a certificate policy and Certification Practice Statement template for ETSI EN 319 411-1 certificate services, with fields for policy identifiers, subscribers, relying parties, revocation, publication, and evidence.
ETSI EN 319 411-1 FAQ for Certificate Services
Answers to common ETSI EN 319 411-1 questions on certificate policies, CPS content, CA and RA boundaries, subscriber evidence, revocation, status services, and record retention.
ETSI EN 319 411-1 Identity Validation
Identity validation requirements in ETSI EN 319 411-1 for subscribers, subjects, RAs, certificate requests, registration evidence, and issuance records.
ETSI EN 319 411-1 Identity Validation Evidence Workflow
A workflow for building ETSI EN 319 411-1 identity validation evidence packs across subscriber, subject, certificate request, RA, logging, and retention controls.
ETSI EN 319 411-1 RA Delegation Guide
How to scope registration authority delegation under ETSI EN 319 411-1, including delegated RA tasks, external provider controls, registration records, and audit evidence.
ETSI EN 319 411-1 RA Delegation Review Workflow
Review delegated registration authority work under ETSI EN 319 411-1: retained CA responsibility, recognized registration service providers, secure data exchange, CPS coverage, and audit evidence.
ETSI EN 319 411-1 requirements map for certificate services
Map ETSI EN 319 411-1 requirements for certificate policies, CP/CPS content, registration, revocation, certificate status, and CA key-management evidence.
ETSI EN 319 411-1 Revocation Evidence Workflow
Build a revocation evidence workflow for ETSI EN 319 411-1 covering CPS procedures, request authentication, 24-hour status updates, CRL/OCSP publication, logs, and retention.
ETSI EN 319 411-1 Revocation, OCSP, and CRL Operations
Operate ETSI EN 319 411-1 revocation status services with CPS procedures, authenticated requests, 24-hour CRL or OCSP publication controls, and audit evidence.
ETSI EN 319 411-1 vs CA/B Forum Baseline Requirements
Compare how EN 319 411-1 incorporates CA/B Forum BRG concepts for DVCP, OVCP, IVCP, [WEB] requirements, CPS disclosure, domain validation, and conflict handling.
How should certificate authorities handle revocation evidence under ETSI EN 319 411-1?
What ETSI EN 319 411-1 expects CAs to evidence for certificate revocation requests, status publication, CRL or OCSP updates, and archived revocation records.
RA delegation under ETSI EN 319 411-1
How certificate authorities can delegate registration authority work under ETSI EN 319 411-1 while keeping identity validation, secure data exchange, role controls, and audit evidence traceable.
Subscriber agreements under ETSI EN 319 411-1
How ETSI EN 319 411-1 expects CAs and TSPs to inform subscribers, record acceptance, handle subject consent, and retain subscriber-agreement evidence.