CA/Browser Forum
Home » All CA/Browser Forum Posts » 2026-02-05 Minutes of the Code Signing Certificate Working Group

2026-02-05 Minutes of the Code Signing Certificate Working Group

Code Signing Working Group – Meeting Minutes

Minutes

Tom led the discussion as Martijn was unable to attend.

Tom read the Note Well.

OCSP discussion for Servercert alignment ballot

Karina is discussing internally at Microsoft on how best to proceed. She plans to send an update to the group in the next few days.

Migration to single profile

Tom said sections 1 and 2 of the proposal are available on Github. Tom led the group through the proposal. No concerns were raised on the changes. Corey said it would be good to discuss overall goal before discussing concrete language changes.

Karina said that Microsoft wants more widespread use of code signing but provides strong identity. In particular, the validation should be closer to EV than OV.

Karina said she is working on a ballot that removes phone validation, as methods with durable proof is preferred.

Inigo suggested looking into eIDAS for validation for code signing certificates.

Topics for F2F

Karina said she will send out the proposal for removing phone validation and it can be discussed at the F2F. Corey suggested discussing the single profile at the F2F.

Other business

The group agreed to meet on February 19th to discuss the F2F agenda.

Meeting adjourned. The next meeting will be February 19th.

Attendees

Brian Winters (IdenTrust), Corey Bonnell (DigiCert), Inaba Atsushi (GlobalSign), Iñigo Barreira (Sectigo), Karina Sirota (Microsoft), Luis Cervantes (SSL.com), Marco Schambach (IdenTrust), Nome Huang (TrustAsia), Scott Rea (eMudhra), Thomas Zermeno (SSL.com), Tim Crawford (CPA Canada/WebTrust), Wiktoria Więckowska (Asseco Data Systems SA (Certum))

Latest releases
Server Certificate Requirements
SC098: Process RFC 8657 CAA Parameters - Jun 16, 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.15 - Ballot SMC017v2 - Jul 30, 2026

This ballot increases the minimum RSA key size for Root and Subordinate CA certificates in the S/MIME BRs from 2048 to 4096 bits for keys created after September 15, 2026, while retaining the 2048-bit minimum for Subscriber certificates. The ballot further requires that by September 15, 2027, CAs SHALL NOT issue Subscriber certificates from any Sub-CA whose RSA key modulus is less than 3072 bits, effectively sunsetting issuance from legacy 2048-bit Sub-CAs. The ballot also includes minor typographic corrections. This ballot is proposed by Martijn Katerbarg (Sectigo) and endorsed by Ben Wilson (Mozilla) and Stephen Davidson (DigiCert)

Network and Certificate System Security Requirements
Version 2.0.5 (Ballot NS-008) - Jul 9, 2025

Edit this page
The Certification Authority Browser Forum (CA/Browser Forum) is a voluntary gathering of Certificate Issuers and suppliers of Internet browser software and other applications that use certificates (Certificate Consumers).