Home » All CA/Browser Forum Posts » CA/Browser Forum Revises Bylaws for Associate Members

CA/Browser Forum Revises Bylaws for Associate Members

On March 25, 2014, the CA/Browser Forum adopted version 1.1 of its bylaws to recognize its long-standing relationships, industry liaisons, and involvement of other organizations in the Forum’s activities. These have included the AICPA/CICA WebTrust Task Force, the European Telecommunications Standards Institute, and several other organizations. A copy of these new bylaws is now posted on the Bylaws page of the Forum’s site.

Latest releases

Server Certificate Requirements
SC099: Improve Recording of Validation Methods - May 19, 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.

Unable to retrieve latest release information from the netsec repository.