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