[Cscwg-public] IPR Review Complete: Ballot CSC-13 - Update to Subscriber Private Key Protection Requirements

Bruce Morton Bruce.Morton at entrust.com
Mon May 9 18:52:10 UTC 2022


The IPR review period has ended and no exclusion notices were filed.

The final document, CSBR 2.8 is attached, effective date being 9 May 2022. The documents can also be found here, https://wiki.cabforum.org/code_signing<https://urldefense.com/v3/__https:/wiki.cabforum.org/code_signing__;!!FJ-Y8qCqXTj2!N8eeuo8whq3tY-1x2agzevq9zlEJy2gxSKgdugLf5s5l5GWnwrQiP98WFEv_-_DZLNI$>.


Thanks, Bruce.

From: Bruce Morton
Sent: Thursday, April 7, 2022 1:30 PM
To: cscwg-public at cabforum.org
Subject: RE: Notice of Review Period: Ballot CSC-13 - Update to Subscriber Private Key Protection Requirements

This is a resend of the Notice of Review which includes the draft in “both in red-line and changes-accepted draft format, in Word and PDF versions.”

Thanks, Bruce.

From: Bruce Morton
Sent: Wednesday, April 6, 2022 3:45 PM
To: cscwg-public at cabforum.org<mailto:cscwg-public at cabforum.org>
Subject: Notice of Review Period: Ballot CSC-13 - Update to Subscriber Private Key Protection Requirements

NOTICE OF REVIEW PERIOD
This Review Notice is sent pursuant to Section 4.1 of the CA/Browser Forum’s Intellectual Property Rights Policy (v1.3). This Review Period of 30 days is for two Final Maintenance Guidelines. The complete Draft Maintenance Guidelines that are the subject of this Review Notice are attached to this email, both in red-line and changes-accepted draft format, in Word and PDF versions.

Summary of Review
Ballot for Review
Ballot CSC-13 - Update to Subscriber Private Key Protection Requirements
Start of Review Period
6 April 2022 at 15:45 Eastern Time
End of Review Period
6 May 2022 at 15:45 Eastern Time

