Kamu SM votes YES on Ballot 221.
Regards, Dr. Tamer ERGUN E-İmza Teknolojileri Bölüm Sorumlusu TÜBİTAK/BİLGEM/Kamu SM Çamlıca Mahallesi 408. Cadde No: 136 C Blok 5. Kat Yenimahalle/Ankara <http://www.tubitak.gov.tr/> www.tubitak.gov.tr tamer.er...@kamusm.gov.tr <mailto:tamer.er...@kamusm.gov.tr> <http://www.kamusm.gov.tr/sorumlulukreddi.jsp> Sorumluluk Reddi / Disclaimer From: Public [mailto:public-boun...@cabforum.org] On Behalf Of Tim Hollebeek via Public Sent: 18 May 2018 00:48 To: CA/Browser Forum Public Discussion List Subject: [cabfpub] Voting Begins: Ballot 221: Two-Factor Authentication and Password Improvements Ballot 221: Two-Factor Authentication and Password Improvements Purpose of Ballot: The Network Security Working Group met a number of times to improve the Network Security Guidelines requirements around authentication, specifically by requiring two-factor authentication, and improving the password requirements in line with more recent NIST guidelines. While CAs are encouraged to improve their password requirements as soon as possible, a two year grace period is being given to allow organizations to develop and implement policies to implement the improved requirements, especially since some organizations may have to simultaneously comply with other compliance frameworks that have not been updated yet and are based on older NIST guidance about passwords. The following motion has been proposed by Tim Hollebeek of DigiCert and endorsed by Dimitris Zacharopoulos of Harica and Neil Dunbar of TrustCor. - MOTION BEGINS - This ballot modifies the "Network and Certificate System Security Requirements" as follows, based upon Version 1.1: In the definitions, add a definition for Multi-Factor Authentication: "Multi-Factor Authentication: An authentication mechanism consisting of two or more of the following independent categories of credentials (i.e. factors) to verify the user's identity for a login or other transaction: something you know (knowledge factor), something you have (possession factor), and something you are (inherence factor). Each factor must be independent. Certificate-based authentication can be used as part of Multifactor Authentication only if the private key is stored in a Secure Key Storage Device." Capitalize all instances of the defined term "Multi-Factor Authentication". Add a definition for Secure Key Storage Device: "Secure Key Storage Device: A device certified as meeting at least FIPS 140-2 level 2 overall, level 3 physical, or Common Criteria (EAL 4+)." In section 1.j., capitalize Multi-Factor Authentication, and strike the parenthetical reference to subsection 2.n.(ii). In section 2.f., add "(for accountability purposes, group accounts or shared role credentials SHALL NOT be used)" after "authenticate to Certificate Systems". Change section 2.g. to read: "g. If an authentication control used by a Trusted Role is a username and password, then, where technically feasible, implement the following controls: i. For accounts that are accessible only within Secure Zones or High Security Zones, require that passwords have at least twelve (12) characters; ii. For authentications which cross a zone boundary into a Secure Zone or High Security Zone, require Multi-Factor Authentication. For accounts accessible from outside a Secure Zone or High Security Zone require passwords that have at least eight (8) characters and are not be one of the user's previous four (4) passwords; and implement account lockout for failed access attempts in accordance with subsection k; iii. When developing password policies, CAs SHOULD take into account the password guidance in NIST 800-63B Appendix A. 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." In section 2.h., change "Require" to "Have a policy that requires" In section 2.i., change "Configure" to "Have a procedure to configure" Change section 2.k. to read: "k. Lockout account access to Certificate Systems after no more than five (5) failed access attempts, provided that this security measure: i. is supported by the Certificate System, ii. Cannot be leveraged for a denial of service attack, and iii. does not weaken the security of this authentication control;" Change section 2.n. to read: "Enforce Multi-Factor Authentication for all Trusted Role accounts on Certificate Systems (including those approving the issuance of a Certificate, which equally applies to Delegated Third Parties) that are accessible from outside a Secure Zone or High Security Zone; and" - MOTION ENDS - The procedure for approval of this ballot is as follows: Discussion (7+ days) Start Time: 2018-03-28 15:00:00 EDT End Time: 2018-05-17 17:45:00 EDT Vote for approval (7 days) Start Time: 2018-05-17 17:45:00 EDT End Time: 2018-05-24 17:45:00 EDT Sorumluluk Reddi Bu e-posta mesaji ve onunla iletilen tum ekler gonderildigi kisi ya da kuruma ozel olup, gizli imtiyazli, ozel bilgiler icerebilecegi gibi gizlilik yukumlulugu de tasiyor olabilir. Bu mesajda ve ekindeki dosyalarda bulunan tum fikir ve gorusler sadece adres yazarina ait olup, TUBITAK / Kamu SM?nin resmi gorusunu yansitmaz. TUBITAK / Kamu SM bu e-posta icerigindeki bilgilerin kullanilmasi nedeniyle hic kimseye karsi sorumlu tutulamaz. Mesajin yetkili alicisi veya alicisina iletmekten sorumlu kisi degilseniz, mesaj icerigini ya da eklerini kullanmayiniz, kopyalamayiniz, yaymayiniz, baska kisilere yonlendirmeyiniz ve mesaji gonderen kisiyi derhal e-posta yoluyla haberdar ederek bu mesaji ve eklerini herhangi bir kopyasini muhafaza etmeksizin siliniz. Kurumumuz size, mesajin ve bilgilerinin degisiklige ugramamasi, butunlugunun ve gizliligin korunmasi konusunda garanti vermemekte olup, e-posta icerigine yetkisiz olarak yapilan mudahale, virus icermesi ve/veya bilgisayar sisteminize verebilecegi herhangi bir zarardan da sorumlu degildir. ****************************************** Disclaimer This e-mail message, including any attachments, is intended only for the use of the individual or entity to whom it is addressed and may contain confidential, privileged, private information as well as the exemption from disclosure. The information and views set out in this email are those of the author and do not necessarily reflect the official position of TUBITAK / Kamu SM. TUBITAK / Kamu SM shall have no liability to any person with regard to the use of the information contained in this message. If you are not the intended addressee(s) or responsible person to inform the addressee(s), you are hereby notified that; any use, dissemination, distribution, or copying of this message and attached files is strictly prohibited. Please notify the sender immediately by e-mail and delete this message and any attachments without retaining a copy. TUBITAK / Kamu SM do not warrant for the accuracy, completeness of the contents of this email and/or the preservation of confidentiality, and shall not be liable for the unauthorized changes made to this message, viruses and/or any damages caused in any way to your computer system.
_______________________________________________ Public mailing list Public@cabforum.org https://cabforum.org/mailman/listinfo/public