CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 65 – QIIS Definition Update

Ballot 65 – QIIS Definition Update

Ballot 65 – QIIS Definition Update (Passed Unanimously)

Motion

Jeremy Rowley made the following motion, and Rich Smith and Stephen Davidson endorsed it:

Motion begins

Effective immediately:

  • Erratum begins Replace Section 10.10.5 in the EV Guidelines:

A Qualified Independent Information Source (QIIS) is a regularly-updated and current, publicly available, database designed for the purpose of accurately providing the information for which it is consulted, and which is generally recognized as a dependable source of such information. A commercial database is a QIIS if the following are true:

(1) Industry groups rely on the database for providing accurate location or contact information;

(2) The database distinguishes between self-reported data and data reported by independent information sources;

(3) The database provider identifies how frequently they update the information in their database;

(4) Changes in the data that will be relied upon will be reflected in the database in no more than 12 months; and

(5) The database provider uses authoritative sources independent of the Subject, or multiple corroborated sources, to which the data pertains.

Databases in which the CA or its owners or affiliated companies maintain a controlling interest, or in which any Registration Authorities or subcontractors to whom the CA has outsourced any portion of the vetting process (or their owners or affiliated companies) maintain any ownership or beneficial interest do not qualify as a QIIS. The CA MUST check the accuracy of the database and ensure its data is acceptable.

With:

A Qualified Independent Information Source (QIIS) is a regularly-updated and current, publicly available, database designed for the purpose of accurately providing the information for which it is consulted, and which is generally recognized as a dependable source of such information. A commercial database is a QIIS if the following are true:

(1) The database is generally recognized as and relied on by other industries for providing accurate data;

(2) The database distinguishes between self-reported data and data reported by independent information sources;

(3) The database provider identifies how frequently the data is updated;

(4) Changes in the data that will be relied upon will be reflected in the database in no more than 12 months; and

(5) The database provider uses authoritative sources or multiple corroborated sources.

Databases in which the CA or its owners or affiliated companies maintain a controlling interest, or in which any Registration Authorities or subcontractors to whom the CA has outsourced any portion of the vetting process (or their owners or affiliated companies) maintain any ownership or beneficial interest do not qualify as a QIIS. The CA MUST check the accuracy of the database and ensure its data is acceptable.

Erratum Ends

The ballot review period comes into effect at 2100 UTC on 2 Feb ’12 and will close at 2100 UTC on 9 Feb ’12. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 2100 UTC on 16 Feb ’12. Votes must be cast by “reply all” to this email.

Motion Ends

Latest releases
Server Certificate Requirements
BRs/2.1.2 SC-080 V3: Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods - Dec 16, 2024

Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contact… (https://github.com/cabforum/servercert/pull/560) Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods” (https://github.com/cabforum/servercert/pull/555)

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.8 - Ballot SMC010 - Dec 23, 2024

This ballot adopts Multi-Perspective Issuance Corroboration (MPIC) for CAs when conducting Email Domain Control Validation (DCV) and Certification Authority Authorization (CAA) checks for S/MIME Certificates. The Ballot adopts the MPIC implementation consistent with the TLS Baseline Requirements. Acknowledging that some S/MIME CAs with no TLS operations may require additional time to deploy MPIC, the Ballot has a Compliance Date of May 15, 2025. Following that date the implementation timeline described in TLS BR section 3.2.2.9 applies. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Ashish Dhiman (GlobalSign) and Nicolas Lidzborski (Google).

Network and Certificate System Security Requirements
v2.0 - Ballot NS-003 - Jun 26, 2024

Ballot NS-003: Restructure the NCSSRs in https://github.com/cabforum/netsec/pull/35

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