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

2022-10-06 Minutes of the Code Signing Certificate Working Group

Attendees

Atsushi Inaba (GlobalSign), Bruce Morton (Entrust), Corey Bonnell (DigiCert), Dimitris Zacharopoulos (HARICA), Ian McMillan (Microsoft), Inigo Barreira (Sectigo), Martijn Katerbarg (Sectigo), Michael Sykes (SSL.com), Mohit Kumar (GlobalSign)

Minutes

  1. Antitrust statement was read.
  2. Approval of prior meeting minutes: Minutes for 22 September 2022 were approved.
  3. Ballot Status:
    1. CSC 15: IPR review ended 18 September 2022, so is now complete.
    2. CSC 17: Passed and is not in IPR period until 27 October 2022.
    3. Special election ballot: Passed, so Dean Coclin will be Chair for another term.
  4. Malware proposal (Martijn): Long discussion about the process and the number of days and the procedure when the CA receives notification about a certificate associated with signed malware. Martijn will update the proposal and forward for review.
  5. Signing Service discussion (Bruce/Corey): Signing Service update will be discussed at the F2F in Berlin.
  6. Timestamping Ballot (Ian): Ina would like to hold off discussion on time-stamping until after we have resolved the malware proposal and the Signing Service update.
  7. Planning for F2F: Decided we would have 1) Status Update, 2) Signing Service update discussion, and 3) Forward Vision discussion for the next 2 years.
  8. Other business: Discussed rationalizing the CSBRs to remove callout to SSL BRs. Dimitris will lead this effort with Corey and Bruce volunteering to support.
  9. Next Meeting – 20 October was cancelled. Next meeting will be at the F2F in Berlin the week of 24 October 2022.
  10. Adjourn
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).