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

2024-05-16 Minutes of the Code Signing Certificate Working Group

Attendees

Atsushi INABA - GlobalSign, Ben Dewberry -Keyfactor, Brian Winters - IdenTrust, Brianca Martin - Amazon, Bruce Morton - Entrust, Corey Bonnell-Digicert, Dean Coclin-DigiCert, Dimitris Zacharopoulos - HARICA, Martijn Katerbarg - Sectigo, Mohit Kumar - GlobalSign, Richard Kisley (Guest), Scott Rea - eMudhra

Minutes

Antitrust statement was read.
Meeting Minutes of 2nd-May-24 approved.

Following Ballots were discussed.

Removing EV Guidelines References: Dimitris removed the Organization Identifier requirements from the updates that had objection from the group. There was alignment on using EV Codesigning certificates vs EV Certificates. Updates to be made by Dimitris. Ballot Process can be started if no further comments and looks right.
CSC - 23: It was not received publicly so it has not been published. Corey mentioned it is required step. Bruce will send it to Public list so Corey can take from there for publication.
CSC-24: Time-stamp Requirements update No further comments from anyone. Voting will be started.

Proposal for PCI-HSM acceptance for CA HSMs evaluation by R.Kisley was discussed

Kisley mentioned that:-

PCI has high level assurance requirements
FIPS program has long queue so good to have other option
PCI Version 4 is proposed as PCI version 3 is going to expire in 2026

So request is to add PCI HSM as an alternative criteria to FIPS. Bruce mentioned that need to understand if it will be accepted by Root programs. Dimitris mentioned that Certification of standard is also important. Richard Kisley to reach out to Microsoft/raise this in F2F.

F2F Agenda was discussed and following topics identified for discussion:

Maximum Certificate Validity period for Codesigning certificates
EV Codesigning changes by Microsoft, dependent usecases on EV and future direction
Problem of change in Subject DN for publishers impacting continuity of upgrades and Use of Subject Organization specific EKU
CT Logging
Need for Organization Identifier for Codesigning certificates Dean to share the list ahead to Ian.

Membership of Encryption Consulting, okay to join as interested party.

No objections raised

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