Members with any Essential Claim(s) to exclude must forward a written Notice to Exclude Essential Claims to the Working Group Chair (email to dean.coclin at digicert.com<mailto:dean.coclin at digicert.com> ) and also submit a copy to the CA/B Forum public mailing list (email to cscwg-public at cabform.org<mailto:cscwg-public at cabform.org> ) before the end of the Review Period.
For details, please see the current version of the CA/Browser Forum Intellectual Property Rights Policy<https://urldefense.com/v3/__https:/cabforum.org/wp-content/uploads/CABF-IPR-Policy-v.1.3_4APR18.pdf__;!!FJ-Y8qCqXTj2!IIcC1cymYvD-x1EtkcMMowAMqmlw9GDlYOwH-TWnqUAkMA6IThBuvUpYdTygF8c2qMw$>.
(An optional template for submitting an Exclusion Notice is available at https://cabforum.org/wp-content/uploads/Template-for-Exclusion-Notice.pdf<https://urldefense.com/v3/__https:/cabforum.org/wp-content/uploads/Template-for-Exclusion-Notice.pdf__;!!FJ-Y8qCqXTj2!IIcC1cymYvD-x1EtkcMMowAMqmlw9GDlYOwH-TWnqUAkMA6IThBuvUpYdTyg-gU5mgo$>)


From: Bruce Morton
Sent: Wednesday, April 6, 2022 2:56 PM
To: cscwg-public at cabforum.org<mailto:cscwg-public at cabforum.org>
Subject: VOTING RESULTS: Ballot CSC-13: Update to Subscriber Private Key Protection Requirements

Voting has closed on CSCWG-13 and the ballot has passed.

Voting Results
Certificate Issuers
7 votes total, with no abstentions:

  *   7 Yes votes: Certum (Asseco), DigiCert, eMudhra, Entrust, HARICA, Sectigo, SSL.com
  *   0 No votes
  *   0 Abstentions

Certificate Consumers
1 vote total, with no abstentions

  *   1 Yes vote: Microsoft
  *   0 No votes
  *   0 Abstentions

Bylaw Requirements
1.     Bylaw 2.3(f) requires:
*      A "yes" vote by two-thirds of Certificate Issuer votes and by 50%-plus-one of Certificate Consumer votes. Votes to abstain are not counted for this purpose.
This requirement was MET for Certificate Issuers and MET for Certificate Consumers.
*      At least one Certificate Issuer and one Certificate Consumer Member must vote in favor of a ballot for the ballot to be adopted.
This requirement was MET.
2.    Bylaw 2.3(g) requires that a ballot result only be considered valid when “more than half of the number of currently active Members has participated”. Votes to abstain are counted in determining quorum. Half of the currently active members at the start of voting was 14, so the quorum was 15 for this ballot.
This requirement was MET.

This ballot now enters the IP Rights Review Period to permit members to review the ballot for relevant IP rights issues.


Bruce.

From: Cscwg-public <cscwg-public-bounces at cabforum.org<mailto:cscwg-public-bounces at cabforum.org>> On Behalf Of Ian McMillan via Cscwg-public
Sent: Wednesday, March 30, 2022 1:01 PM
To: cscwg-public at cabforum.org<mailto:cscwg-public at cabforum.org>
Subject: [EXTERNAL] [Cscwg-public] VOTING BEGINS: Ballot CSC-13: Update to Subscriber Private Key Protection Requirements

WARNING: This email originated outside of Entrust.
DO NOT CLICK links or attachments unless you trust the sender and know the content is safe.
________________________________
Ballot CSC-13: Update to Subscriber Private Key Protection Requirements<https://urldefense.com/v3/__https:/nam06.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwiki.cabforum.org*2Fcscwg*2Fcsc_13_-_update_to_subscriber_private_key_protection_requirements&data=04*7C01*7Cianmcm*40microsoft.com*7C31d96159f5ed42ea367808da0ceebaa5*7C72f988bf86f141af91ab2d7cd011db47*7C0*7C0*7C637836517169400423*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000&sdata=W9JW6jbaoIP9q5eo5kI9KtC*2FbyLkrPw4*2BknyEac9Fa8*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSU!!FJ-Y8qCqXTj2!MYP8nntl_HIl8acy3IX1BSy9KDw03s4s-Iq9hy2JIlgcyb3etHjF79amo1fImlNaYj4$>
Purpose of this ballot: Update the subscriber private key protection requirements in the Baseline Requirement for the Issuance and Management of Publicly-Trusted Code Signing Certificates v2.7. The following motion has been proposed by Ian McMillan of Microsoft and endorsed by Tim Hollebeek of DigiCert and Bruce Morton of Entrust.

- MOTION BEGINS -

This ballot updates the “Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates“ version 2.7 according to the attached redline which includes:


  *   Update section 16.3 “Subscriber Private Key Protection” to “Subscriber Private Key Protection and Verification”
  *   Update section 16.3 “Subscriber Private Key Protection” to include sub-sections “16.3.1 Subscriber Private Key Protection” and “16.3.2 Subscriber Private Key Verification”
  *   Update section 16.3 under new sub-section 16.3.1 to remove allowance of TPM key generation and software protected private key protection, and remove private key protection requirement differences between EV and non-EV Code Signing Certificates
  *   Update section 16.3 under new sub-section 16.3.1 to include the allowance of key generation and protection using a cloud-based key protection solution providing key generation and protection in a hardware crypto module that conforms to at least FIPS 140-2 Level 2 or Common Criteria EAL 4+
  *   Update section 16.3 under new sub-section 16.3.2 to include verification for Code Signing Certificates' private key generation and storage in a crypto module that meets or exceeds the requirements of FIPS 140-2 level 2 or Common Criteria EAL 4+ by the CAs. Include additional acceptable methods for verification including cloud-based key generation and protection solutions and a stipulation for CAs to satisfy this verification requirement with additional means specified in their CPS. Any additional means specified by a CA in their CPS, must be proposed to the CA/Browser Forum for inclusion into the acceptable methods for section 16.3.2 by November 15, 2022.

- MOTION ENDS -

The procedure for approval of this ballot is as follows:

Discussion (7 days)
Start Time: 2022-03-23, 13:00 Eastern Time (US)
End Time: 2022-03-30, 13:00 Eastern Time (US)

Vote for approval (7 days)
Start Time: 2022-03-30, 13:00 Eastern Time (US)
End Time: 2022-04-06, 13:00 Eastern Time (US)

Any email and files/attachments transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/cscwg-public/attachments/20220509/cef9b62f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Baseline Requirements for the Issuance and Management of Code Signing.v2.8_redline.pdf
Type: application/pdf
Size: 580148 bytes
Desc: Baseline Requirements for the Issuance and Management of Code Signing.v2.8_redline.pdf
URL: <http://lists.cabforum.org/pipermail/cscwg-public/attachments/20220509/cef9b62f/attachment-0002.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Baseline Requirements for the Issuance and Management of Code Signing.v2.8.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 142888 bytes
Desc: Baseline Requirements for the Issuance and Management of Code Signing.v2.8.docx
URL: <http://lists.cabforum.org/pipermail/cscwg-public/attachments/20220509/cef9b62f/attachment-0002.docx>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Baseline Requirements for the Issuance and Management of Code Signing.v2.8.pdf
Type: application/pdf
Size: 545615 bytes
Desc: Baseline Requirements for the Issuance and Management of Code Signing.v2.8.pdf
URL: <http://lists.cabforum.org/pipermail/cscwg-public/attachments/20220509/cef9b62f/attachment-0003.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Baseline Requirements for the Issuance and Management of Code Signing.v2.8_redline.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 166712 bytes
Desc: Baseline Requirements for the Issuance and Management of Code Signing.v2.8_redline.docx
URL: <http://lists.cabforum.org/pipermail/cscwg-public/attachments/20220509/cef9b62f/attachment-0003.docx>


More information about the Cscwg-public mailing list