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

2026-01-08 Minutes of the Code Signing Certificate Working Group

Code Signing Working Group – Meeting Minutes

Date: 8 January 2026

1. Antitrust Reminder (Note Well)

The Note Well was read

2. Review of Agenda

  • An additional item was added: Interested Party Application.

3. Discussion Topics

Interested Party Application

  • An application was received from Digital Berry, a CLM and token management system provider based in France.
  • Dean confirmed the application was complete and properly signed by a senior representative.
  • No objections were raised by the working group.

SC-Alignment Ballot – Microsoft OCSP Concerns

  • No representatives from Microsoft were present.
  • No updates had been received via the mailing list.
  • Given the lack of new information, this topic was skipped.

Post-Quantum Cryptography (PQC)

  • Brianca (Amazon) confirmed there were no updates on PQC.
  • Microsoft was not present to provide any platform-related updates.

Migration to a Single Code Signing Profile

  • The Chair presented initial work toward migrating to a single code signing profile, merging Code Signing and EV Code Signing.
  • Work has begun on Sections 1 and 2 of the Code Signing Baseline Requirements (CSBRs), using a branch-based workflow rather than a formal PR at this stage.
  • Key points discussed:
    • Likely need to move to a new major version (e.g., v4.0).
    • Proposal to allow the existing requirements until a TBD cutoff date, after which only the single profile would be permitted.
    • Maintaining both old and new requirements in one document was viewed as impractical.
    • Proposal to deprecate the EV Code Signing policy OID and move to a single OID.
    • Most changes so far are structural (removal of EV references, minor corrections).
    • Significant concern was raised about proceeding without active Microsoft participation:
    • Microsoft is currently the primary consumer of code signing certificates.
    • Risk of misalignment with Microsoft expectations, similar to prior issues (e.g., OCSP requirements).
    • Consensus that meaningful progress requires Microsoft engagement.

4. Any Other Business

  • It was noted that Microsoft representatives have been absent for three consecutive meetings.
  • It was agreed that Microsoft should be reminded of the purpose of the working group and the importance of their participation.

5. Adjourn

6. Next Meeting

Date: 5 February 2026

Attendees

Brianca Martin (Amazon), Brian Winters (IdenTrust), Corey Bonnell (DigiCert), Dean Coclin (DigiCert), Inaba Atsushi (GlobalSign), Iñigo Barreira (Sectigo), Marco Schambach (IdenTrust), Martijn Katerbarg (Sectigo), Nome Huang (TrustAsia), 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).