CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 35 – Role Requirements

Ballot 35 – Role Requirements

Ballot 35 – Role Requirements (Passed Unanimously)

Motion

Tim Moses made the following motion, and Mads Henriksveen and Jay Schiavo endorsed it:

Motion begins

The role requirements laid out in Section 9.1.2 are incorrect.

Effective immediately, delete: “9.1.2 Role Requirements

The following Applicant roles are required for the issuance of an EV Certificate.

One person MAY be authorized by the Applicant to fill one, two, or all three of these roles, provided that the Certificate Approver and Contract Signer are employees of the Applicant. An Applicant MAY also authorize more than one person to fill each of these roles.”

And insert: “9.1.2 Role Requirements

The following Applicant roles are required for the issuance of an EV Certificate.

The Applicant MAY authorize one individual to occupy two or more of these roles. The Applicant MAY authorize more than one individual to occupy any of these roles.’

Motion ends

The ballot review period comes into effect at 2100 UTC on 11 Jan ’10 and will close at 2100 UTC on 18 Jan ’10. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2100 UTC on 25 Jan ’10.

Votes must be cast by ‘reply all’ to this email.

A vote in favour 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.

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

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