CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot FORUM-13: Correction to Code-Signing Working Group Charter

Ballot FORUM-13: Correction to Code-Signing Working Group Charter

The voting period for Ballot FORUM-13 has ended and the Ballot has Passed. Here are the results:

Voting by Certificate Issuers – 16 votes total

16 CAs voted in favor: Entrust Datacard, eMudhra, DigiCert, Certigna, Certum, Sectigo, Trustcor, SecureTrust, HARICA, Camerfirma, Actalis, Disig, SwissSign, GoDaddy, GDCA, Chungwa Telecom

Voting by Certificate Consumers – 3 votes total

Three Certificate Consumers voted in favor: Microsoft, Mozilla, 360

Therefore, the ballot Passes.

The following ballot is proposed by Dean Coclin of DigiCert and has been endorsed by Robin Alden (Sectigo) and Mike Reilly (Microsoft).

Purpose: This ballot modifies the CSCWG charter to correct an error in the original document in Section 4.2.2. It was pointed out that there is an error in the CSCWG charter, section 4.2.2 where it states:


Applicants that qualify as Certificate Issuers or Root Certificate Issuers must supply the following additional information:

  • URL of the current qualifying audit report.
  • The URL of at least one third party website that includes a certificate issued by the Applicant in the certificate chain.
  • Links or references to issued end-entity certificates that demonstrate them being treated as valid by a Certificate Consumer Member.

The second bullet should be removed as it was a copy and paste error from another charter.

Ballot Conflicts

  • None

Changes:

As noted above and on github:

https://github.com/timfromdigicert/documents/commit/dc7ebf48d45304f101e47b688ab672d4d720957c

Motion begins

Modify the Code Signing Working Group Charter as indicated above and in the github redline.

Motion ends

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