<div dir="ltr">Note, the redline doc doesn't quite align with this ballot text - look for "Multi-Ffactor" in the doc :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 28, 2018 at 3:25 PM, Tim Hollebeek via Public <span dir="ltr"><<a href="mailto:public@cabforum.org" target="_blank">public@cabforum.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="#0563C1" vlink="#954F72"><div class="m_-8512326469134851651WordSection1"><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Ballot 221: Two-Factor Authentication and Password Improvements<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Purpose of Ballot: The Network Security Working Group met a number of times to <u></u><u></u></p><p class="MsoNormal">improve the Network Security Guidelines requirements around authentication,<u></u><u></u></p><p class="MsoNormal">specifically by requiring two-factor authentication, and improving the password <u></u><u></u></p><p class="MsoNormal">requirements in line with more recent NIST guidelines.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">While CAs are encouraged to improve their password requirements as soon as <u></u><u></u></p><p class="MsoNormal">possible, a two year grace period is being given to allow organizations to <u></u><u></u></p><p class="MsoNormal">develop and implement policies to implement the improved requirements, especially<u></u><u></u></p><p class="MsoNormal">since some organizations may have to simultaneously comply with other<u></u><u></u></p><p class="MsoNormal">compliance frameworks that have not been updated yet and are based on older NIST <u></u><u></u></p><p class="MsoNormal">guidance about passwords.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">The following motion has been proposed by Tim Hollebeek of DigiCert and endorsed <u></u><u></u></p><p class="MsoNormal">by Dimitris Zacharopoulos of Harica and Neil Dunbar of TrustCor.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">— MOTION BEGINS –<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">This ballot modifies the “Network and Certificate System Security Requirements” <u></u><u></u></p><p class="MsoNormal">as follows, based upon Version 1.1:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">In the definitions, add a definition for Multifactor Authentication:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">"Multi-Factor Authentication: An authentication mechanism consisting of two or <u></u><u></u></p><p class="MsoNormal">more of the following independent categories of credentials (i.e. factors) to <u></u><u></u></p><p class="MsoNormal">verify the user’s identity for a login or other transaction: something you know <u></u><u></u></p><p class="MsoNormal">(knowledge factor), something you have (possession factor), and something you <u></u><u></u></p><p class="MsoNormal">are (inherence factor). Each factor must be independent. Certificate-based <u></u><u></u></p><p class="MsoNormal">authentication can be used as part of Multifactor Authentication only if the <u></u><u></u></p><p class="MsoNormal">private key is stored in a Secure Key Storage Device."<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Add a definition for Secure Key Storage Device:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">"Secure Key Storage Device: A device certified as meeting at least FIPS 140-2<u></u><u></u></p><p class="MsoNormal">level 2 overall, level 3 physical, or Common Criteria (EAL 4+)."<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">In section 1.j., capitalize Multi-Factor Authentication, and strike the <u></u><u></u></p><p class="MsoNormal">parenthetical reference to subsection 2.n.(ii).<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">In section 2.f., add "(for accountability purposes, group accounts or shared<u></u><u></u></p><p class="MsoNormal">role credentials SHALL NOT be used)" after "authenticate to Certificate Systems".<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Change section 2.g. to read:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">"g. If an authentication control used by a Trusted Role is a username and password, <u></u><u></u></p><p class="MsoNormal"> then, where technically feasible, implement the following controls:<u></u><u></u></p><p class="MsoNormal"> i. For accounts that are accessible only within Secure Zones or High Security <u></u><u></u></p><p class="MsoNormal"> Zones, require that passwords have at least twelve (12) characters; <u></u><u></u></p><p class="MsoNormal"> ii. For accounts that are accessible from outside a Secure Zone or High Security <u></u><u></u></p><p class="MsoNormal"> Zone, require Multi-Factor Authentication, with passwords that have at least <u></u><u></u></p><p class="MsoNormal"> eight (8) characters and are not be one of the user's previous four (4) <u></u><u></u></p><p class="MsoNormal"> passwords; and implement account lockout for failed access attempts in <u></u><u></u></p><p class="MsoNormal"> accordance with subsection k;<u></u><u></u></p><p class="MsoNormal"> iii. When developing password policies, CAs SHOULD take into account the password <u></u><u></u></p><p class="MsoNormal"> guidance in NIST 800-63B Appendix A.<u></u><u></u></p><p class="MsoNormal"> iv. If passwords are required to be changed periodically, that period SHOULD be <u></u><u></u></p><p class="MsoNormal"> at least two years. Effective April 1, 2020, if passwords are required to <u></u><u></u></p><p class="MsoNormal"> be changed periodically, that period SHALL be at least two years."<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">In section 2.h., change "Require" to "Have a policy that requires"<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">In section 2.i., change "Configure" to "Have a procedure to configure"<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Change section 2.k. to read:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">"k. Lockout account access to Certificate Systems after no more than five (5) failed access attempts, provided that this security measure:<u></u><u></u></p><p class="MsoNormal"> i. is supported by the Certificate System,<u></u><u></u></p><p class="MsoNormal"> ii. Cannot be leveraged for a denial of service attack, and<u></u><u></u></p><p class="MsoNormal"> iii. does not weaken the security of this authentication control;"<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Change section 2.n. to read:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">"Enforce Multi-Factor Authentication for all Trusted Role accounts on Certificate<u></u><u></u></p><p class="MsoNormal">Systems (including those approving the issuance of a Certificate, which equally<u></u><u></u></p><p class="MsoNormal">applies to Delegated Third Parties) that are accessible from outside a Secure Zone<u></u><u></u></p><p class="MsoNormal">or High Security Zone; and”<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">— MOTION ENDS –<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">The procedure for approval of this ballot is as follows:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Discussion (7+ days)<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Start Time: 2018-03-28 15:30:00 EDT<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">End Time: after 2018-04-04 15:30:00 EDT<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Vote for approval (7 days)<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Start Time: TBD<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">End Time: TBD<u></u><u></u></p></div></div><br>______________________________<wbr>_________________<br>
Public mailing list<br>
<a href="mailto:Public@cabforum.org">Public@cabforum.org</a><br>
<a href="https://cabforum.org/mailman/listinfo/public" rel="noreferrer" target="_blank">https://cabforum.org/mailman/<wbr>listinfo/public</a><br>
<br></blockquote></div><br></div>