CA/Browser Forum
Home » All CA/Browser Forum Posts » New Working Group on Performance Formed

New Working Group on Performance Formed

Announcing the formation of the Performance Working Group – Call for Participants

The CA/Browser Forum has chartered a Performance Working Group, the purpose of which is to review certificate contents, choice of proposed ciphers, webserver configuration, and OCSP configuration for best practice guidance for performance while still providing acceptable levels of security. The CA/Browser Forum would like to invite interested third parties to participate. The working group meets bi-weekly by phone and expects to hold face to face meetings coinciding with the regular CA/Browser Forum meetings.

Interested parties will need to:

  1. Review the Intellectual Property Rights policy (/IPR_Policy_V1.pdf) and complete the IPR agreement which can be found here: /IPR_Agreement_V1.pdf
  2. Send an email to questions@cabforum.org with your name, organization (if applicable), contact details and the signed agreement with the subject: Performance Working Group Participation

Once the Chair determines all is in order, you will be added to the mailing list and invited to the conference calls.

As the title of this group states, this is a Working Group, meaning everyone is expected to contribute in some fashion. Please do not apply if you can’t devote time to attend and participate in the discussion.

Latest releases
Server Certificate Requirements
SC099: Improve Recording of Validation Methods - May 19, 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

Related posts
Tags
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).