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
SC095v3: Clean-up 2025 - Apr 2, 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.

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).