Home » All CA/Browser Forum Posts » Ballot CSC-9 – Spring 2021 Cleanup and Clarification

Ballot CSC-9 – Spring 2021 Cleanup and Clarification

IPR Review Results

The review period has ended and no exclusion notices were filed.

The final documents, with the effective date being 9 September 2021, are available here.

Voting Results

Voting on Ballot CSC-9 has concluded and the ballot has passed. Below are the results:

CAs voting in favor: Actalis, Certum (Asseco), DigiCert, eMudhra, Entrust, GlobalSign, HARICA, Sectigo, SSL.com, SecureTrust

CAs opposed: None CAs abstaining: None

Certificate Consumers:

In Favor: Microsoft

Opposed: None

Abstaining: None

The Chair instructs the Vice Chair to create the guideline as voted.

Dean Coclin

CSCWG Chair

Purpose of this ballot

Cleanup and clarify requirements in the Baseline Requirement for the Issuance and Management of Publicly-Trusted Code Signing Certificates v2.3.

The following motion has been proposed by Bruce Morton, and endorsed by Ian McMillan of Microsoft and Corey Bonnell of DigiCert.

Motion begins

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

Baseline Requirements for the Issuance and Management of Code Signing Ballot CSC-9

Motion ends

The procedure for approval of this ballot is as follows:

Discussion (7 days) Start Time: 2021-07-20, 11:30 Eastern Time (US) End Time: not before 2021-07-27, 11:30 Eastern Time (US)

Vote for approval (7 days) Start Time:

Latest releases

Server Certificate Requirements
SC-084: DNS Labeled With ACME Account ID Challenge (#566) - Mar 13, 2025

BRs release version 2.1.4

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