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
SC099: Improve Recording of Validation Methods - May 19, 2026

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.14 - Ballot SMC016 - May 5, 2026

This ballot maintains consistency between the S/MIME Baseline Requirements and the TLS Baseline Requirements with changes introduced by Ballots SC096 and SC097. Specifically, this ballot: Creates a carve-out of the logging requirements for DNSSEC specifically, stating these are not in scope. For audit purposes, change management logging is able to confirm if the appropriate controls are in effect or not. Sunsets all remaining use of SHA-1 signatures in Certificates and CRLs. It is noted that most uses of SHA-1 signatures are already deprecated by SC097. With this ballot, all unexpired Subordinate CA Certificates issuing S/MIME containing the SHA-1 signature algorithm must be revoked. This proposal does not prohibit the use of SHA-1 to generate issuerKeyHash or issuerNameHash values as currently required by RFC 5019. Includes minor formatting corrections.

Unable to retrieve latest release information from the netsec repository.