CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot CSC-7v2: Update to merge EV and Non-EV clauses

Ballot CSC-7v2: Update to merge EV and Non-EV clauses

Voting has closed on this ballot and the results are as follows:

CAs voting in favor (7): Actalis, DigiCert, Entrust, GDCA, GlobalSign, GoDaddy, HARICA

CAs opposed: None

CAs abstaining: None

Certificate Consumers voting in favor (1): Microsoft Certificate Consumers opposed: None Certificate Consumers abstaining: None

Therefore the ballot CSC-7 passes.

Purpose of the Ballot:

The CSC-2 merger of the Code Signing BRs and the EV Code Signing Guidelines was done without technical changes. The result is that we have some sections where there is different text for Non-EV and EV Code Signing certificates. In many cases there was no reason to have two different requirements. In other cases, it made sense that they both have the same requirement. There were of course some items where EV is different and these clauses were not touched for now. These items were all discussed in our bi-weekly meetings. Other minor changes were the adding in a table for document revision and history and another table for effective dates within the BRs. There were also some errors corrected from the merger.

The following motion has been proposed by Bruce Morton of Entrust, and endorsed by Dimitris Zacharopoulos of HARICA and Dean Coclin of DigiCert.

Motion begins

This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates” version 2.1 according to the attached redline.

Baseline Requirements for the Issuance and Management of Code Signing v2.2.pdf Baseline Requirements for the Issuance and Management of Code Signing v2.2 – redline.pdf

Motion ends

The procedure for approval of this ballot is as follows:

Discussion (7+ days) Start Time: 2021-01-14, 3:00 PM Eastern Time (US) End Time: not before 2021-01-25, 9:00 AM Eastern Time (US)

Vote for approval (7 days)

Start Time: 2021-01-25, 9:00 AM Eastern Time (US) End Time: 2021-02-01, 9:00 AM Eastern Time (US)

Latest releases
Server Certificate Requirements
SC088v3: DNS TXT Record with Persistent Value DCV Method - Nov 11, 2025

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.12 - Ballot SMC014 - Oct 13, 2025

This ballot introduces requirements that a Certificate Issuer MUST deploy DNSSEC validation back to the IANA DNSSEC root trust anchor on all DNS queries associated with CAA record lookups performed by the Primary Network Perspective, effective March 15, 2026. The ballot is intended to maintain consistency in the S/MIME Baseline Requirements with the requirements of Ballot SC-085 which implemented identical requirements in the TLS Baseline Requirements. Note: SC-085 also introduced requirements in TLS Baseline Requirements for the use of DNSSEC in domain control validation. These requirements are automatically adopted in the S/MIME BR by the email domain control methods that include a normative reference to section 3.2.2.4 of the TLS Baseline Requirements. The draft also includes minor corrections to web links in the text. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Client Wilson (Apple) and Ashish Dhiman (GlobalSign).

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