CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot CSC-14 – Convert Code Signing Baseline Requirements to RFC 3647 Framework

Ballot CSC-14 – Convert Code Signing Baseline Requirements to RFC 3647 Framework

Results of Review Period

(Mailing list post is available here.)

The IPR review period ended on June 25, 2022 and no exclusion notices were filed.

The final documents, with the effective date being 2022-06-29, are available here.

Summary of Review

Ballot for ReviewBallot CSC-14 – Convert Code Signing Baseline Requirements to RFC 3647 Framework
Start of Review Period26 May 2022 at 18:00 UTC
End of Review Period25 June 2022 at 18:00 UTC

Members with any Essential Claim(s) to exclude must forward a written Notice to Exclude Essential Claims to the Working Group Chair (email to ) and also submit a copy to the CA/B Forum public mailing list (email to ) before the end of the Review Period.

For details, please see the current version of the CA/Browser Forum Intellectual Property Rights Policy.

Results of Voting

YesNoAbstain
Certificate IssuersActalisCertum (Asseco), DigiCert, eMudhra, Entrust, GlobalSign, HARICA, SSL.com, SecureTrustSectigo
Certificate ConsumersMicrosoft

The ballot has PASSED.

Purpose of the Ballot

RFC 3647 defines a standard framework for outlining the obligations of participants in a PKI. Following the recommended framework as specified in RFC 3647 allows for easier comparison of “The Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates” with other policy documents, most notably work products of other CA/Browser Forum working groups and individual Certification Authority Certificate Policies and Certification Practice Statements. This ballot restates all existing obligations and requirements that are contained in The Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates” in the outline recommended by RFC 3647.

The following motion has been proposed by Corey Bonnell of DigiCert and endorsed by Ian McMillan of Microsoft and Dimitris Zacharopoulos of HARICA.

Motion

This ballot updates the “Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates” version 2.8 by replacing the entirely of the content of the document with the attached document.

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.

Unable to retrieve latest release information from the netsec repository.
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).