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
SC-089: Mass Revocation Planning - Aug 26, 2025

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.12 - Ballot SMC014 - Oct 13, 2025

This ballot introduces requirements that a Certificate Issuer MUST deploy DNSSEC validation back to the IANA DNSSEC root trust anchor on all DNS queries associated with CAA record lookups performed by the Primary Network Perspective, effective March 15, 2026. The ballot is intended to maintain consistency in the S/MIME Baseline Requirements with the requirements of Ballot SC-085 which implemented identical requirements in the TLS Baseline Requirements. Note: SC-085 also introduced requirements in TLS Baseline Requirements for the use of DNSSEC in domain control validation. These requirements are automatically adopted in the S/MIME BR by the email domain control methods that include a normative reference to section 3.2.2.4 of the TLS Baseline Requirements. The draft also includes minor corrections to web links in the text. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Client Wilson (Apple) and Ashish Dhiman (GlobalSign).

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