Home » All CA/Browser Forum Posts » WebTrust Releases New Audit Criteria for Extended Validation and Baseline Requirements

WebTrust Releases New Audit Criteria for Extended Validation and Baseline Requirements

On April 3, 2014, the WebTrust® Task Force of the American Institute of CPAs (AICPA) and Chartered Professional Accountants Canada (CPA Canada) released three new audit criteria documents to the CA/Browser Forum and others for review and/or implementation. These documents are part of the WebTrust Program for Certification Authorities and are based on the CA/Browser Forum Guidelines.

The Trust Services Principles and Criteria for Certification Authorities – Extended Validation SSL – Version 1.4.5 is based on the Forum’s Guidelines for the Issuance and Management of Extended Validation SSL Certificates – Version 1.4.5 and is effective immediately (3 April 2014).

Trust Services Principles and Criteria for Certification Authorities – SSL Baseline with Network Security – Version 2.0 is based on the Forum’s Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates – Version 1.1.6 and its Network and Certificate Systems Security Requirements – Version 1.0. The exposure draft released today has a proposed effective date of 1 July 2014 (applicable to audit periods starting on or after 1 July 2014).

The Trust Services Principles and Criteria for Certification Authorities – Extended Validation Code Signing is based on the Forum’s Guidelines for the Issuance and Management of Extended Validation Code Signing Certificates – Version 1.1. The exposure draft released today has a proposed effective date of 1 July 2014 (applicable to audit periods starting on or after 1 July 2014).

All three of these documents are available in PDF, DOC and DOCX format at .

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