CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot SMC017: Increase Minimum RSA CA Key Size

Ballot SMC017: Increase Minimum RSA CA Key Size

Ballot SMC017: Increase Minimum RSA CA Key Size

Ballot SMC017 was withdrawn on May 12, 2026.

Ballot SMC017: Increase Minimum RSA CA Key Size

Summary:

This ballot increases the minimum RSA key size for Root and Subordinate CA certificates in the S/MIME BRs from 2048 to 4096 bits for keys created on or after September 15, 2026, while retaining the 2048-bit minimum for Subscriber certificates.

The ballot further requires that by September 15, 2027, CAs SHALL NOT issue certificates from any Sub-CA whose RSA key modulus is less than 4096 bits, effectively sunsetting issuance from legacy 2048-bit Sub-CAs.

This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Ben Wilson (Mozilla) and Roman Fischer (SwissSign).

— Motion Begins —

This ballot modifies the “Baseline Requirements for the Issuance and Management of Publicly-Trusted S/MIME Certificates” (“S/MIME Baseline Requirements”), based on Version 1.0.13.

MODIFY the Baseline Requirements as specified in the following Redline:

https://github.com/cabforum/smime/compare/21bda9e4a5f04f373dbd359b4e2213a3f4910c76...a6d582ab7da98ac1ca7fd92f35f321aa9f70df37

— Motion Ends —

This ballot proposes a Final Maintenance Guideline. The procedure for approval of this ballot is as follows:

Discussion (at least 7 days)

  • Start time: April 29, 2026 at 18:30:00 UTC

  • End time: May 6, 2026 at 18:30:00 UTC

Voting for Approval

  • Start time: May 6, 2026 at 21:30:00 UTC

  • End time: May 13, 2026 at 21:30:00 UTC

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