CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot CSC-23 - Marking the EV Code Signing Guidelines SUPERCEDED

Ballot CSC-23 - Marking the EV Code Signing Guidelines SUPERCEDED

The final documents, with the effective date being 2024-03-26, are available here.

Results of Voting

YesNoAbstain
Certificate IssuersActalis, Asseco (Certum), DigiCert, Entrust, Globalsign, HARICA, IdenTrust, Sectigo, SSL.com
Certificate ConsumersMicrosoft

Purpose of the Ballot

As agreed at the F2F#61 meeting, this is a ballot to mark the “Guidelines For The Issuance And Management Of Extended Validation Code Signing Certificates” as superceded.

The following motion has been proposed by Dimitris Zacharopoulos of HARICA and endorsed by Scott Rea of eMudhra and Martijn Katerbarg of Sectigo.

Motion

Update the EVCS Guidelines v1.4 to version 1.5 with the following changes: In the “Notice to Readers” section, update the second paragraph to state:

“The Code Signing Working Group considers this document SUPERCEDED as of September 2, 2020. CAs SHOULD NOT use this standard but instead SHOULD use the “Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates” that has incorporated and improved requirements related to Extended Validation (EV) Code Signing Certificates.”

Update section 17.1 to state the following:

“As this document is marked SUPERCEDED, CAs SHOULD NOT be audited against this standard. "

Latest releases
Server Certificate Requirements
BRs/2.1.2 SC-080 V3: Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods - Dec 16, 2024

Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contact… (https://github.com/cabforum/servercert/pull/560) Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods” (https://github.com/cabforum/servercert/pull/555)

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.8 - Ballot SMC010 - Dec 23, 2024

This ballot adopts Multi-Perspective Issuance Corroboration (MPIC) for CAs when conducting Email Domain Control Validation (DCV) and Certification Authority Authorization (CAA) checks for S/MIME Certificates. The Ballot adopts the MPIC implementation consistent with the TLS Baseline Requirements. Acknowledging that some S/MIME CAs with no TLS operations may require additional time to deploy MPIC, the Ballot has a Compliance Date of May 15, 2025. Following that date the implementation timeline described in TLS BR section 3.2.2.9 applies. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Ashish Dhiman (GlobalSign) and Nicolas Lidzborski (Google).

Network and Certificate System Security Requirements
v2.0 - Ballot NS-003 - Jun 26, 2024

Ballot NS-003: Restructure the NCSSRs in https://github.com/cabforum/netsec/pull/35

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