<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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
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">
<div class="WordSection1">
<p class="MsoNormal">I’m having internal conversations with concerns regarding section iv which states:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><i>“ iv. If passwords are required to be changed periodically, that period SHOULD be at least two years. Effective April 1, 2020, if passwords are required to be changed periodically, that period SHALL be at least two years."<o:p></o:p></i></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sorry I didn’t catch this during the discussion period but the language should be adjusted. A period of at
<u>least</u> two years means you wait a <u>minimum</u> of two years. Can we use words like maximum?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The reference to NIST SP 800-63 makes us think we want to emphasize stronger passwords while minimizing the frequency with which those secrets are changed. That is what the NIST guidance calls for. The language “if passwords are required
to be changed…” also makes us think this. Basically, password changes are optional, but if you require them to be changed, two years is the
<u>minimum</u> amount of time to wait before changing them.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Also, why have separate policies for different security zones? A 12-character password of seahawks2018 shouldn’t be considered better than an 8 digit randomly generated one.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I agree with Wayne that a redlined version should be provided for a vote as it’s difficult to clearly see the changes. I’m inclined to vote No at this point and apologize for not looking harder at this in the discussion period.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks, Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Public <public-bounces@cabforum.org> <b>On Behalf Of
</b>Tim Hollebeek via Public<br>
<b>Sent:</b> Thursday, May 17, 2018 2:48 PM<br>
<b>To:</b> CA/Browser Forum Public Discussion List <public@cabforum.org><br>
<b>Subject:</b> [cabfpub] Voting Begins: Ballot 221: Two-Factor Authentication and Password Improvements<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ballot 221: Two-Factor Authentication and Password Improvements<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Purpose of Ballot: The Network Security Working Group met a number of times to
<o:p></o:p></p>
<p class="MsoNormal">improve the Network Security Guidelines requirements around authentication,<o:p></o:p></p>
<p class="MsoNormal">specifically by requiring two-factor authentication, and improving the password
<o:p></o:p></p>
<p class="MsoNormal">requirements in line with more recent NIST guidelines.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">While CAs are encouraged to improve their password requirements as soon as
<o:p></o:p></p>
<p class="MsoNormal">possible, a two year grace period is being given to allow organizations to
<o:p></o:p></p>
<p class="MsoNormal">develop and implement policies to implement the improved requirements, especially<o:p></o:p></p>
<p class="MsoNormal">since some organizations may have to simultaneously comply with other<o:p></o:p></p>
<p class="MsoNormal">compliance frameworks that have not been updated yet and are based on older NIST
<o:p></o:p></p>
<p class="MsoNormal">guidance about passwords.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The following motion has been proposed by Tim Hollebeek of DigiCert and endorsed
<o:p></o:p></p>
<p class="MsoNormal">by Dimitris Zacharopoulos of Harica and Neil Dunbar of TrustCor.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">— MOTION BEGINS –<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This ballot modifies the “Network and Certificate System Security Requirements”
<o:p></o:p></p>
<p class="MsoNormal">as follows, based upon Version 1.1:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the definitions, add a definition for Multi-Factor Authentication:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"Multi-Factor Authentication: An authentication mechanism consisting of two or
<o:p></o:p></p>
<p class="MsoNormal">more of the following independent categories of credentials (i.e. factors) to
<o:p></o:p></p>
<p class="MsoNormal">verify the user’s identity for a login or other transaction: something you know
<o:p></o:p></p>
<p class="MsoNormal">(knowledge factor), something you have (possession factor), and something you
<o:p></o:p></p>
<p class="MsoNormal">are (inherence factor). Each factor must be independent. Certificate-based
<o:p></o:p></p>
<p class="MsoNormal">authentication can be used as part of Multifactor Authentication only if the
<o:p></o:p></p>
<p class="MsoNormal">private key is stored in a Secure Key Storage Device."<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Capitalize all instances of the defined term "Multi-Factor Authentication".<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Add a definition for Secure Key Storage Device:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"Secure Key Storage Device: A device certified as meeting at least FIPS 140-2<o:p></o:p></p>
<p class="MsoNormal">level 2 overall, level 3 physical, or Common Criteria (EAL 4+)."<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In section 1.j., capitalize Multi-Factor Authentication, and strike the
<o:p></o:p></p>
<p class="MsoNormal">parenthetical reference to subsection 2.n.(ii).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In section 2.f., add "(for accountability purposes, group accounts or shared<o:p></o:p></p>
<p class="MsoNormal">role credentials SHALL NOT be used)" after "authenticate to Certificate Systems".<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Change section 2.g. to read:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"g. If an authentication control used by a Trusted Role is a username and password,
<o:p></o:p></p>
<p class="MsoNormal"> then, where technically feasible, implement the following controls:<o:p></o:p></p>
<p class="MsoNormal"> i. For accounts that are accessible only within Secure Zones or High Security
<o:p></o:p></p>
<p class="MsoNormal"> Zones, require that passwords have at least twelve (12) characters;
<o:p></o:p></p>
<p class="MsoNormal"> ii. For authentications which cross a zone boundary into a Secure Zone or High
<o:p></o:p></p>
<p class="MsoNormal"> Security Zone, require Multi-Factor Authentication. For accounts accessible
<o:p></o:p></p>
<p class="MsoNormal"> from outside a Secure Zone or High Security Zone require passwords that have
<o:p></o:p></p>
<p class="MsoNormal"> at least eight (8) characters and are not be one of the user's previous
<o:p></o:p></p>
<p class="MsoNormal"> four (4) passwords; and implement account lockout for failed access attempts
<o:p></o:p></p>
<p class="MsoNormal"> in accordance with subsection k;<o:p></o:p></p>
<p class="MsoNormal"> iii. When developing password policies, CAs SHOULD take into account the password
<o:p></o:p></p>
<p class="MsoNormal"> guidance in NIST 800-63B Appendix A.<o:p></o:p></p>
<p class="MsoNormal"> iv. If passwords are required to be changed periodically, that period SHOULD be
<o:p></o:p></p>
<p class="MsoNormal"> at least two years. Effective April 1, 2020, if passwords are required to
<o:p></o:p></p>
<p class="MsoNormal"> be changed periodically, that period SHALL be at least two years."<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In section 2.h., change "Require" to "Have a policy that requires"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In section 2.i., change "Configure" to "Have a procedure to configure"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Change section 2.k. to read:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"k. Lockout account access to Certificate Systems after no more than five (5) failed
<o:p></o:p></p>
<p class="MsoNormal"> access attempts, provided that this security measure:<o:p></o:p></p>
<p class="MsoNormal"> i. is supported by the Certificate System,<o:p></o:p></p>
<p class="MsoNormal"> ii. Cannot be leveraged for a denial of service attack, and<o:p></o:p></p>
<p class="MsoNormal"> iii. does not weaken the security of this authentication control;"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Change section 2.n. to read:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">"Enforce Multi-Factor Authentication for all Trusted Role accounts on Certificate<o:p></o:p></p>
<p class="MsoNormal">Systems (including those approving the issuance of a Certificate, which equally<o:p></o:p></p>
<p class="MsoNormal">applies to Delegated Third Parties) that are accessible from outside a Secure Zone<o:p></o:p></p>
<p class="MsoNormal">or High Security Zone; and"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">— MOTION ENDS –<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The procedure for approval of this ballot is as follows:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Discussion (7+ days)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Start Time: 2018-03-28 15:00:00 EDT<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">End Time: 2018-05-17 17:45:00 EDT<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Vote for approval (7 days)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Start Time: 2018-05-17 17:45:00 EDT<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">End Time: 2018-05-24 17:45:00 EDT<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>