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

2023-04-20 Minutes of the Code Signing Certificate Working Group

Attendees

Bruce Morton – (Entrust), Corey Bonnell – (DigiCert), Dean Coclin – (DigiCert), Dimitris Zacharopoulos – (HARICA), Ian McMillan – (Microsoft), Inaba Atsushi – (GlobalSign), Inigo Barreira – (Sectigo), Janet Hines – (VikingCloud), Martijn Katerbarg – (Sectigo), Tim Crawford – (CPA Canada/WebTrust)

Minutes

Note Well: The Note Well was read.

Approval of Minutes: April 6th minutes are approved. January 26th minutes are pending. Bruce will take over writing these minutes.

Ballot Status

  • CSC-18 – In discussion period. A few additional items were mentioned which are being added:
  • Request from Application Software Suppliers to not revoke a certificate when requested by them
  • Effective Date. During the call it was discussed to set April 15th 2024 as the effective date, also adding language that will allow CAs to start using the new way earlier.
  • A v2 ballot will be started soon
  • Incorporating BR references
  • No changes since the last meeting. Still need to review and go over definitions
  • Signing Service
  • No changes here. Also waiting on the other two ballots to complete first

RFC for Key Attestation

Mike from Entrust is trying to put together an RFC around Key Attestation. Information was circulated on the public list for anyone wanting to assist

There was a discussion on TPM 2.0 chips and similar if these are allowed or not. There’s consensus that as long as a device is FIPS 140-2 or 140-3 at the correct level, they are allowed to be used.

This will be clarified in the CSBRs in a future ballot.

Any Other Business

Next F2F is in 6 weeks. Ian mentioned that he plans on requesting a number of Microsoft employees working close with Code Signing to join the CSWG session as well as have some guest speakers during the F2F

Next Meeting

May 4th

Latest releases
Server Certificate Requirements
SC100: DNSSEC Clarification and Consolidation - Sep 7, 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.17 - Ballot SMC020 - Nov 20, 2026

Addresses https://github.com/cabforum/smime/issues/308. Aligns the S/MIME BR with TLS BR Ballot SC-099. Changes Section 3.2.2: Removes the requirement to record the validation method “including the relevant version number” from the TLS BR or S/MIME BR. This version number is unclear and can’t be enforced. It also creates problems for CAs that share validation services with TLS and have already stopped logging it. Section 5.4.1 (2.ii): Effective March 15, 2027, audit logs of verification activities must include: the information validated; the domain name whose control was validated, if different from the domain portion of the Mailbox Address (e.g., the Authorization Domain Name or SMTP FQDN); the validation method used. Together with the time and date that 5.4.1 already requires, this is enough to tell which requirements applied to a validation. Section 1.2.1: Adds revision and compliance date rows. The ballot number and publication date are placeholders. Differences from SC-099 Uses “domain name whose control was validated” instead of “ADN”, because ADN is not defined in the SBR and S/MIME also covers SMTP FQDN validation (3.2.2.3). The method can refer to a section of either the SBR or the TLS BR, because 3.2.2.1 and 3.2.2.3 rely on TLS BR 3.2.2.4.

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).