<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.elementtoproof
{mso-style-name:elementtoproof;}
p.elementtoproof1, li.elementtoproof1, div.elementtoproof1
{mso-style-name:elementtoproof1;
margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Aptos",sans-serif;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:948508067;
mso-list-type:hybrid;
mso-list-template-ids:-110727372 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:2109889800;
mso-list-template-ids:-1581743896;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><div><p class=MsoNormal><span style='font-family:"Aptos",sans-serif;color:black'>I’m not sure retaining the clause starting with “A CA identifying a high risk application under this section…” provides much clarity or value. Two reasons:<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Aptos",sans-serif;color:black'><o:p> </o:p></span></p><ol style='margin-top:0in' start=1 type=1><li class=MsoListParagraph style='color:black;margin-left:0in;mso-list:l0 level1 lfo2'><span style='font-family:"Aptos",sans-serif'>All other language concerning high risk checks in section 4.2.1 has been struck. The turn of phrase “under this section” implies there are additional requirements defined in this section, but there are none. This will likely result in confusion.<o:p></o:p></span></li><li class=MsoListParagraph style='color:black;margin-left:0in;mso-list:l0 level1 lfo2'><span style='font-family:"Aptos",sans-serif'>The requirement for the CA to confirm that the Applicant has not been the victim of multiple Takeover Attacks is still present in section 4.2.2. I’m not sure we need a reference to that requirement in another section.<o:p></o:p></span></li></ol><p class=MsoNormal><span style='font-family:"Aptos",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Aptos",sans-serif;color:black'>I’m partial to removing the clause entirely. However, if the group agrees that it should be retained, then I think at the very least the language needs to be modified to no longer imply that there are (non-existent) requirements in the current section.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Aptos",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Aptos",sans-serif;color:black'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Aptos",sans-serif;color:black'>Corey<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Aptos",sans-serif;color:black'><o:p> </o:p></span></p></div><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="98%" align=center></div><div id=divRplyFwdMsg><p class=MsoNormal><b><span style='color:black'>From:</span></b><span style='color:black'> Cscwg-public <cscwg-public-bounces@cabforum.org> on behalf of Martijn Katerbarg via Cscwg-public <cscwg-public@cabforum.org><br><b>Sent:</b> Wednesday, November 22, 2023 9:22 AM<br><b>To:</b> Bruce Morton <bruce.morton@entrust.com>; cscwg-public@cabforum.org <cscwg-public@cabforum.org>; Tim Hollebeek <tim.hollebeek@digicert.com><br><b>Subject:</b> Re: [Cscwg-public] Ballot CSC-??: High Risk Requirements Update</span> <o:p></o:p></p><div><p class=MsoNormal> <o:p></o:p></p></div></div><p>Hi Bruce,<br><br>Going for the full clarification:<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p>The PR show that:<span style='font-size:10.0pt'><o:p></o:p></span></p><table class=MsoNormalTable border=0 cellspacing=3 cellpadding=0><tr><td style='padding:.75pt .75pt .75pt .75pt'><p>”Prior to issuing a Code Signing Certificate, each CA SHOULD check at least one database containing information about known or suspected producers, publishers, or distributors of Suspect Code, as identified or indicated by an Anti-Malware Organization and any database of deceptive names maintained by an Application Software Provider. The CA MUST determine whether the entity is identified as requesting a Code Signing Certificate from a High Risk Region of Concern. The CA MUST also maintain and check an internal database listing Certificates revoked due to Code Signatures on Suspect Code and previous certificate requests rejected by the CA. ”<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p>Is being replaced with:<span style='font-size:10.0pt'><o:p></o:p></span></p></td></tr></table><p class=MsoNormal><span style='display:none'><o:p> </o:p></span></p><table class=MsoNormalTable border=0 cellspacing=3 cellpadding=0><tr><td style='padding:.75pt .75pt .75pt .75pt'><p>”Prior to issuing a Code Signing Certificate, each CA SHOULD check at least one database containing information about known or suspected producers, publishers, or distributors of Suspect Code, as identified or indicated by an Anti-Malware Organization and any database of deceptive names maintained by an Application Software Provider. The CA MUST also maintain and check an internal database listing Certificates revoked due to Code Signatures on Suspect Code and previous certificate requests rejected by the CA. ”<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p><span class=elementtoproof>That makes sense. Then the PR goes on to additionally remove:</span><br><span class=elementtoproof>“A CA identifying a high risk application under this section MUST follow the additional procedures defined in [Section 4.2.2](#422-approval-or-rejection-of-certificate-applications) of this document to ensure that the applicant will protect its Private Keys and not sign Suspect Code.”</span><span style='font-size:10.0pt'><o:p></o:p></span></p><p><br>That’s the part I think should remain.<span style='font-size:10.0pt'><o:p></o:p></span></p></td></tr><tr><td style='padding:.75pt .75pt .75pt .75pt'><p><br>So yes, I think we’re on the same page with that one <span style='font-family:"Segoe UI Emoji",sans-serif'>😊</span><br><br>Regards,<br><br>Martijn<span style='font-size:10.0pt'><o:p></o:p></span></p></td></tr></table><p style='margin-bottom:12.0pt'><span style='font-size:10.0pt'><o:p> </o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><div id="x_mail-editor-reference-message-container"><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p style='margin-bottom:12.0pt'><b><span style='font-size:12.0pt;font-family:"Aptos",sans-serif;color:black'>From: </span></b><span style='font-size:12.0pt;font-family:"Aptos",sans-serif;color:black'>Bruce Morton <Bruce.Morton@entrust.com><br><b>Date: </b>Wednesday, 22 November 2023 at 14:34<br><b>To: </b>Martijn Katerbarg <martijn.katerbarg@sectigo.com>, cscwg-public@cabforum.org <cscwg-public@cabforum.org>, Tim Hollebeek (tim.hollebeek@digicert.com) <tim.hollebeek@digicert.com><br><b>Subject: </b>RE: Ballot CSC-??: High Risk Requirements Update</span><span style='font-size:10.0pt'><o:p></o:p></span></p></div><p>Hi Martijn,<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p>For clarification, for the following two paragraphs which have been deleted, you would like the first deleted and the second to remain:<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p style='margin-left:.5in'><s><span style='color:red'>Prior to issuing a Code Signing Certificate, each CA SHOULD check at least one database containing information about known or suspected producers, publishers, or distributors of Suspect Code, as identified or indicated by an Anti-Malware Organization and any database of deceptive names maintained by an Application Software Provider. The CA MUST determine whether the entity is identified as requesting a Code Signing Certificate from a High Risk Region of Concern. The CA MUST also maintain and check an internal database listing Certificates revoked due to Code Signatures on Suspect Code and previous certificate requests rejected by the CA.</span></s><span style='font-size:10.0pt'><o:p></o:p></span></p><p style='margin-left:.5in'> <span style='font-size:10.0pt'><o:p></o:p></span></p><p style='margin-left:.5in'>A CA identifying a high risk application under this section MUST follow the additional procedures defined in [Section 4.2.2](#422-approval-or-rejection-of-certificate-applications) of this document to ensure that the applicant will protect its Private Keys and not sign Suspect Code.<span style='font-size:10.0pt'><o:p></o:p></span></p><p style='margin-left:.5in'> <span style='font-size:10.0pt'><o:p></o:p></span></p><p>If so, I agree to this change. Please confirm.<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p><a id=OWAAMF9C3148C7DB4404DBBB23DFFEDAB8A4F href="mailto:tim.hollebeek@digicert.com"><span style='font-family:"Calibri",sans-serif;text-decoration:none'>@Tim Hollebeek (tim.hollebeek@digicert.com)</span></a> does this work for you?<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p>Thanks, Bruce.<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p><b>From:</b> Martijn Katerbarg <martijn.katerbarg@sectigo.com><br><b>Sent:</b> Wednesday, November 22, 2023 3:32 AM<br><b>To:</b> Bruce Morton <Bruce.Morton@entrust.com>; cscwg-public@cabforum.org<br><b>Subject:</b> [EXTERNAL] Re: Ballot CSC-??: High Risk Requirements Update<span style='font-size:10.0pt'><o:p></o:p></span></p></div><p><span style='font-size:10.0pt'> <o:p></o:p></span></p><p>Bruce, I’ve added a single comment on the PR, as I think we’ve removed one paragraph too much. Other than that, I’m also happy to endorse.<span style='font-size:10.0pt'><o:p></o:p></span></p><p><br>Regards,<br><br>Martijn<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><div id="x_mail-editor-reference-message-container"><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p><b><span style='font-size:12.0pt;font-family:"Aptos",sans-serif;color:black'>From: </span></b><span style='font-size:12.0pt;font-family:"Aptos",sans-serif;color:black'>Cscwg-public <</span><span style='font-size:12.0pt;font-family:"Aptos",sans-serif'><a href="mailto:cscwg-public-bounces@cabforum.org">cscwg-public-bounces@cabforum.org</a><span style='color:black'>> on behalf of Bruce Morton via Cscwg-public <</span><a href="mailto:cscwg-public@cabforum.org">cscwg-public@cabforum.org</a><span style='color:black'>><br><b>Date: </b>Tuesday, 21 November 2023 at 20:25<br><b>To: </b></span><a href="mailto:cscwg-public@cabforum.org">cscwg-public@cabforum.org</a><span style='color:black'> <</span><a href="mailto:cscwg-public@cabforum.org">cscwg-public@cabforum.org</a><span style='color:black'>><br><b>Subject: </b>[Cscwg-public] Ballot CSC-??: High Risk Requirements Update</span></span><span style='font-size:10.0pt'><o:p></o:p></span></p></div><div style='border:solid black 1.0pt;padding:2.0pt 2.0pt 2.0pt 2.0pt'><p style='line-height:12.0pt;background:#FAFA03'><span style='font-size:10.0pt;color:black'>CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.</span><span style='font-size:10.0pt'><o:p></o:p></span></p></div><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p>Here is a draft of the High Risk Requirements update ballot. Looking for comments and 2 endorsers. There is no future effectivity date proposed, since the ballot does not add new requirements.<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p>Thanks, Bruce.<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p><b><span style='font-size:13.5pt;font-family:"Arial",sans-serif;color:black'>Purpose of the Ballot</span></b><o:p></o:p></p><p>This ballot updates the “Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates“ version 3.4 in order to clarify language regarding Signing Service and signing requests. The main goals of this ballot are to:<span style='font-size:10.0pt'><o:p></o:p></span></p><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'>Remove references to High Risk Certificate Request, since the CSBRs do not provide any actions for a high risk application.<span style='font-size:10.0pt'><o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'>Remove references to High Risk Region of Concern, since the CSBR appendix has never been populated.<span style='font-size:10.0pt'><o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'>Remove rules for a Takeover Attack to require the Subscriber to generate keys in a crypto device, since crypto device key generation is now a baseline requirement for all code signing certificates.<span style='font-size:10.0pt'><o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'>Remove option to transfer private key which has been generated in software.<span style='font-size:10.0pt'><o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'>Cleanup to remove Subscriber key generation option which expired effective 1 June 2023.<span style='font-size:10.0pt'><o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo1'>Cleanup to remove “any other method” to verify the Subscriber key was generated in a crypto device, since this option expired 1 June 2023.<span style='font-size:10.0pt'><o:p></o:p></span></li></ol><p>The following motion has been proposed by Bruce Morton of Entrust and endorsed by ?? and ??.<span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p><b><span style='font-size:13.5pt;font-family:"Arial",sans-serif;color:#0E101A'>MOTION BEGINS</span></b><o:p></o:p></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p class=elementtoproof1>This ballot updates the “Baseline Requirements for the Issuance and Management of Publicly‐Trusted Code Signing Certificates” ("Code Signing Baseline Requirements") based on version 3.4. MODIFY the Code Signing Baseline Requirements as specified in the following redline: <a href="https://url.avanan.click/v2/___https:/github.com/cabforum/code-signing/pull/31/files___.YXAzOmRpZ2ljZXJ0OmE6bzpiNzQxNmRlMjNkMjlmN2JiMWRlMmQwZDlhZGFjN2YzNDo2OjE1MzA6MTgzMDJkZjgwZjQ5NDU3MzljY2EyODY5MGE0NzcwZDExY2ExMDE1ZWE5ZWUyOTNjNmEwMjQxYWYwMGQ5NWE4YTpoOkY" title="Protected by Avanan: https://github.com/cabforum/code-signing/pull/31/files">https://github.com/cabforum/code-signing/pull/31/files</a><span style='font-size:10.0pt'><o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p><b><span style='font-size:13.5pt;font-family:"Arial",sans-serif;color:#0E101A'>MOTION ENDS</span></b><o:p></o:p></p><p>The procedure for this ballot is as follows:<span style='font-size:10.0pt'> Discussion (7 days)<o:p></o:p></span></p><p><span style='font-size:10.0pt'> <o:p></o:p></span></p><p style='margin-left:52.2pt'><span style='font-size:10.0pt'>1.</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span style='font-size:10.0pt'>Start Time: TBD<o:p></o:p></span></p><p style='margin-left:52.2pt'><span style='font-size:10.0pt'>2.</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span style='font-size:10.0pt'>End Time: TBD<o:p></o:p></span></p><p><span style='font-size:10.0pt'> <o:p></o:p></span></p><p><span style='font-size:10.0pt'>Vote for approval (7 days)<o:p></o:p></span></p><p><span style='font-size:10.0pt'> <o:p></o:p></span></p><p style='margin-left:52.2pt'><span style='font-size:10.0pt'>3.</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span style='font-size:10.0pt'>Start Time: TBD<o:p></o:p></span></p><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:52.2pt'><span style='font-size:10.0pt'>4.</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><span style='font-size:10.0pt'>End Time: TBD<o:p></o:p></span></p><p> <span style='font-size:10.0pt'><o:p></o:p></span></p><p><i>Any email and files/attachments transmitted with it 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. <u>Please notify Entrust immediately and delete the message from your system.</u></i><span style='font-size:10.0pt'><o:p></o:p></span></p></div></div></div></body></html>