Home » All CA/Browser Forum Posts » Ballot CSC-4 v1: Move deadline for transition to RSA-3072 and SHA-2 timestamp tokens

Ballot CSC-4 v1: Move deadline for transition to RSA-3072 and SHA-2 timestamp tokens

Voting on this ballot has closed. The results are below:

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

0 CAs opposed

0 CAs abstaining

1 Certificate Consumer voting in favor: Microsoft

0 Certificate Consumers opposed

0 Certificate Consumers abstaining

Therefore the ballot passes.

Dean Coclin

CSCWG Chair

Ballot CSC-4 v1: Move deadline for transition to RSA-3072 and SHA-2 timestamp tokens

Purpose of the Ballot:

The current deadline for moving from RSA-2048 to RSA-3072 and from SHA-1 to SHA-2 for timestamp tokens falls on January 1, 2021, which is inconvenient due to code freezes due to the winter holidays. This ballot delays the deadline to June 1, 2021 for RSA-3072 and April 30, 2022 for SHA-2 timestamp tokens.

The following motion has been proposed by Tim Hollebeek of DigiCert, and endorsed by Ian McMillan of Microsoft and Hugh Mercer of GlobalSign.

Motion begins

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

Motion ends

/uploads/baseline_requirements_for_the_issuance_and_management_of_code_signing.v.2.1.pdf

/uploads/baseline_requirements_for_the_issuance_and_management_of_code_signing.v.2.1_redline.pdf

The procedure for approval of this ballot is as follows:

Discussion (7+ days) Start Time: 2020-09-22, 12:45pm Eastern Time (US) End Time: 2020-09-29, 1:10pm Eastern Time (US)

Vote for approval (7 days) Start Time: 2020-09-29, 1:10pm Eastern Time (US) End Time: 2020-10-06, 1:10pm Eastern Time (US)

Latest releases

Server Certificate Requirements
SC095v3: Clean-up 2025 - Apr 2, 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.14 - Ballot SMC016 - May 5, 2026

This ballot maintains consistency between the S/MIME Baseline Requirements and the TLS Baseline Requirements with changes introduced by Ballots SC096 and SC097. Specifically, this ballot: Creates a carve-out of the logging requirements for DNSSEC specifically, stating these are not in scope. For audit purposes, change management logging is able to confirm if the appropriate controls are in effect or not. Sunsets all remaining use of SHA-1 signatures in Certificates and CRLs. It is noted that most uses of SHA-1 signatures are already deprecated by SC097. With this ballot, all unexpired Subordinate CA Certificates issuing S/MIME containing the SHA-1 signature algorithm must be revoked. This proposal does not prohibit the use of SHA-1 to generate issuerKeyHash or issuerNameHash values as currently required by RFC 5019. Includes minor formatting corrections.

Network and Certificate System Security Requirements
Version 2.0.5 (Ballot NS-008) - Jul 9, 2025