CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot CSC-20: Restore Version Reference to EV Guidelines

Ballot CSC-20: Restore Version Reference to EV Guidelines

Ballot CSC-20: Restore Version Reference to EV Guidelines

Notice of Review Period

The IPR review period ended on December 7, 2023 and no exclusion notices were filed.

The final documents, with the effective date being 2023-12-07, are available here.

This Review Notice is sent pursuant to Section 4.1 of the CA/Browser Forum’s Intellectual Property Rights Policy (v1.3). This Review Period is for a Final Maintenance Guideline (30 day Review Period). A complete Draft Guideline subject of this Review Notice is available here.

Ballot for Review: Ballot CSC-20

Start of Review Period: October 30, 2023 at 6:00 pm Eastern Time

End of Review Period: December 1, 2023 at 6:00 pm Eastern Time

Please forward a written notice to exclude Essential Claims to the Forum and Working Group Chair by email to and a copy to the CA/B Forum CSCWG public mailing list before the end of the Review Period.

Results of Voting

YesNoAbstain
Certificate IssuersDigiCert, eMudhra, Entrust, GlobalSign, HARICA, Sectigo
Certificate ConsumersMicrosoft

This ballot has PASSED.

Purpose of the Ballot

This ballot updates the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Code Signing Certificates” version 3.4 in order to restore a version reference to the Extended Validation Guidelines which was inadvertently removed in a previous version of the Requirements. In addition, a minor typographical issue is also resolved.

The following motion has been proposed by Corey Bonnell of DigiCert and endorsed by Bruce Morton of Entrust and Dimitris Zacharopoulos of HARICA.

Motion

This ballot updates the “Baseline Requirements for the Issuance and Management of Publicly-Trusted Code Signing Certificates” (“Code Signing Baseline Requirements”) based on version 3.4.

MODIFY the Code Signing Baseline Requirements as specified in the following redline: https://github.com/cabforum/code-signing/compare/93ee9976cdc4e1104952146e3556800459694874…50b40d41319ffae5fec9c9dd22ae6ebb55c34ba1

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