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

2022-11-17 Minutes of the Code Signing Certificate Working Group

Attendees

Atsushi Inaba (GobalSign), Bruce Morton (Entrust), Corey Bonnell (DigiCert), Dimitris Zacharopoulos (HARICA), Ian McMillan (Microsoft), Joanna Fox (Trustcor), Martijn Katerberg (Sectigo), Roberto Quinones (Intel), Tim Crawford (BDO), Tomas Gustavsson, Trevoli Ponds-White (Amazon Trust Services)

Minutes

  1. Antitrust statement was read.
  2. Minutes from 25 October are not yet available. Minutes from 3 November were approved.
  3. Ballot: Signing Service Update – The draft text has been recirculated. Dimitris has some comments on the ETSI Time-stamping audit requirements. The Signing Service audit requirements were fine. Discussed allowing a Signing Service to be audited to a SANs standard; this would require more discussion. Ian plans to endorse. Ian would like to address FIPS 140-2 Level 3 requirement date for the Signing Service. Bruce reviewed the NetSec audit requirements and most appear they could apply to a Signing Service, if CA was replaced with Signing Service and other minor adjustments.
  4. Ballot: Malware base revocation – A number of comments have been added and have been addressed. Martijn will push the changes to GitHub and will push the ballot forward in the next few days.
  5. Other business – Dimitris has not received any other feedback on moving away from the SSL BRs. The direction is to try to replace references with text from the SSL BRs. Martijn will plan to put sometime to this over the next week. Bruce stated the plan was also to try to rationalize if the changes do not make sense for Code Signing.
  6. Next Meeting – 1 December
  7. Adjourn
Latest releases
Server Certificate Requirements
SC099: Improve Recording of Validation Methods - May 19, 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).