eIDAS & Trust Services

What Is ETSI EN 319 412?

ETSI EN 319 412, "Certificate Profiles", is the European standard that specifies what X.509 certificates issued by trust service providers must contain. It profiles RFC 5280 for the European context in five parts and defines the fields that make a certificate recognisable as qualified under eIDAS. Where ETSI EN 319 411 says how a certificate authority must operate, EN 319 412 says what the certificates look like.

The five parts

Part 1, "Overview and common data structures", introduces the series and defines the identifier formats that the other parts use.

Part 2 is the profile for certificates issued to natural persons, used for electronic signatures. Part 3 is the profile for certificates issued to legal persons, used for electronic seals. Part 4 is the profile for web site certificates and builds on the CA/Browser Forum requirements. Part 5 defines the QCStatements, the declarations that mark a certificate as qualified.

Identifiers that can be parsed

The most visible contribution of Part 1 is a common format for identity numbers, so that software can tell what kind of number it is looking at and which country issued it.

For a natural person, the serialNumber attribute in the subject holds a three-character type, a two-letter country code, a hyphen and the identifier. The types include PAS for a passport number, IDC for a national identity card number, PNO for a national personal number and TIN for a tax identification number.

For a legal person, the organizationIdentifier attribute (OID 2.5.4.97) uses the same pattern with types such as VAT, NTR for a national trade register, LEI and PSD. In both cases two letters followed by a colon indicate a nationally defined scheme. A semantics identifier in the QCStatements extension (OID arc 0.4.0.194121.1) can declare that the certificate follows these rules.

What the profiles constrain

The profiles state which subject attributes must be present, which extensions are required and how they are set. A legal person certificate, for example, must contain the country, the organisation name, the organizationIdentifier and a common name. For natural person certificates used to sign, Part 2 recommends a key usage with only the non-repudiation bit (renamed contentCommitment in X.509), so that a signing key is not also used for authentication or encryption.

Parts 2 to 4 also state which QCStatements and which certificate policy identifiers belong in an EU qualified certificate of each type, tying the profile to Part 5 and to ETSI EN 319 411-2.

Why it matters in practice

If you issue certificates, EN 319 412 is the specification your certificate templates are checked against, and profile deviations are among the easier audit findings to avoid. If you consume certificates, it is the reason you can reliably extract a company registration number or a personal identifier from a European certificate without writing a parser per country.

Try it yourself — free tools

  • Certificate Checker — decode the subject identifiers, QCStatements and policy OIDs that the profiles define
  • CPS Builder — describe your certificate profiles in section 7 of an RFC 3647-structured CPS

How MI Support IT can help

PKI Tools is built by MI Support IT, a Danish IT company with deep specialization in enterprise PKI: ADCS design and health checks, Venafi certificate automation, key ceremonies and CP/CPS documentation. Read about our PKI services or get in touch.

PKI Glossary