CA/Browser Forum
Home » Working Groups » NetSec WG » Ballots

Network Security Working Group Ballots

Ballots by Status

Voting Period

There are no ballots with the status "Voting Period" in the Network Security Working Group

IPR Review Period

There are no ballots with the status "IPR Review" in the Network Security Working Group

Discussion Period

There are no ballots with the status "Discussion Period" in the Network Security Working Group

Draft / Under Consideration

There are no ballots with the status "New" in the Network Security Working Group
There are no ballots with the status "Pre-Ballot" in the Network Security Working Group

Passed

  • NS-008v3: Updates to CA Infrastructure Scope, Trusted Roles, Systems' Applicability, and various other improvements
  • NS-007: Extend deadline to implement NSRv2
  • NS-004: "Updating Section 4 - Vulnerability Management - of the NCSSRs"
  • NS-006: Fix 1.2.2 encrypted connections scoping
  • Forum-31: Election of CA/Browser Network Security WG Vice Chair
  • NS-005: Clarifications to sections 1, 2 and a definition prior to NS-003 taking effect
  • NS-003: Restructure the NCSSRs

Cancelled

There are no ballots with the status "Cancelled" in the Network Security Working Group

Failed

There are no ballots with the status "Ballot Failed" in the Network Security Working Group

Information about Ballots

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