Home » About the CA/Browser Forum » Information » Auditors and Assessors » ETSI

ETSI – European Telecommunications Standards Institute

Current Standards (as of Sept. 2020)

For the most current version of ETSI standards, please refer to this site:
https://portal.etsi.org/TB-SiteMap/ESI/Trust-Service-Providers

You can also use the number for that ETSI standard on this search page:
https://www.etsi.org/standards-search

Accreditation

National Accreditation Bodies (NABs)

European Accreditation Members

Accredited Conformity Assessment Bodies (CABs)

ETSI Electronic Signatures and Infrastructure (ESI)

ESI Activities

Specialist Task Forces

Specialist Task Force 457 works on Framework and Coordination Activities – Coordinating the fulfilment of the Rationalised Framework for electronic signature standards across all areas as defined in Phase 1a and in line with mandate M/460, and at executing tasks that requires joint ETSI-CEN activities with regards to the fulfilment of the Rationalised Framework. It also addresses cryptographic suites which overlap with standardisation addressed by both CEN and ETSI.

STF 458 works on Trust Service Providers (TSP) Supporting electronic signatures - To align specifications for TSP supporting electronic signatures with the rationalised framework, addressing any gaps identified in the rationalised framework work plan, and the progression of all the relevant specifications to EN status.

Previous Versions

General Policy Requirements for CAs – EN 319 401 and EN 319 411-1

Data and Record Systems Security – TS 101 533-1

Qualified Certificates – EN 319 411-2 (replaces TS 101 456)

Publicly Trusted Certificates – EN 319 411-3 (replaces TS 102 042)

Extended Validation Certificates – TS 103 090 and TR 101 564

Certificate Profiles – TS 119 412 and EN 319 412

(Replaces TS 101 862 – Qualified certificate profile)

Time Stamping – EN 319 421 (replaces TS 101 861)

CEN is also working on a security Protection Profile (PP) for time-stamping systems.

Trusted Lists – Harmonization of Status Information

Latest releases

Server Certificate Requirements
BRs/2.1.2 SC-080 V3: Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods - Dec 16, 2024

Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contact… (https://github.com/cabforum/servercert/pull/560) Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods” (https://github.com/cabforum/servercert/pull/555)

Code Signing Requirements
v3.8 - Aug 5, 2024

What’s Changed CSC-25: Import EV Guidelines to CS Baseline Requirements by @dzacharo in https://github.com/cabforum/code-signing/pull/38 Full Changelog: https://github.com/cabforum/code-signing/compare/v3.7...v3.8

S/MIME Requirements
v1.0.8 - Ballot SMC010 - Dec 23, 2024

This ballot adopts Multi-Perspective Issuance Corroboration (MPIC) for CAs when conducting Email Domain Control Validation (DCV) and Certification Authority Authorization (CAA) checks for S/MIME Certificates. The Ballot adopts the MPIC implementation consistent with the TLS Baseline Requirements. Acknowledging that some S/MIME CAs with no TLS operations may require additional time to deploy MPIC, the Ballot has a Compliance Date of May 15, 2025. Following that date the implementation timeline described in TLS BR section 3.2.2.9 applies. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Ashish Dhiman (GlobalSign) and Nicolas Lidzborski (Google).

Network and Certificate System Security Requirements
v2.0 - Ballot NS-003 - Jun 26, 2024

Ballot NS-003: Restructure the NCSSRs in https://github.com/cabforum/netsec/pull/35