<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=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><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:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* 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:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:12.0pt'>Here are the final minutes from the November 3, 2022 call:<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Attendees:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Andrea Holland<o:p></o:p></p><p class=MsoNormal>Atsushi Inaba<o:p></o:p></p><p class=MsoNormal>Bruce Morton<o:p></o:p></p><p class=MsoNormal>Corey Bonnell<o:p></o:p></p><p class=MsoNormal>Dean Coclin<o:p></o:p></p><p class=MsoNormal>Dimitris Zacharopoulos<o:p></o:p></p><p class=MsoNormal>Ian McMillan<o:p></o:p></p><p class=MsoNormal>Inigo Barreira<o:p></o:p></p><p class=MsoNormal>Mohit Kumar<o:p></o:p></p><p class=MsoNormal>Tim Crawford<o:p></o:p></p><p class=MsoNormal>Tim Hollebeek<o:p></o:p></p><p class=MsoNormal>Tomas Gustavsson<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dean read the antitrust statement.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- Signing Service Ballot<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bruce said that he received no further feedback and would like to push this to ballot. Tim and Ian offered to review and endorse, barring any issues found.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dimitris mentioned that one of the takeaways from the F2F was that there is ETSI guidance for remote QSCDs for activation and we should consider incorporating. Tim H. said that we should look at these requirements and incorporate compatible criteria in the CSBRs instead of requiring any associated audit regime. Dimitris said that approach may have IP issues.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bruce proposed that we look at that guidance after the initial ballot is pushed out. There was agreement that the remote QSCD standards should be looked at further by the group.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bruce said he will circulate the current PR (<a href="https://github.com/cabforum/code-signing/pull/12">https://github.com/cabforum/code-signing/pull/12</a>) for this ballot for review and call for endorsers.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bruce said that the NetSec requirements document describes requirements for CAs but is silent on Signing Services, and so we may want to consider removing the NetSec requirement for Signing Services. Tim said that while some things are CA-specific, there are many requirements which cover good security practices that would be applicable to Signing Services. Tim also agreed with Bruce that the NetSec requirements solely address CA keys, which is not useful for Signing Services.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bruce raised a concern that if we require adherence to the NetSec document as a whole, then there is much room for interpretation as to which sections are applicable to Signing Services. Dimitris agreed with Bruce and added that similar challenges have occurred with RA audits.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Ian asked if there are any ISO standards for cloud services. Tim said that there are not, and cloud services generally get the 2000-level security audit. Ian said that ISO 27001-7 audits for cloud services are common.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- Importing TLS BR text into CSBRs<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dimitris created a branch on GitHub(<a href="https://github.com/cabforum/code-signing/tree/importTLSBRrefs">https://github.com/cabforum/code-signing/tree/importTLSBRrefs</a>) to copy the TLS BR text to the CSBRs. He mentioned that there have been no significant issues thus far besides the references to the EV Guidelines, which will be handled in a second pass. He asked for volunteers for this effort.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Next meeting is November 17th.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Meeting adjourned.<o:p></o:p></p></div></body></html>