CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 90 – Governance Finalists

Ballot 90 – Governance Finalists

Ballot 90 – Governance Finalists

Results

Trend Micro - 18 votes - Certum, Comodo CA Ltd, Digidentity, GoDaddy.com, Inc., Izenpe S.A., KEYNECTIS, KPN Getronics PinkRoccade, Logius PKIoverheid, Microsoft Corporation, Network Solutions, LLC, Opera Software ASA, QuoVadis Ltd., Skaitmeninio sertifikavimo centras (SSC), StartCom Certification Authority, SwissSign AG, Trend Micro, Trustis Limited, and Wells Fargo Bank, N.A.,

Digicert - 8 votes - Buypass AS, DigiCert, Inc., GlobalSign, Google Inc., Symantec Corporation, TAIWAN-CA Inc., The Mozilla Foundation, and Trustwave.

Therefore, pursuant to Ballot 85, the Trend Micro proposal is adopted and a period of undefined duration has commenced, during which Trend Micro shall refine its proposal in order to ensure its completeness, while keeping within the spirit of the original proposal posted to . Once the proposal has been finalized, a ratification ballot shall be conducted in accordance with established Forum procedures to ratify the proposal.

Ballot Text

Pursuant to Ballot 85, Governance Reform, a 7-day review period of the two final proposals for governance reform of the CA/Browser Forum has commenced and closes at 2100 UTC on 21 September 2012. Each proponent has provided its final proposal for the purposes of this review period. This review period (Sept. 14-21) shall be followed by a seven-day voting period (Sept. 21-28) and will close at 2100 UTC on 28 September 2012.

Votes by members must be cast by a “reply all” post to the “Ballot 90 – Governance Finalists” email thread on either the Management or Public email list.

A vote in favor of either proposal must contain a clear indication of whether the vote is for the DigiCert proposal or the Trend Micro proposal. A vote to abstain must indicate a clear ‘abstain’ in the response. Unclear responses will not be counted. The latest vote received from any representative of a voting member before the close of the voting period will be counted.

Voting members are listed here:

Pursuant to Ballot 85, the proposal receiving a simple majority of votes in favor will be deemed the governance policy that the Forum will pursue.

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