CA/Browser Forum
Home » All CA/Browser Forum Posts » 2025-12-11 Minutes of the Code Signing Certificate Working Group

2025-12-11 Minutes of the Code Signing Certificate Working Group

Code Signing Working Group – Meeting Minutes

Date: 11 December

1. Antitrust Reminder (Note Well)

The Note Well was read

2. Review of Agenda

3. Approval of Minutes

November 13th Meeting Minutes were approved Face-to-Face (F2F) Meeting Minutes were approved

4. Discussion Topics

4.1 SC-Alignment Ballot – Microsoft OCSP Concerns

  • No Microsoft representatives were present on the call.
  • No updates were observed on the mailing list regarding Microsoft’s OCSP-related concerns.
  • Topic tabled until Microsoft provides an update.

4.2 Post-Quantum Cryptography (PQC)

  • The topic remains on the agenda at the request of Brianca (Amazon)
  • Discussion noted that progress is largely dependent on Microsoft’s platform direction and support.

4.3 Code Signing – Next Steps (Single Profile)

  • Identified consolidation into a single code signing profile (merging Code Signing and EV Code Signing) as a major project for the coming year.
  • A working branch tracking proposed updates to the Code Signing Baseline Requirements (CSBRs) has been created
  • Rewrite and review CSBR sections incrementally (approximately one section per month).

5. Any Other Business

None

6. Adjourn

7. Next Meeting

Date: 8 January

Attendees

Brian Winters (IdenTrust), Inaba Atsushi (GlobalSign), Iñigo Barreira (Sectigo), Martijn Katerbarg (Sectigo), Nome Huang (TrustAsia), Scott Rea (eMudhra), Thomas Zermeno (SSL.com), 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).