CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 160 – Amend Section 4 of Baseline Requirements

Ballot 160 – Amend Section 4 of Baseline Requirements

Voting on Ballot 160 closed on 4 February 2016. There were 18 YES votes, 0 NO votes and 0 Abstentions from CAs. There were 3 YES votes, and 0 NO or Abstention votes from Browsers.

Therefore, the ballot passes.

Ballot 160 – Amend Section 4 of Baseline Requirements

The Policy Review Working Group has reviewed Section 4 of the Baseline Requirements and, as a result, suggests that certain changes be made. Therefore, the following motion has been proposed by Ben Wilson of DigiCert and endorsed by Tim Hollebeek of Trustwave and Kirk Hall of TrendMicro:

Motion begins

  1. In Sections 4.2.3, 4.3.2, 4.4.1, 4.4.2, 4.4.3, 4.5.2, 4.6.1, 4.6.2, 4.6.3, 4.6.4, 4.6.5, 4.6.6, 4.6.7., 4.7.1, 4.7.2, 4.7.3, 4.7.4, 4.7.5, 4.7.6, 4.7.7, 4.8.1, 4.8.2, 4.8.3, 4.8.4, 4.8.5, 4.8.6, 4.8.7, 4.9.4, 4.9.8, 4.10.3, 4.11, and 4.12.1, add “No stipulation.”

  2. In Sections 4.9.14, 4.9.15, 4.9.16, and 4.12.2, add “Not applicable.”

  3. In Section 4.5.1, add “See Section 9.6.3, provisions 2. and 4.”

  4. In Section 4.9.2, add “The Subscriber, RA, or Issuing CA can initiate revocation. Additionally, Subscribers, Relying Parties, Application Software Suppliers, and other third parties may submit Certificate Problem Reports informing the Issuing CA of reasonable cause to revoke the certificate. ”

  5. In Section 4.9.6, add “No stipulation. (Note: Following certificate issuance, a certificate may be revoked for reasons stated in Section 4.9.1. Therefore, relying parties should check the revocation status of all certificates that contain a CDP or OCSP pointer.)”

Motion ends

The review period for this ballot shall commence at 2300 UTC on 21 January 2016, and will close at 2300 UTC on 28 January 2016. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2300 UTC on 4 February 2016. Votes must be cast by posting an on-list reply to this thread.

A vote in favor of the motion must indicate a clear ‘yes’ in the response. A vote against must indicate a clear ‘no’ in the response. 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:

In order for the motion to be adopted, two thirds or more of the votes cast by members in the CA category and greater than 50% of the votes cast by members in the browser category must be in favor. Quorum is currently nine (9) members– at least nine members must participate in the ballot, either by voting in favor, voting against, or abstaining.

See Ballot-160 Redlining of Section 4 of BRs

Latest releases
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.13 - Ballot SMC015v2 - Mar 28, 2026

This ballot introduces requirements that a CA or RA must follow to rely upon a Mobile Drivers License (mDL) to provide evidence for the authentication of individual identity. It allows the use of mDL that conform to ISO/IEC 18013-5 and which may be verified by the CA or RA in conformance with ISO/IEC 18013-7. The CA or RA shall only accept mDL from an Issuing Authority that is legally authorized by the relevant government or jurisdiction to issue driving licenses. The draft also aligns the subsections of 3.2.4.2 (Validation of individual identity) to correspond more closely with those in 3.2.4.1 (Attribute collection of individual identity). It also includes minor editorial corrections. SMC015v2 was updated to remove an additional reference to the superceded ETSI EN 319 403. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Ben Wilson (Mozilla) and Scott Rea (eMudhra).

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