CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 76 – Public Review of Network Security Controls

Ballot 76 – Public Review of Network Security Controls

Ballot 76 – Public Review of Network Security Controls (Passed)

Motion

Ben Wilson made the following motion, and Eddy Nigg and Gerv Markham endorsed it:

Motion begins

Members of the CAB Forum have drafted Network Security Requirements, dated May 14,2012, and setting a baseline level of network security for all certification authorities that operate or manage a root certificate embedded as a trust anchor in publicly distributed browser software. The document is available for review here:

The members therefore resolve to:

(1) ask the cabforum.org Web master to

(a) post the Network Security Requirements dated May 14 2012 on a publicly-accessible location on the cabforum.org web site;

(b) post a notice adjacent to the link for the draft advising the public that the CAB Forum will accept public comments until June 22, 2012.

(c) include in the notice instructions on how public comments may be discussed on the Mozilla security-policy mailing list;

(d) include in the notice instructions on how comments may be submitted by email to “”; and

(e) include any other relevant information necessary to accomplish the foregoing.

During the public comment period, the CAB Forum will:

(1) gather all questions posted to either the Mozilla list or the CAB Forum’s questions email list; and

(2) discuss the gathered questions via CAB Forum teleconference or email;

The ballot review period comes into effect at 2100 UTC on 29 May 2012 and will close at 2100 UTC on 5 June 2012. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2100 UTC on 12 June 2012.

Votes must be cast by “reply all” to this email.

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.

Motion ends

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