CA/Browser Forum
Home » All CA/Browser Forum Posts » 2022-12-15 Minutes of the Code Signing Certificate Working Group

2022-12-15 Minutes of the Code Signing Certificate Working Group

Attendees

Andrea Holland, Brianca Martin, Bruce Morton, Corey Bonnell, Dean Coclin, Dimitris Zacharopoulos, Inigo Barreira, Michael Sykes Mohit Kumar, Rollin Yu, Tim Crawford, Trevoli Ponds-White

Minutes

Antitrust statement was read.

Minutes approved for last meeting 1-Dec-22 and F2F.

There was discussion on how we can make minutes more effective – in general with a suggestion on recapping along discussion by chair or minute taker for summary.

Ballot around Malware protection

Updates made to draft to suggest that subscriber can provide a different date based on impact. And also, software application provider can check for possible impact. Based on these 2, CA can decide on revocation date.

It was mentioned that section 4 is confusing and not clear.

Clarification provided that if CA receives a report of malware being signed, they will report it to subscriber. If subscriber reports within 72 hours, CAs can do impact assessment else they have to revoke in 24 hours. In any case, CA has to revoke in 7 days

Alternate proposal was presented that if subscriber or Software application asks CA to revoke, it should be revoked in 24 hours else in 7 days.

The critical element of the actual process is deciding what will be the revocation date i.e. the back date from which we expect malware to be signed. For this reason, we had procedure for impact analysis.

CA should have date of previously signed suspected code or evidence to show that private key was compromised. That way we can backdate the revocation

If we go to the back date of issue of certificate, then it impacts all the drivers signed till date so CA need a different timestamp.

Need to be improved and discussion to be kept in progress.

Signing Service

No updates

Removing SSL BRs references

Concerns highlighted in redline in Github. Pull request to be shared with the group.

Next meeting will be on 12-Jan-23

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.13 - Ballot SMC015v2 - Mar 28, 2026

This ballot introduces requirements that a CA or RA must follow to rely upon a Mobile Drivers License (mDL) to provide evidence for the authentication of individual identity. It allows the use of mDL that conform to ISO/IEC 18013-5 and which may be verified by the CA or RA in conformance with ISO/IEC 18013-7. The CA or RA shall only accept mDL from an Issuing Authority that is legally authorized by the relevant government or jurisdiction to issue driving licenses. The draft also aligns the subsections of 3.2.4.2 (Validation of individual identity) to correspond more closely with those in 3.2.4.1 (Attribute collection of individual identity). It also includes minor editorial corrections. SMC015v2 was updated to remove an additional reference to the superceded ETSI EN 319 403. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Ben Wilson (Mozilla) and Scott Rea (eMudhra).

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