CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 172 – Removal of permanentIdentifier from EV Code Signing Guidelines

Ballot 172 – Removal of permanentIdentifier from EV Code Signing Guidelines

Voting on Ballot 172, “Removal of Permanent Identifier” has now closed. The results are as follows:

From the CAs, we received 9 YES votes, 1 NO vote and 7 Abstentions

From the Browsers, we received 1 YES vote, 0 NO votes and 0 Abstentions

Therefore the ballot passes. Full results can be seen on the ballot tracker: https://docs.google.com/spreadsheets/d/1FBsMZjlzyvK3mFR1u4qMqvZwlI86yJ-v0am1pCBo8uI/edit#gid=4

Dean Coclin

CA/B Forum Chair

Ballot 172 – Removal of permanentIdentifier from EV Code Signing Guidelines

The following motion has been proposed by Bruce Morton of Entrust and endorsed by Rick Andrews of Symantec and Jeremy Rowley of DigiCert:

Background:

The EV Code Signing Guidelines require a SAN which includes the permanentIdentifier. The permanentIdentifier is not used by any browser or operating system. Therefore, it is proposed that the permanentIdentifier requirement be removed from the EV Code Signing Guidelines.

–Motion Begins–

Effective upon the date of passage, the following modifications are made to the EV Code Signing Guidelines:

Section 9.2.2 • Replace all contents with “No stipulation.”

Section 9.7 (B): • Remove section 9.7 (B).

–Motion Ends–

The review period for this ballot shall commence at 2200 UTC on 21 June 2016, and will close at 2200 UTC on 28 June 2016. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2200 UTC on 5 July 2016. Votes must be cast by posting an on-list reply to this thread.

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. Voting members are listed here: /about/members/

In order for the motion to be adopted, two thirds or more of the votes cast by members in the CA category and greater than 50% of the votes cast by members in the browser category must be in favor. Quorum is currently ten (10) members– at least ten members must participate in the ballot, either by voting in favor, voting against, or abstaining.

Latest releases
Server Certificate Requirements
SC098: Process RFC 8657 CAA Parameters - Jun 16, 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.15 - Ballot SMC017v2 - Jul 30, 2026

This ballot increases the minimum RSA key size for Root and Subordinate CA certificates in the S/MIME BRs from 2048 to 4096 bits for keys created after September 15, 2026, while retaining the 2048-bit minimum for Subscriber certificates. The ballot further requires that by September 15, 2027, CAs SHALL NOT issue Subscriber certificates from any Sub-CA whose RSA key modulus is less than 3072 bits, effectively sunsetting issuance from legacy 2048-bit Sub-CAs. The ballot also includes minor typographic corrections. This ballot is proposed by Martijn Katerbarg (Sectigo) and endorsed by Ben Wilson (Mozilla) and Stephen Davidson (DigiCert)

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