<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:新細明體;
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:細明體;
panose-1:2 2 5 9 0 0 0 0 0 0;}
@font-face
{font-family:細明體;
panose-1:2 2 5 9 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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@新細明體";
panose-1:2 2 5 0 0 0 0 0 0 0;}
@font-face
{font-family:"\@細明體";
panose-1:2 2 5 9 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML 預設格式 字元";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:細明體;
color:black;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTML
{mso-style-name:"HTML 預設格式 字元";
mso-style-priority:99;
mso-style-link:"HTML 預設格式";
font-family:"Courier New";
color:black;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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 bgcolor=white lang=ZH-TW link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:#1F497D'>Chunghwa Telecom Votes “Yes” to ballot SC3 version 2.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='text-indent:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:#1F497D'>Li-Chun Chen<o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> Public [mailto:public-bounces@cabforum.org] <b>On Behalf Of </b>Dimitris Zacharopoulos via Public<br><b>Sent:</b> Thursday, August 16, 2018 4:01 PM<br><b>To:</b> CA/Browser Forum Public Discussion List<br><b>Subject:</b> [</span><span style='font-size:10.0pt;font-family:"新細明體","serif";color:windowtext'>外部郵件</span><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>] Re: [cabfpub] Voting has started on Ballot SC3 version 2<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US>HARICA votes "yes" to ballot SC3 version 2.<br><br>Dimitris.<br><br>On 13/8/2018 7:27 μμ, Kirk Hall via Public wrote:<o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>See text and link below. Voting ends on Thursday, August 16, 2018 at 11:45 am Eastern.</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'> </span><span lang=EN-US><o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Servercert-wg [<a href="mailto:servercert-wg-bounces@cabforum.org">mailto:servercert-wg-bounces@cabforum.org</a>] <b>On Behalf Of </b>Tim Hollebeek via Servercert-wg<br><b>Sent:</b> Thursday, August 9, 2018 8:48 AM<br><b>To:</b> CA/Browser Forum Public Discussion List <<a href="mailto:public@cabforum.org">public@cabforum.org</a>><br><b>Cc:</b> <a href="mailto:servercert-wg@cabforum.org">servercert-wg@cabforum.org</a><br><b>Subject:</b> [EXTERNAL][Servercert-wg] Voting begins: Ballot SC3 version 2<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US><a href="https://github.com/cabforum/documents/compare/SC3-PasswordChangesDieDieDie?expand=1">https://github.com/cabforum/documents/compare/SC3-PasswordChangesDieDieDie?expand=1</a><o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Ballot SC3: Two-Factor Authentication and Password Improvements<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Purpose of Ballot: The Network Security Working Group met a number of times to <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>improve the Network Security Guidelines requirements around authentication,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>specifically by requiring two-factor authentication, and improving the password <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>requirements in line with more recent NIST guidelines.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>While CAs are encouraged to improve their password requirements as soon as <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>possible, a two year grace period is being given to allow organizations to <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>develop and implement policies to implement the improved requirements, especially<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>since some organizations may have to simultaneously comply with other<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>compliance frameworks that have not been updated yet and are based on older NIST <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>guidance about passwords.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>The following motion has been proposed by Tim Hollebeek of DigiCert and endorsed <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>by Dimitris Zacharopoulos of Harica and Neil Dunbar of TrustCor.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>— MOTION BEGINS –<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>This ballot modifies the “Network and Certificate System Security Requirements” <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>as follows, based upon Version 1.1:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>In the definitions, add a definition for Multi-Factor Authentication:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>"Multi-Factor Authentication: An authentication mechanism consisting of two or <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>more of the following independent categories of credentials (i.e. factors) to <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>verify the user’s identity for a login or other transaction: something you know <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>(knowledge factor), something you have (possession factor), and something you <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>are (inherence factor). Each factor must be independent. Certificate-based <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>authentication can be used as part of Multifactor Authentication only if the <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>private key is stored in a Secure Key Storage Device."<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Capitalize all instances of the defined term "Multi-Factor Authentication".<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Add a definition for Secure Key Storage Device:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>"Secure Key Storage Device: A device certified as meeting at least FIPS 140-2<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>level 2 overall, level 3 physical, or Common Criteria (EAL 4+)."<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>In section 1.j., capitalize Multi-Factor Authentication, and strike the <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>parenthetical reference to subsection 2.n.(ii).<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>In section 2.f., add "(for accountability purposes, group accounts or shared<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>role credentials SHALL NOT be used)" after "authenticate to Certificate Systems".<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Change section 2.g. to read:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>"g. If an authentication control used by a Trusted Role is a username and password, <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> then, where technically feasible, implement the following controls:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> i. For accounts that are accessible only within Secure Zones or High Security <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> Zones, require that passwords have at least twelve (12) characters; <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> ii. For authentications which cross a zone boundary into a Secure Zone or High <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> Security Zone, require Multi-Factor Authentication. For accounts accessible <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> from outside a Secure Zone or High Security Zone require passwords that have <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> at least eight (8) characters and are not be one of the user's previous <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> four (4) passwords; and implement account lockout for failed access attempts <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> in accordance with subsection k;<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> iii. When developing password policies, CAs SHOULD take into account the password <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> guidance in NIST 800-63B Appendix A.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> iv. Frequent password changes have been shown to cause users to select less <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> secure passwords. If the CA has any policy that specifies routine periodic <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> password changes, that period SHOULD NOT be less than two years. Effective <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> April 1, 2020, if the CA has any policy that requires routine periodic password <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> changes, that period SHALL NOT be less than two years.<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>In section 2.h., change "Require" to "Have a policy that requires"<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>In section 2.i., change "Configure" to "Have a procedure to configure"<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Change section 2.k. to read:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>"k. Lockout account access to Certificate Systems after no more than five (5) failed <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> access attempts, provided that this security measure:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> i. is supported by the Certificate System,<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> ii. Cannot be leveraged for a denial of service attack, and<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> iii. does not weaken the security of this authentication control;"<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Change section 2.n. to read:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>"Enforce Multi-Factor Authentication for all Trusted Role accounts on Certificate<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Systems (including those approving the issuance of a Certificate, which equally<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>applies to Delegated Third Parties) that are accessible from outside a Secure Zone<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>or High Security Zone; and"<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>— MOTION ENDS –<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>The procedure for approval of this ballot is as follows:<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Discussion (7+ days)<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Start Time: 2018-07-26 17:45 Eastern<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>End Time: 2018-08-09 11:45 Eastern<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Vote for approval (7 days)<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>Start Time: 2018-08-09 11:45 Eastern<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span lang=EN-US>End Time: 2018-08-16 11:45 Eastern<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"新細明體","serif"'><br><br><br><o:p></o:p></span></p><pre><span lang=EN-US>_______________________________________________<o:p></o:p></span></pre><pre><span lang=EN-US>Public mailing list<o:p></o:p></span></pre><pre><span lang=EN-US><a href="mailto:Public@cabforum.org">Public@cabforum.org</a><o:p></o:p></span></pre><pre><span lang=EN-US><a href="https://cabforum.org/mailman/listinfo/public">https://cabforum.org/mailman/listinfo/public</a><o:p></o:p></span></pre></blockquote><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"新細明體","serif"'><o:p> </o:p></span></p></div></body></html><br><html><div><div>本信件可能包含中華電信股份有限公司機密資訊,非指定之收件者,請勿蒐集、處理或利用本信件內容,並請銷毀此信件. 如為指定收件者,應確實保護郵件中本公司之營業機密及個人資料,不得任意傳佈或揭露,並應自行確認本郵件之附檔與超連結之安全性,以共同善盡資訊安全與個資保護責任. </div><div>Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.</div></div><div><br></div><div><br></div></html>