Home » All CA/Browser Forum Posts » Ballot 182 – Readopting BR 3.2.2.4 (Part 2)

Ballot 182 – Readopting BR 3.2.2.4 (Part 2)

Ballot 182 has failed – see results below. We will send out more information on what happens next.

Ballot 182 Results

CAs – 0 votes

Browsers – 0 votes

Result: Ballot 182 fails (requires 2/3 affirmative vote by CAs and majority affirmative vote by browsers). Quorum is 10 votes – quorum not achieved.

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.16 - Ballot SMC018 - Sep 29, 2026

This ballot implements the requirements of CCADB Policy Section 6.3 relating to cross-certificates into the S/MIME BR effective immediately. The ballot also specifies that effective July 1, 2027 id-kp-emailProtection (mandatory) and the id-kp-clientAuth (optional) are the only extKeyUsage (EKU) permitted in both Subordinate CA Certificates and Subscriber Certificates. Finally, the ballot clarifies in the Definitions that Legacy Generation profiles were deprecated effective July 15, 2025. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Dustin Hollinback (Apple) and Ashish Dhiman (GlobalSign)

Network and Certificate System Security Requirements
Version 2.0.5 (Ballot NS-008) - Jul 9, 2025