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

2023-08-10 Minutes of the Code Signing Certificate Working Group

Attendees: Abhishek Bhat (eMudhra), Andrea Holland (VikingCloud), Ben Dewberry (Keyfactor), Brianca Martin (Amazon), Corey Bonnell (DigiCert), Dean Coclin (DigiCert), Ian McMillan (Microsoft), Inaba Atsushi (GlobalSign), Martijn Katerbarg (Sectigo), Mohit Kumar (GlobalSign), Rollin Yu (TrustAsia Technologies, Inc.), Scott Rea (eMudhra), Tim Hollebeek (DigiCert), Tomas Gustavsson (PrimeKey)

Note Well: The Note Well was read.

Approval of Minutes: July 27th minutes are approved.

Interested Party application: Waiting on news from Adobe regarding their application.

Ballot Status:

Incorporating BR references
Ballot has passed and is now in IPR review period.
Signing Service
Bruce is out this week as such there’s no update on this ballot.
Timestamping changes ballot
Ian and Bruce are working on this language. Language needs to be tweaked with some additional clarifications
Ian poses the question if we need to specify how audit criteria around key destruction should be collected. Corey mentioned he believes there’s already guidance available for auditors on the WebTrust front.

Presentation on Certificate Transparency

Tim Hollebeek ran a presentation on CT for Code Signing. Slides of this presentation are attached to these minutes.

Gather information for a Lessons Learned after hardware requirement changes

Ben mentioned an issue that was noticed signing Office Macros. Ian will look into it as it appears to be a Microsoft restriction

Any Other Business

Next Meeting

August 24th

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