CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 158 – Adoption of Code Signing Baseline Requirements

Ballot 158 – Adoption of Code Signing Baseline Requirements

Voting on Ballot 158 (Code Signing BRs) closed on 17 December 2015. The results are as follows:

In the CA category, 17 CAs voted YES, 1 voted NO and 3 Abstained

In the Browser category, 2 browsers voted YES, 3 browsers voted NO and none Abstained

Therefore the ballot fails.

Detailed results can be seen here: https://docs.google.com/spreadsheets/d/1FBsMZjlzyvK3mFR1u4qMqvZwlI86yJ-v0am1pCBo8uI/edit#gid=4

After a 2 week pre-ballot, the Code Signing Working Group has now prepared the formal ballot below:

Ballot 158: Adopt Code Signing Baseline Requirements

The following motion is proposed by the Code Signing Working Group and is endorsed by Microsoft, Trend Micro and OATI. Further information on the ballot is in the email message below.

– – – – Motion for Ballot 158 – – – –

Be it resolved that the CA / Browser Forum adopts the recommendation of the Code Signing Working Group for Version 1.0 of the Baseline Requirements for Code Signing. Once adopted, the effective date will be October 1, 2016.

– – – Motion ends – – –

The review period for this ballot shall commence at 2200 UTC on 3 Dec 2015, and will close at 2200 UTC on 10 Dec 2015. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2200 UTC on 17 Dec 2015. Votes must be cast by posting an on-list reply to this thread.

A vote in favor of the motion must indicate a clear ‘yes’ in the response. A vote against must indicate a clear ‘no’ in the response. A vote to abstain must indicate a clear ‘abstain’ in the response. Unclear responses will not be counted. The latest vote received from any representative of a voting member before the close of the voting period will be counted. Voting members are listed here: /about/members/

In order for the motion to be adopted, two thirds or more of the votes cast by members in the CA category and greater than 50% of the votes cast by members in the browser category must be in favor. Quorum is currently nine (9) members– at least nine members must participate in the ballot, either by voting in favor, voting against, or abstaining.

Dean Coclin and Jeremy Rowley

Code Signing Working Group co-chairs

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