CA/Browser Forum
Home » All CA/Browser Forum Posts » 2025-10-30 Minutes of the Code Signing Certificate Working Group

2025-10-30 Minutes of the Code Signing Certificate Working Group

CSCWG – Meeting Minutes

Date: October 30, 2025

1. Note Well

The Note Well was read.

2. Review of Agenda

Agenda accepted as sent.
Minutes backlog noted; drafts to be circulated for approval at a future call.

3. Discussion Topics

SC-Alignment ballot — Microsoft OCSP concerns

  • Still awaiting Microsoft’s specific concerns on OCSP language from the failed SC-alignment ballot.
  • Nate will ping Karina for an update and ETA.
  • Group prefers to understand concerns before carving items out.

F2F take-aways and next steps

  • F2F largely focused on guest presentations (law enforcement and researcher). Slides will be linked from CSCWG minutes; recording is available.
  • PQC for code signing:
    • Brianca requested adding PQC back to the agenda; most other groups are progressing PQC.
    • Nate: Windows Insider builds support experimenting with ML-DSA for code signing via APIs (e.g., SignTool verify); ADCS support is not yet in public preview. He will share public docs to CSCWG-public.
  • Hardening against threat actors:
    • Ideas discussed: CT-like logging for code signing (with privacy considerations), clearer revocation signaling (malware-specific reason code), and adding telemetry that helps anti-malware vendors.
    • Concern: privacy in certificates vs. value to defenders.
    • Nate will check with Microsoft Defender contacts on what certificate data or logging would be most useful; may join a future call for a discussion.
  • Single profile work:
    • Martijn started drafting a ballot toward a single profile (EV-style validation). Open to collaborators.
    • Open question: replace JOI fields with organizationIdentifier (as in S/MIME). No positions taken yet.

Future schedule of teleconferences

  • Proposal: move from biweekly to every 4 weeks, and use the mailing list more actively between calls.
  • No objections on the call. Martijn will confirm via CSCWG-public.

4. Any Other Business

None raised.

5. Adjourn

Attendees

Brianca Martin (Amazon), Brian Winters (IdenTrust), Inaba Atsushi (GlobalSign), Luis Cervantes (SSL.com), Marco Schambach (IdenTrust), Martijn Katerbarg (Sectigo), Nate Santiago (Microsoft), Nome Huang (TrustAsia), Rebecca Kelly (SSL.com), Thomas Zermeno (SSL.com), Wiktoria Więckowska (Asseco Data Systems SA (Certum))

Latest releases
Server Certificate Requirements
SC088v3: DNS TXT Record with Persistent Value DCV Method - Nov 11, 2025

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.12 - Ballot SMC014 - Oct 13, 2025

This ballot introduces requirements that a Certificate Issuer MUST deploy DNSSEC validation back to the IANA DNSSEC root trust anchor on all DNS queries associated with CAA record lookups performed by the Primary Network Perspective, effective March 15, 2026. The ballot is intended to maintain consistency in the S/MIME Baseline Requirements with the requirements of Ballot SC-085 which implemented identical requirements in the TLS Baseline Requirements. Note: SC-085 also introduced requirements in TLS Baseline Requirements for the use of DNSSEC in domain control validation. These requirements are automatically adopted in the S/MIME BR by the email domain control methods that include a normative reference to section 3.2.2.4 of the TLS Baseline Requirements. The draft also includes minor corrections to web links in the text. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Client Wilson (Apple) and Ashish Dhiman (GlobalSign).

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