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

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